45568132 W RNO Analysis Mate V1 0

8/21/2019 45568132 W RNO Analysis Mate V1 0

http://slidepdf.com/reader/full/45568132-w-rno-analysis-mate-v1-0 1/1528

Developed By: Aumpika Viun (Ice)

Contact: [email protected]

W-RNO AnalysisMate Ver1.0

0. UTRAN Network Architecture and Protocols

1.1 UMTS Network Architecture

1.2 UTRAN Protocols

1. RRC,RB and UE Measurement Procedures

1.1 Mapping of UE state to 3GPP Specifications

1.2 RRC Tasks and Functions

1.3 RRC Modes and State Transitions including GSM 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)

MML C

Conv

Underl

Click to retur

Val

Com

mailto:[email protected]

mailto:[email protected]



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 C S 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)



Release Date Genex Probe Version Genex AssistantVersion

RAN Version

25-Jun-09V100R005C01B040

(V1.51 20090210 )

V100R005C01B040

(V1.52 20090210 )10.0

Change Type Change Date

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

ntion Description

ine TextAll texts with an Underline has a hyperlink function which link to other r

signalling procedure, signalling measages,parameter description, feature

Change History

to main page Click here to return to root topic

ue= Give an acutal value includes the conversion schemes

ents Extra comments for some topics



;



RNC Version

V200R010C01B061

Remark

elated information e.g.

algorithm etc.





Change Type

Correction

Addition

Remove



The UMTS PLMN is logically divided into a Core Netwo rk (CN), a Radio Access Network (RAN) and the Us

The Core Network(CN) consists of an enhanced GSM Phase2+ with a Circuit Switched CS and Packet S

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 re

encoding,Modulation and demodulation on the carrier,Power control,Quality and field strenght measurements,

- UMTS Subscriber Identity Module (USIM), The USIM functions to save data and procedures in ther termina

entries, etc. The installed USIM is made available to the customer by the network operator and can be update

Examples of USIM data and procedures,

1.Data: International Mobile Subscriber Identity,Packet Switched Location Information,Security Information for

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, w

network solution. Please note, that there are differences in the protocol stacks on the Iu-CS and Iu-PS interfa

- 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 handove

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 inter faces Iu, Iur , and Iub, ATM is used for the transport o f user data and h igher layer signal l ing

Click to return to main page

UMTS Network Architecture (Rel'99)

Radio Network Controller(RNC) Functionality



The RNC has many different tasks in the UTRAN. It is responsible for e.g. Radio Resource Management (RR

and to the PS domain via Iu(PS) interface. Signalling and data transfer to other RNCs are possible via Iur inter

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

- 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 N

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).

higher layer functions related to radio access and information transport through UTRAN. The S-RNC performs

- 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

In the case of Soft Handover,S-RNC performs data splitting toward the different NodeBs and combining toward

the C-RNC of some NodeBs used for the connection toward an UE. The S-RNC is no anchor functionality. It ca

Summary: The S-RNC for one UE is the RNC that terminates both Iu link for transport of user data and



Node B Functionality

A nodeB is a physical unit for i

serviced by a Node B. Generall

A Node B can be used for Freq

in different timeslots) or dual mthe opposite direction. Node Bs

predefined one and instructs th

Error Rate (FER). The followin

- Radio Channel functions: Tr

- Air Interface management.

Intra NodeB SofterHO,Power C

- O&M Processing,Interfacing

- Cellular Transmission mana

of the physical transmission int

1.International UMTS/GSM Service Area

Geographical and UTRAN Entity Identifiers

(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

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

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

The UE receives all the data streams from the cells,it is connected to and adds them together (RAKE Receiver

the S-RNC takes only the data frame with the smallest bit error rate, all other data frames will be discarded (SeBecause the implementation of Iur interface is optional,i's matter of network planning, whether the usage of D-

Summary: D-RNC is any RNC, other than SRNC that controls cells used by the UE. The D-RNC performs

,but routes the data transparently between the Iub and Iur interfaces.The UE can be connected to 0 ,on

more UTRAN access points.



, . . -

2.National Service Area

National Service Area is the area of on country or region. It is identified by the Mobile Country Code (MCC) an

3. PLMN Service Area

PLMN Service Area is the service area of a single PLMN. It identified by the Mobile Country Code(MCC) and C

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 SGS

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

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 L

stored in the PS-domain (in the SGSN) of UMTS. It is world-wide uniquely identified by the Routing Area Identit

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 P

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

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

E212.

2. CN-Domain Id:

CS- and PS core network introduce their own regional area concept. This is the concept of Location Area for CLAI= 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

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

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 t

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

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



UTRAN Protocols

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

1. Core Network Identities or NAS (Non Access Stratum) Identifiers: These identifiers are allocated by the

2. UTRAN identifiers : UTRAN identifiers are always temporary (Radio Network Temporary Identifiers ,RNTIs)

- International Mobile Subscriber Identity (IMSI)

The IMSI is the quasi-permanent subscriber identity in GSM/UMTS. The IMSI is composed by the Mobile Coun

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. T

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

- 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 EI

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 th

1. Serving RNC RNTI (S-RNTI) : The S-RNTI is allocated by the S-RNC,after every S-RNC Reallocation it has

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 t

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

(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 U



The communic

between UE an

signalling betw

1. Access Stra

messages occu

UTRAN and UT

enables the CN

2. Transport S

and user data.

messages betw

3. Non-Access

access or trans

,handling of sub

UTRAN Protocol Architecture

The UMTS network is split into

(radio access bearer services)

between the CN and the UEs u

The higher layer protocols of th

Session Manangement (SM) ta

procedures. The radio and Iu pr

used in the Iu and radio protoco

UTRAN Interface Protocol Structure

The protocol structures of the U

planes as logically independent

parts remain intact.

The transport system used with

different types of bearer service

type2 can be set up with explici

switches. This behavior results

Horizontal Layer:The general protocol model con

are visible in the Radio Network

specific requirements.

- Transport Network Layer : T

layer and its transport frame lay

- Radio Network Layer : The R

streams, to be transported thro

Vertical Plane:

There is also a vertical structur

next to eachother. The general

Horizontal Layer

Vertical Layer



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

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 pl

Plane.

-User Plane: The user plane su

protocols will be transmitted via

explicit signalling.

-Control Plane: The control pla

application protocol,one or sev

signaling,which is UMTS-specifi

Application Protocol messages.

-Transport Network Control Pprotocols are used to set up an

not necessary to use the ALCA

are used. The Transport Netwo

information.

The Transport Network Control

to be total independent of the te



UMTS transports the control signaling and the user data over the same transport network. So,there are some p

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.

-User data stream : The user data streams are generated by the applications using the CS core network servi

-

The CS control plane is used for the exchange of control information which are related to CS services. In add

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

-Medium Access Control (MAC) : The MAC protocol belongs to Layer 2. The tasks of MAC are the control of

-Radio Link Control (RLC) : As MAC also the RLC protocol is a Layer 2 protocol. RLC provides three reliabilt

-Radio Resource Control (RRC) : The RRC protocol is the first protocol of Layer 3. The RRC protocol perfor

-NAS Protocols : On top of RRC there are the control protocols for the non-access stratum (NAS). For the CS

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 task

counterpart to RRC

-Signaling Connection Control Part (SCCP): The SCCP has mainlu transport tasks. It is used to establish a

identifier.

-MTP 3B,SAAL,AAL5, ATM : These protocols belong to transport network (ATM). They provide a signaling be

User Plane- CS

Control Plane - CS



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

UTRAN Interface Protocol -Uu (UE-UTRAN)

For Packet Switched (PS) service,there are different procedures. So there is a need for special proctocols for

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 a

- ATM,AAL 5, SAAL,MTP 3B : Also the transport and access stratum on the Iu-PS interface is similar to the Iu

- SCCP,RANAP : SCCP and RANAP are the same as for CS. The SCCP is mainlu used to setup a signaling c

- NAS protocols : The only special protocols for the packet switched service are the non-access stratum proto

network has its own mobility managment GMM ( GPRS Mobility Management). To set up a data session the S

In contrast to the control planes, that look very similar for PS and CS, the user plane has important diff

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

network have their own special network protocols (e.g .TCP/IP). When a UMTS user wants want to be connect

network this only data. But because of its special role, the network protocol of the external network is called Pa

transport of the PDP packets.

-Packet Data Convergence Protocol (PDCP) : This protocol performs header compression of the PDP packe

-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.

-UDP/IP : To route from RNC to SGSN the standard UDP/IP protocol stack is used. This is a connection less u

-AAL5 /ATM : The UDP/IP datagrams (packets) are transmitted on ATM using the adaptaiton layer 5.

-AAL 2 : To provide a circuit switched like transport bearer on Iu, The AAL 2 protocol is used. This adaptation l

includes time stamps in the transport frames. This allows synchronization and timing control between sender a

-Iu User Plane protocol (Iu UP) : The Iu user Plane protocl is on top of AAL2. This protocal can provide differ

Please note that AAL 5 is used for all control functions on the Iu-CS interface ( <> RANAP) and the Iub i

messages (<> Iub-FP) between NodeB and RNC and for user data on Iu-CS interface between RNC and

Control Plane - PS



Physical Layer (L1) Functions

Uu interface is

important inte

The radio inter

-the physical la

-the data link la

-the network la

The layer 1 suconsisting in in

… It is basically

“physical chann

The layer 2 pr

sublayers: MAC

Control).

The layer 3 is

Resource Contr

L3 are implem

The protocol l

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 h1. CRC attachement (error detection) : Every transport block of a transport block set get its own CRC,used f

2. Transport Block concatenation & code block segmentation : The transport blocks are concatenated afte

afterwards

3. Channel Coding : Channel coding can enhance symbol correlation to recover signals in the case of interfer

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. th

5. Radio Frame Equalization : If the data block after rate matching is too short for one radio frame,some pad

6. Interleaving : Interleaving is used to damage symbol correlation and reduce the impact caused by fast fadin

7. TrCH Multiplexing : This function multiplexes several transport channels to one CCTrCH (Code Composite

8. Ph sical Channel Se mentation : The CCTrCH are s lit to several h sical channels,it there are an

Transport Channel Processing for FDD Uplink Transport For



L2 Functions

L2 includes four sublayers, Medium Access Control (MAC), Radio Link Control (RLC), Broadcast/Multic

(BMC) and Packet Data Convergence Protocol (PDCP).

I. MAC, The funct ions 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 channels7.Multiplexing/demultiplexing of upper layer PDUs into/from transport blocks delivered to/from the physical laye

transport channels

8. Switching of the transport channel type for a radio berarer(controlled by RRC),means several transport chan

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)

9. DTX bit insertion : If no information is to be transmitted by the network, so called DTX (Discontinuous trans

10. Radio Frame segmentation : When a data block is too long for one radio frame(10ms), it is segmented to

11. Physial Channel Mapping : The data has to be mapped to the slot format of a physical channel or to seve

Transport Format Combinations

When multiple transport channels are multiplexed to CCTrCH (Coded Composite Transport Channel) and tr

channel. Therefore the so called "Transport Format Combination Identifier (TFCI)" is used. In UE and Nod

- 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 combinati

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

care,taking UE radio capabilities into account.

3. Several transport format combinations from a so called "transport format combination set" .Every transp

combination identifier TFCI.

B) Radio Tasks:

1. Provision for higher layers with measurements and indications (such as FER, SIR, interference power, and t

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 p

the following categories:

1. Synchonization procedures : These types of procedures are used for cell search,radio frame/slot and chip

the UE to the cell timing.

2. Power Control Procedures : One of the most critical issues for CDMA systems is the near-far problem. Th

3. Random Access Procedures : Like all known mobile radio access technologies also WCDMA has to use r

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 perfratio,interference power,signal power). These measurment are used as criteria for the cell reselection or hando

frames. In such radio frames some slots are not used for transmission/reception,rather the measuement are t



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 UTRAN4.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 - Iur ( RNC-RNC)

UTRAN Interface Protocol - Iub ( RNC-NodeB)The control plane of the Iub i

-NBAP (NodeB Application P

(e.g. code allocation,transceive

-SAAL,AAL 5, ATM : These pr

The user plane of the Iub inte

way as on the Iur interface. T

-Frame Protocols : The Frame

-AAL 2 ,ATM : The frame proto

first-AAL type 2 signaling protoc

-STC, SAAL,AAL 5,ATM : The

The physical layer is not stan



The following protocol model is

PS-core network domain.

1. Iu-CS protocol stack

The control plane for Iu-CS is

-RANAP ( Radio Access Netw

protocol of the Iu-CS interface

-SCCP (Signaling Connection

connection UTRAN-MSC for ev

-MTP 3B,SAAL,AAL5,ATM : T

The user plane on Iu-CS has t

-Iu UP (User Plane) protocol : control,data rate control,backw

-AAL2,ATM : For the data bea

The t ranspor t network cont ro

network control plane consistin

- AAL type 2 signaling protoc

- STC,MTP 3B,SAAL,AAL5,AT

UTRAN Interface Protocol - Iu ( UTRAN-CN)

The control plane of the Iur in

-RNSAP (Radio Network Sub

covers resource allocation for a

(SRNS relocation)

- SCCP (Signaling Connectio

the S-RNC sets up one SCCP

signaling messages


The user plane of the Iur inte

protocols

-Frame Protocols : The data t

protocols allow traffic managem

-AAL 2 ,ATM : The frame proto

-AAL type 2 signaling protoc

-STC,MTP3B, SAAL,AAL 5,AT

Converter) provides functionalit

signaling bearer of RNSAP of C

Iu-CS Protocol Stack



2. Iu-PS protocol stack

The Iu-PS interface is the interf

Iu-PS control plane

-RANAP : The application proto

-SCCP : Provides signaling con

service. SCCP connections on I


The user plane on Iu-PS is co

necessary. The UTRAN provide

-Iu UP protocol : As for Iu-CS t

-GTP-U (GPRS Tunneling Pro

the PDP context and sequence

-UDP/IP : The UDP/IP protocol

vice versa.

-AAL 5,ATM : The ATM adapta

The AAL 5 virtual channels do

for the packet transfer. Therefo

UMTS system has different application parts depending on interface being used and each application part cont

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 signali

1. RANAP (Radio Access Network Applciation Part) : This application part is the Iu interface signaling proto

implemented by various Elementatry Procedures (EP). Each RANAP function requires the execution of one or

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 con-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 interpre

-Security Mode Control : Sets the ciphering on or off by encrypting signaling and user data connection in the

2. NBAP (NodeB Application Part): This application part is the Iub interface signaling protocol. It is divided in

-Common NBAP : Defines the signaling sequence across the common signaling link. Common NBAP defines

management

-Dedicated NBAP : Sequence related to a specific UE signaling in the NodeB. Upon radio link setup procedur

UMTS Protocol Stacks -> Application Part

Iu-PS Protocol Stack



3. RNSAP (Radio Network Subsystem Application Part) : This application part is the Iur interface signaling

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

-CCCH Signaling Transfer : Allows the SRNC and DRNC to pass information between UE and SRNC on a C-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 provid

words, ALCAP setup transport bearer such as AAL2 path between different nodes interfaces (Iu,Iur,Iub) in the

Control Plane (NBAP,RANAP,RNSAP). And then,data bearer is setup by the ALCAP protocol.The use of the A

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 se

The setup or release of a bearer is always controlled by an application protocol. But to avoid the restriction to a

the application protocol can control the bearer via abstract parameters (QOS parameters) only. This principle i

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 ,persuccessful bearer setup, the application protocol procedure can be finished, and the application can be inform

.

The following NBAP functions are defined:

1.Cell Configuration Management ,this function gives the controlling RNC (CRNC) the possibility to manage

2.Common Transport Channel Management,this function gives the CRNC the possibility to manage the con

3.System Information Management, this function gives the CRNC the ability to manage the scheduling of Sy

4.Resource Event Management, this function gives the NodeB the ability to inform the CRNC about the statu

5.Configuration Alignment ,this function gives the CRNC and the NodeB the possibility to verify and enforce

6.Measurements on Common Resources,this function allows the NodeB to initiate measurements in the No

7.Radio Link Management, this function allows the CRNC to manage radio links using dedicated resources in8.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 N

10.Measurements on Dedicated Resources,this function allows the CRNC to initiate measurements in the N

11.DL Power Drifting Correction, this function allows the CRNC to adjust the DL power level of one or more r

12.Reporting of General Error Situations, this function allows reporting of general error situations.



er Equipment UE.

witched PS (i.e. GPRS) domain

sponsible 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.

l equipment. It supports call handling,contains security parameters,user-specific data e.g. telephone directory

e.g. via SMS or cell broadcasting.

authentication and chiphering for circuit and packet switched applications,PLMN selector and HPLMN search

.

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

e.

r situations, where a UE„s active cells are under the control of more than one RNC. One RNC is responsible f

informat ion.



) and the control of itself and the connected NodeB (O&M functionality). It is connected to the CN , CS domai

ace 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:

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

The existence of a serving RNC does not imply that the UE is camped on a cell belonging to the S-RNC.The s

the following functions:

/modification or release of radio resources,for Outer Loop Power Control and for Handover decisions/initiation.

the CN. It decides to add or remove cells in the Soft Handover. The S-RNC is in most cases (but not always)

n be re-allocated to another RNC with the S-RNS reallocation procedure.

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



plementing a UMTS radio transmission. Depending on the sectoring of the cells ,one (omni) cell or multiple (s

y,up to six cells are serviced by a Node B in UMTS.

uency Division Duplex (Uplink and Downlink separated by different frequency bands),Time division Duplex

ode operation. A Node B converts user and signalling information received from the RNC for transport via theare involved in power control,NodeB measures the signal to noise ratio (SIR) of the User Equipment ,compar

UE to control its transmission power. The NodeB also measures the quality and strength of the links and det

g are examples of NodeB functions:

ansport to physical channel mappings. Encoding/Decoding – Spreading/De-spreading user traffic and signallin

ontrolling Uplink and Downlink radio paths on the Uu Air Interface,Baseband to RF conversion,Antenna multi-

ontrol,Quality and signal strength measurements

ith M2000 and RNC for alarm and control (Operations and Maintenance) functions.

gement. Managing ATM switching and multiplexing over the Iub interface. Control of AAL2/AAL5 connections.

erfaces – E1, PDH, SDH or microwave.

a cell, that does not belong to the S-RNC. This means the UE is connected with a cell controlled by a RNC diff

E is connected to, but its not the S-RNC.Therefore D-RNC performs the C-RNC functions for the cells not

-RNC. In the downlink the S-RNC sends the data to own cells and to the D-RNC(soft HO),this is called splittin

, Maximum Ratio Combining). In the Uplink,the S-RNC receives data from the own cells and from the D-RNC ,

lective combining). The usage of a D-RNC requires a Iur interface between D-RNC and S-RNC.NCs is allowed or not.

macro-diversity combining and splitting,if necessary. The D-RNC does not perform user plane data L2

or more DRNCs. ( Macro Diversity is an operation state in which a UE simultaneously has radio links



, - .

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

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

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

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

y. The RA is sub-divided into the Cell-Areas.

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

aphical and physical entities of UTRAN are described as follow,

MCC(mobile country code) and a MNC(mobile network code). MCC and MNC are allocated by ITU-T and are

S and the concept of Routing Area for PS.

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

NC-ID the Cell-ID forms the UTRAN cell ID

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 r

try Code,MCC (3 digits) + Mobile Network Code,MNC (2-3 digits)+Mobile Subscriber Identification Number,M

his TMSI is allocated to an UE by VLR and stored in the U-SIM. It has only local significance i.e. within the are

-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

RNCs. Fours RNTI types exists:

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

he 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

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



tion between the different domains can be divided according to their functions. The UTRAN has the functions

d UTRAN and transport of signalling messages and user data between UE and CN. Therefore we can distigui

en UE,UTRAN and CN as follows,

um(AS) : The Access Stratum covers all signalling exchange used to control the access of an UE to the netw

r between UE and UTRAN and between UTRAN and CN. The difference between the access stratum UE-

RAN-CN is ,that the UTRAN-CN access stratum shall be independent of the radio technology used in UTRAN.

to support several different radio access technologies.

ratum: The Transport Stratum protocols and messages have the task to transport higher layer PDUs (Protoco

ecause UTRAN has the task to transparently transport data between UE and CN,there will be transport stratu

een UE and UTRAN and between UTRAN and CN.

Stratum (NAS) : The Non-Access-Stratum covers all messages of higher layers and user data, that do not de

port tasks.This cover pure application control (application stratum), service request and control (serving stratu

scription data and subscriber specific services (home stratum).

he CN,UTRAN and the UE. CN and UTRAN are connected via Iu interface,UTRAN and the UE via Uu(radio) i

nd control information (including requesting the service,controlling different transmission resources,handover

ing 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 Ma

ks. The NAS procedures (of Rel. '99) are in most cases unchanged compared to the GSM Phase 2+

otocols contain mechanism for transparent NAS message transfer. So-called Direct Transfer (DT) procedures

ls for these these transparent NAS message transfer.

TRAN interfaces are designed in horizontal layers and vertical planes. The general protocol model describe

of each other. The modularity of this model allows changing parts of the protocol structure in the future,if necc

in UTRAN is ATM. There is difference between the usage of ATM and the use PCM lines in a GSM-BSS. ATM

labelled AAL type 1,AAL type 2, AAL type 3/4 and AAL type 5. In UTRAN only AAL type 2 and AAL Type 5 ar

signalling. This means before a AAL type 2 virtual channel can be used,there might be signalling between th

in a new protocol model, where protocols for user bearer set up and release occur.

sists of two main horizontal layers- the Radio Network Layer and Transport Network Layer. All UTRAN relate

Layer only.The Transport Network Layer is used for UTRAN,offering transport technologies.It is without any U

he Transport Network Layer consists of all protocols used for the transport network solution. This includes the

er,also the bearer service protocols are included.

adio Network Layer contains all protocols,that are specific to the radio access and transport stratum. Also all

gh UTRAN, belong to this layer.

, the elements of this vertical structure are planes. A plane principle is protocol stack,more than one plane ca

protocol model consists of three vertical planes- the Control Plane,the User Plane and the Transport Network



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

pports the data streams for user data. Therefore the data streams are packed into frame protocols. These fra

data bearers. In contrast to the signalling bearers of the control plane,the data bearer can require to be set up

ne consists of all application protocols that are used for radio network controlling. To transport the messages

ral signaling bearers,provided by the transport network are neccesary. The Control Plane is used for all contro

ic. It includes the Application Protocols (i.e. RANAP,RNSAP and NBAP) and the signaling bearer for transport

lane: The transport network control plane contains the ALCAP (Access Link Control Application Part). The ALrelease the data bearers of the user plane. Also ALCAP messages require a signaling bearer for transmissio

for all data bearers. Expecially the transport network control plane is not necessary when pre-configured bea

rk Control Plane is used for all control signaling within the Transport Layer. It contains no Radio Network Layer

Plane acts as plane between the Control Plane and User Plane, it enables the Application Protocol in the Con

chnology selected for data bearer in the User Plane.

Control Plane



rotocols supporting the user data transfer. In the lowest layers there are the same protocols as for the control

The same basic stack is used for the user plane.

ces (switched channels). These data streams are directly input to the RLC

ition ,the CS control plane is used for controlling supplementary services and it can be used for the exchange

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.

modes for every radio bearer. These modes are : Acknowledge (AM),Unacknowledge(UM) and Transparent

s all higher layer tasks related to the access stratum on the air interface (e.g. radio bearer setup)

service these are: MM (Mobility Management),CC (Call Control),SS(Supplementary Services) and SMS (Shor

s 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 expli

rer to transport SCCP and RANAP.



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

d CS. UMTS has been designed to support both types of services, so that there are no special protocols.

interface towards the MSC.

nenction to the SGSN in the core network. RANAP handles all signaling transport and access related tasks.

cols. Because there are essential differences how to handle a packet switched service request, the PS core

(Session Management) protocol is used. The SMS is in fact the same as for CS.

rences.

. These external data network have their own special network protocols ( e.g. internet) . These external data

ed with such an external network, the UE has to send packets of this special network protocol, for the UMTS

cket Data Protocol (PDP). It is the task of the UMTS network to provide a tunnel (PDP context) for transpare

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

TP-U organizes addressing and identification of the originator and destination of the data between RNC and

nreliable transport service. In principle only routing is performed with UDP/IP

ayer provides a bearer channel (virtual channel of AAL type 2) with certain QOS gurantees. Additonally the A

nd receiver.

nt stages of user data stream support.

nterface (<>NBAP). On the other hand, the real time AAL 2 is used for relaying UE- data and UE-signali

MSC.

User Plane -PS



the interface between User Equipment (UE) and UMTS Terrestrial Radio Access Network (UTRAN) and

face in the UMTS system.

face (Uu) is layered into three protocol layers:

er (L1)

yer (L2)

er (L3).

ports all functions required for the transmission of bit streams on the physical medium. It is also in charge oficating to higher layers, for example, Frame Error Rate (FER), Signal to Interference Ratio (SIR),interference

composed of a “layer 1 management” entity, a “transport channel” entity, and a

el” entity.

tocol is responsible for providing functions such as mapping, ciphering, retransmission and segmentation. It i

(Medium Access Control), RLC (Radio Link Control), PDCP (Packet Data Convergence Protocol) and BMC (

plit into 2 parts: the access stratum and the non access stratum. The access stratum part is made of “RRC (R

ol)” entity and “duplication avoidance” entity. The non access stratum part is made of CC, MM parts.The RRC

nted by RNC, and the MM and CC functions of L3 are implemented by CN.

yers are located in the UE and the peer entities are in the node B or the RNC.

as the following steps,that can be identified with the presented functional blocks:r error detection

r the CRC is appended. if the resulting data block is too long (e.g does not fit into one radio frame) a segment

ence.UTRAN FDD and TDD offer four different channel coding schemes as FEC(Forward Error Correction). T

physical layer gets matching parameters from RRC layer

ing bits are appended

g and interference of the channel

Transport Channels)

at Combinations



ast Control

r on common

nel types can

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 dete

3. Sequence numbers check

4. Protocol error detection and recovery

5. Ciphering

6. Suspend/resume function

III. PDCP, The funct ions o f PDCP include:

1.Header compression and decompression of IP data streams at the transmit and receive enti2.Transfer of packet oriented user data using RLC transparent,unackowledge or acknowledge

3.Forwarding of PDCP-SDUs from NAS to RLC, and multiplexing of different RBs to the same

IV. BMC ,The funct ions 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)

mission) bits are inserted. This is only for downlink

several radio frames

ral physical channels if neccesary

ansmitted in physical channels,there has to be an indication which transport formats are used for every transp

B the value of the TFCI can be translated into:

on is signaled by RRC during radio bearer establishment.

transport format set build a "transport format comnination". Such a combination has to be chosen with

rt format combination in the transport format combination set is uniquely identified with a transport format

ransmission power)

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

synchronization to physical channels. In the TDD mode also timing advance procedures are used to synchron

solution for this is a very fast power control mechanism,using a closed control loop ( UE<>NodeB<>UE)

ndom access mechanism to establish a radio connection between an UE and the Network. BNut also for

rm measurements of radio signal quality (bit error rate) and radio signal strength (signal interferencever procedures. For the measurments the UE physical layer has uses so called compressed mode mode radi

en performed.



terface contains the following protocols:

rt) : The NBAP protocol is the application protocol of the Iub interface. It organizes all controlling tasks betwe

r configuration).

tocols constitute the signalling bearer for the NBAP messages.

rface has to transfer the downlink and uplink data to and from the UE. Therefore different frames are d

e user plane consists of:

Protocols encapsulate the UE data (UL&DL) on the Iub interface

col,that encapsulate the UE data,are transported over AAL 2 virtual channels of ATM. These AAL 2 virtual cha

l : The AAL type 2 SP provides the messages and functions to setup, release and modify AAL 2 virtual chann

STC (Signaling Transport Converter),SAAL,AAL 5 and ATM provide the signaling bearer for AAL type 2 signal

dardized. it is up to the operator and verndor to choose an appropiate physical transmission system.



applied to the UTRAN interfaces Iu, there are differences between Iu-CS toward the CS-core network domain

formed out of the following protocols:

ork Application Part) : The RANAP protocol is responsible for all access and signaling transport related task

Control Part) : The SCCP is used to setup signaling connection between RNC and MSC. There will be one a

ery IE using CS service.

eses protocols provide the signaling bearer for RANAP/SCCP messages

o support the transfer of real time CS data streams. Therefore the Iu-CS plane has the following protocols:

The Iu UP protocol is used to provide additional support functions for CS data streams on Iu. These functionsrd error conrrection.

er to transport the data streams the AAL 2 virtual channels are used.

l plane is necessary ,because AAL2 virtual channels need to be setup and released. The protocol suite on th

of:

l : used to setup ,modify and release AAL 2 virtual channels.

M : These protocols provide the signaling bearer for the AAL type 2 signalling protocol messages.

terface contains the following protocols:

ystem Application Part) : The RNSAP protocol is responsible for the communication between S-RNC and D-

UE in a cell of the D-RNC,soft handover procedures and procedures to transfer the S-RNC functionality to a

Control Part) : The SCCP is used to set up a signaling connection between S-RNC and D-RNC for the UE.

signaling connection for every D-RNC and UE. The signaling connection will be used for fast identification of t

hese protocols form the signaling bearer used for the RNSAP protocol messages.

face has the tasks to transport uplink and downlink data for the UE connected to a D-RNC. This tasks

and from the UE will be encapsulated into frame. These frames are defined by so called frame protocols. Th

ent with in-band signaling

col packets are transmitted via Iub using AAL 2 virtual channels. So AAL 2 ,ATM form the data bearer on the I

l : The AAL type 2 SP provides the messages and functions to setup, release and modify AAL 2 virtual chann

M : These protocols provide the signaling bearer for the AAL type2 signaling protocol. The STC(Signaling Tra

y for congestion handling and load control. The protocol suite MTP3B,SAAL,AAL5 and ATM can be shared wit

ontrol Plane



ce between RNC and SGSN. The control plane of Iu-PS is similar to the Iu-CS plane. It consists of:

col for Iu-CS and Iu-PS

nection on Iu-PS. There will be one and only one SCCP connection between RNC and SGSN for every UE usi

u-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 lay

s the following protocols on the Iu-PS user plane:

he Iu UP protocol can provide additional support functions for the data stream.

ocol-User Plane): GTP-U provides a frame for the user data to be transported. In a GTP-U frame a reference

numbers for the data are contained.

suite is used as network layer between RNC and SGSN. The task of these protocols is to route from RNC to S

tion layer of type 5 is used as bearer for the packets of IP/UDP/GTP-U.

ot need to be set up in a dynamic manner. Rather the operator is expected to pre-configure the AAL 5 bearer

re on Iu-PS there is no need for a transport network control plane. no bearer set up with explicit signalling is n

rols signaling information for the call setup between nodes. Basically these applications message structure is

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

col that contains all the control information specified for the Radio Network Layer. The fucntions of RANAP are

more EP.

ected RAB

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

radio interface

o two procedures :

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

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

RANAP NBAP



rotocol that controls signaling transfer between two RNC (SRNC and DRNC) in order to support the inter RN

to avoid DL power drifting between radio links

CH controlled by the DRNS

s the signaling capability to establish,release and maintain AAL2 connections by a series of ATM VCCs. In ot

UTRAN. The transport bearer in the User Plane are setup first sending signals by the Application Protocol in t

LCAP is dependent on the type of bearer to be used. The signaling bearers are usually pre-configured. This m

tup runs in the following manner:

single transport system, the application protocols shall not be specific to a certain transport solution. Therefo

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 ad to start the data stream transmission.

he cell configuration information in a NodeB.

iguration of common transport channels in a NodeB.

tem Information to be broadcast in a cell.

s of NodeB resources.

hat both nodes have the same information on the configuration of the radio resources.

eB. The function also allows the NodeB to report the result of the measurements.

a NodeB.

deB.

odeB. The function also allows the NodeB to report the result of the measurements.

adio links in order to avoid DL power drifting between radio links.



n

r



via Iu(CS) interface

hnology

erving RNC handles all

alling



ector) cells can be

(Uplink and Downlink

radio interface,and ins the value with a

rmines the Frame

g.

coupling,

. Control

erent

g.

processing

ith two or



and

specified within ITU-T

b



eleased.

IN. The total length of

a controlled by a VLR.

which

to the



to provide access links

h three types of

ork. Access Stratum

. This

l Data Unit)

m

al with

)

nterface. User data

etc) are exchanged

agement (CM) or

are

s these layers and

essary,while other

supports

e used. Bearers of AAL

corresponding ATM

issues

TRAN

physical

ther data

coexist

ontrol



e

with

f an

l

the

CAPn. It is

rers only

rol Plane



plane. The following

of short messages. It

TM).

t

it



same as for the CS

nt

SGSN.

L 2 cirtual channel

ng



it is the most

easurements functionpower, transmit power,

s made of four

roadcast/Multicast

adio

functions of

ation is performed

ese



ction

ities respectivelyd mode

RLC entity

ort

to

ize



n RNC and NodeB

efined in the same

nnels have to be set up

els.

ing protocol.



and Iu-PS towards the

. It is the application

nd only one SCCP

can be : timing

transport

RNC. This

-RNC

his means

e UE in

equires the following

se frame

ub interface.

els.

sport

h the



ing PS

r are

number for

GSN and

to be used

cessary.

similar to the SS7

o



soft

er

e

eans

re



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 mod

further divided into 4 service states,which define what kind of physical channels a UE is using. The mapping of UE state

speciafication is shown below:

RRC Tasks and Functions

The RRC protocol is the application part for the UMTS radio access technology. This means all controlling radio tasks ar-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 phigher layer control plane protocol messages.

UE Switch on

UE Idle3GPP TS 25.304

UE Connected3GPP TS 25.331

GSMConnectedGSM TS 04.18

GSM PackTransfer

GSM TS 04.

GSM IdleGSM TS 05.08

UE Idle3GPP TS 25.3043GPP TS 25.331

Cell_DCH3GPP TS 25.331

Cell_PCH3GPP TS 25.3043GPP TS 25.331

Cell_FACH3GPP TS 25.3043GPP TS 25.331

URA_PCH3GPP TS 25.3043GPP TS 25.331



RRC Modes and State Transitions including GSM

The RRC protocol is an application part (Radio Resource Management) and transport protocol (NAS message transport

states.

The RRC state definiton describes the RRC protocol behavior as a nested set of stated. Two main states are def

1. UTRA Idle Mode : In UTRA idle mode, the UE has no signaling relationship with the UTRAN. In this case the idle mo

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 interfa

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 R

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 mes

-RB3 and optional RB4 : These two radio bearers shall be used for RRC messages carrying NAS message

The radio bearers 5,...,31 can be used with explicit radio bearer set up for all purposes, e.g. traffic channels o

For RRC messages the protocol specified which RLC mode and with this which radio bearer can be chosen f

Release RRCConnection

Release RRCConnection

Establish RRCConnection

Establish RRCConnection

CellReselection

Relof

URA_PCH

CELL_DCH CELL_FACH

CELL_PCH

UTRA RRC Connected Mode

Idle Mode

(UE camps on UTRAN cell)

G

UTRA: Inter-RAT

(MS in

(

G



RRC Idle Mode

RRC Connected ModeThe RRC connected Mode can be further decomposed into four different states. These four sub-states describe, on whi

UE. UTRAN can know any UE either on cell level (cell state) or on URA level (URA state). On the other hand any UE ca

exchange. Therefore the four connected states are introduced:

When a UE is switched on, it enters the RRC idle mode. In the RRC idle mode, there is no connection on the access str

in the RRC idle mode. If UTRAN wants to address the UE, it must use non-access stratum identifiers, such as IMSI or T

In the RRC idle mode, the UE monitors the BCCH, and when it is registered to the CN, it also listens to paging occasion

The transition from the RRC idle mode to the RRC connected mode can only be initiated by the UE by sending the "RR

used to exchange messages and data between the UE and UTRAN, the UE is identified by a Radio Network Temporary

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

channels depend also on the sub-states. For instance, the DCHs are not available in the sub-states CELL_PCH and CE

mode when sending the RRC Connection Request message to UTRAN. When UTRAN accepts the UE„s request, the U

RRC Mode Description

CELL_DCHIn this sub-state, dedicated physical channels are allocated to the UE. DCCH and – if configured – DTCH information ca

because the physical channels are exclusively allocated to this UE. UTRAN knows the active set cells for the radio links

allocated to the UE. In this state, the UE is capable to receive RRC messages on the DCCH (and BCCH, if it owns spec

UE reads the cell system information and acts accordingly. For instance, it determines the measurement quality and the

entered from Cell_FACH by setting up a DCH. When the last DCH is released the UE enters Cell_FACH,Cell_PCH,UR

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 cel

- 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 caseof user data (e.g. SMS messages) have to be transmitted. In this case, an exclusive allocation of one physical channel t

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

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

handover takes place in this sub-state. The UE is responsible for cell re-selection. By listening to the cell system informa

values, neighbourhood lists to perform the cell re-selection process. Other relevant information is also learned from the

RRC messages on the BCCH, CCCH and DCCH channels. Due to the discontinuous type of traffic, UTRAN can comm

,

2. UTRA RRC Connected Mode : In the connected mode the UE has a signaling connection with the UTRAN. The setu

connection set up). This procedure is the transistion from idle to connected mode. When the RRC connection is release

For multi-mode mobile phones (e.g. UMTS,GSM/GPRS) the RRC states can be combined with the radio resource

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, t

2. GSM conected mode : In GSM the RR (Radio Resource Layer) performs the radio management. This protocol can s

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 tempo

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 Technolo

handover from UTRA connected mode to GSM connected mode and vice versa. A transistion from UTRA connected mo

packet transfer in UMTS, making a cell reselection to a GPRS cell and getting a GPRS temporary block flow.



_

if the UE is "in service area":

- DCCH and DTCH are available

- perform cell reselection process


- 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

CELL_PCH and URA_PCH

The remaining two sub-states – CELL_PCH and URA_PCH – were introduced to cope with inactive data users. Just thin

with the data, and for a longer time, no transmission takes place. If this is the case, access stratum resources can be rel

DTCH is allocated to the UE. No exchange of data is possible between the UE and UTRAN. If the UE wants to transmit

The UE listens to the cell system information, broadcasted on the BCCH. It performs measurements accordingly, and is

PLMN with a higher priority. When UTRAN wants to transmit data to the UE, it must be paged first. Therefore, the UE h

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

must perform a cell update. Also periodical cell updates can be requested by UTRAN. To perform updates, the UE must

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

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 o

cell may belong to several URAs. If UTRAN wants to transmit something to the UE, it must page the UE within the URA.

URA – and periodic URA updates – when required by UTRAN.

In the URA_PCH or CELL_PCH state the UE shall perform the following actions:

if the UE is "in service area":

- maintain up-to-date system information as broadcast by the serving cell


- perform 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_P

if the UE is "out of service area":


- run timer T316;

- run timer T305

RRC Connection Mobility Management and RRC ModesIf the UE is in the RRC connected mode, but not in the CELL_DCH sub-state, it is responsible to inform UTRAN about a

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 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 t

2. Periodical updates can be enforced by the operator for UEs in the sub-states CELL_FACH, CELL_PCH and URA_PC

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 a

transmitted u link.



Cell and URA updates performed according to the causes in the figure below. As you can see, a periodic update can be

also, when the UE is in the CELL_FACH sub-state. A periodic update is a supervision mechanism, which can be used b

performed, a UE in the CELL_FACH sub-state may transit to the sub-states CELL_DCH, CELL_PCH or URA_PCH, or i

- 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

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 unrecovera

UE performs cell re-selection, and the new“ cell does not belong the the UE„s URA. An URA Update is then triggered b

When a UE transmits a Cell Update or URA Update message, it starts the timer T302. It waits for the T302 period to get

If no confirmation message arrived within this time period, the UE retransmits the original message. The number of Cell

send, it hereby limited to N302. The retransmission is of course only possible, when the UE is in the service area; if not,



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 update

It is still active, when the UE is out of the service area. What happens, if this timer expires? The timer T307 is activated,

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 mess

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.

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. B

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, th

happens, if the timer T316 expires? If the UE is still out of service area, it moves to the sub-state CELL_FACH and start

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 ti

timer T317 is stopped. Also timer T307 is stopped, when it was active. The UE has to transmit the RRC Cell Update mecell update: re-entering service area. If the timer T317 expires, the UE moves to the idle mode. It releases all dedicated






e can be

to 3GPP

e in the responsibility of RRC. The RRC has following functions:

erformed and it belongs to the transport stratum,because it carriers the

et

0



. Therefore the RRC protocol requires state definition with transitions between

ined:

e procedures have to be applied. This means as soon as the

ce. The radio bearers in an UE will be numbered from 0 to 31.

LC transparent mode, the downlink CCCH is mapped to the

sages that transport NAS messages inside.

on DCCH in RLC acknowledged mode.

r control channels.

or transport of this message.

Release RRConnection

Establish RRConnection

Initiationof a TBF

ease TBF

GSMConnected

Mode

SM-UMTS Handover

andover

GPRS Packet Idle Mode)

S camps on a GSM/GPRS cell)

RS PacketTransfer

Mode



h level the UE is known by UTRAN and which resources are allocated by the

have a DCH or a FACH or no transport channel for control message

atum level between the UE and UTRAN. UTRAN has no information about UEs

SI and LAI.

s on its PICH.

Connection Request" message to UTRAN. If common transport channels

Identity (RNTI). As can be seen in the

the connectivity level between the UE and UTRAN. The set of usable transport

LL_URA. The UE leaves the RRC idle

enters either the sub-state CELL_DCH or CELL_FACH.

n be transmitted. There no need to identify the UE on a dedicated channel,

and thus the location of the the UE. Also downlink shared channels can be

ific capabilities). The cell system information is broadcasted on the FACH. The

reporting events from the cell system information. This state can only be

_PCH or idle mode

ls);

when only higher layer signalling information (NAS signalling) or small amountthe UE would result in a waste of resources. Only common transport channel

icitly addressed, for instance by the RNTI. It has to monitor the FACH

to one cell, and this is the location information, known within UTRAN. No soft

tion from the BCCH, it gains all relevant measurement qualities, threshold

CCH. The UE receives

nd the UE to perform periodic cell updates.

p of this signaling conenction is done by a RRC procedure (RRC

, the connected mode is left and the idle more is entered.

management states of GSM/GPRS. In GSM/GPRS the states of a mobile

at the UE is camped on a GSM/GPRS cell

etup a RR connection between network and mobile equipment.

rary resource is called a temporary block flow (TBF). When a

gy (RAT).Therefore it is possible to make a inter-system

de to GPRS packet transfer mode is simply done by stoppint the



mode)

k about users, who surf in the Internet. After downloading some files, they work

eased when moving in one of the two states. In both states, no DCCH nor

omething, it must move first internally to the sub-state CELL_FACH.

responsible for cell-reselection. In addition to that, it periodically looks for a

s to monitor paging occasions on its PICH, i.e. it receives RRC messages both

, it only needs to page the UE there. If the UE changes the cell, it

change to the CELL_FACH sub-state. (Please note, that no

nows the UE on URA level.

e or several cells under one S-RNC. URAs may overlap, i.e. a

The UE is responsible for URA updates – when it changes the

H

detected change of location. The UE then moves (or is) in the CELL_FACH

– if it accepts the UE„s update request. Otherwise, it return the RRC

e CELL_FACH state and notifies UTRAN.

H.

indication by the UE„s higher layers, that data has to be



done not only, when the UE is in the CELL_PCH or URA_PCH sub-state, but

y the mobile operator to keep track of the UE. If a cell or URA update was

the RRC mode idle.

be confirmed by the UE. It may also include a re-

ble error and because of an periodic URA update – when the

the UE to get a new URA assigned.

the Cell Update Confirm resp. URA Update confirm message

Update or URA Update messages, the UE is allowed to

it must continue to search a service area.



s.

and the UE starts the cell selection process. If the timer T307 expires, the UE

age):

The UE attempts to find a serving cell again. If it is successful,

ing back in the service area can mean, that the UE is served

e cell or URA update has to be initiated by the UE. But what

timer T317. If the UE is back in the service area, it performs

er T317, if it was not yet active. If the UE enters the service area again, the

sage to UTRAN, indicating the cause of theresources.









>>State Transist ions Parameters Descr ipt ion (Module II)








>>UE&NodeB Timer and constant Parameters Descr ipt ion (Module II)




RRC Connection Request Message

RRC ProceduresBetween the UE and the RNC, the Radio Resource Control (RRC) protocol is used to exchange signalling and contro

transport channel configurations, and the physical layer settings. With that, the UE knows how to receive and transmi

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, pinformation transfer, etc.

-Radio Bearer Control Procedures :These procedures for radio bearer establishment, transport channel and physic

-RRC Connection Mobility Procedures :These procedures such as cell and URA updates, UTRAN mobility informat

-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 exampl

-UE information elements: UE related information is exchanged here, including capability update requirements, PD

-Radio Bearer information elements: These information elements mostly describe the characteristics of a radio bea

-Transport Channel information elements: Here, mainly the transport channel characteristics are described, such

-Physical Channel information elements: Here, everything relevant for the PHY-layer is covered, such as the descr

-Measurement information elements: Cell measured results, event results, filter coefficients etc. are exchanged he-Other information elements

RRC Connection EstablishmentThe purpose of the RRC Connection Establishment procedure is to create a RRC connection between the UE and U

To do so, the UE sends the RRC Connection Request message to the RNC. The UE was in the RRC idle mode, and

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 Con

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

interface and Uu-interface. Before the RNC returns the RRC Connection Setup message to the UE, it uses the UTRA

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

If the UE has received the message RRC Connection Setup, it returns the RRC Connection Setup Complete messag



RRC Connection Setup Message

2.RRC Con

If the S-RN

connection

configuratio

prepared to

parameters

establish sig

The RRC C

characteristi

the RRC lay

-If only the

modification

has no impa

change mea

-If the trans

PHY layer.

resources, c

-If a radio b

(RLC) layer

Broadcast/

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 i

-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

-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, becau

operator, but it is an option. If set by the operator, it is broadcasted as cell system information. The cells, listed in the

with the best one in the beginning of the list.



the RRC Co

PDCP layer

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 es

3. Transport channel information elements(TrCH IEs: UL/DL) to define the transport channel characteristics, in ot4. Physical Channel information elements(PhyCH IEs: UL/DL), which specify parameters relevant for the PHY lay



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 ch

mapped on transport channels. But on which transport channels can the higher layer information be transmitted? Ho

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 thewhich 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

holds relevant information to identify the receiver of the RLC PDU. For instance, if two DTCHs are multiplexed on one

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, DSC

-MAC-d: This MAC-entity control the access to the dedicated transport



RRC Connection Setup Complete message

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 ch

established. As can be seen, a UE can be immediately re-directed to another frequency band for the signalling beare

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.

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 measuremen

the downlink transmission must be interrupted to give the UE time to make its measurements. Therefore, this mode i

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 ce

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 t

called „closed loop modes“: - closed loop mode 1: A phase adjustment is done with one antenna. Hereby, the fe

are sent on four timeslots to the Node B.



L1 Synchonization on DPCCH and DPDCH (UL and DL)

Downlink synchronisation primitives

RRC Connection Establishment Timing

After the UE transmits RRC CONNECTION REQUEST message, the T300 timer will be started, and the timer will be

REQUEST message is retransmitted less than the number of times specified by the constant N300, the UE repeats R

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" e

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.



For the dedicated channels, synchronisation primitives are used to indicate the synchronisation status of rad

A UE Layer1 shall check the synchronisation status of every radio frame of downlink and uplink dedicated channels i

a radio link is determined based on the physical channel BER of the DPCCH (The physical channel BER is the relatio

Qout and Qin specify at what DPCCH quality levels the UE shall shut its power off and when it shall turn its power on

The cr i ter ia for report ing sy nchro nisat ion status are def ined in two d if ferent phases.

Phase 1:

-Starts when higher layers initiate physical dedicated channel establishment and lasts until 160 ms after the downlink

-During this time the Out-of-sync status shall not exist-Dur ing th is t ime the In-sync s ta tus shal l be repor ted us ing the CPHY-Sync-IND pr im i t ive i f the fo l lowing cr i te

The UE estimates the DPCCH quality over the previous 40 ms period to be better than a threshold Qin. This criterion

collected. Qin is defined implicitly by the relevant tests. (def. 20% BER) . (The mapping of the Q_IN values to the act

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 shal l be repo rted using the CPHY-Out-of -Sync-IND pr imit ive if ei ther of the fol low ing c r i ter ia are

- The UE estimates the DPCCH quality over the previous 160 ms period to be worse than a threshold Qout. Qout is d

- The 20 most recently received transport blocks with a CRC attached, as observed on all TrCHs using CRC, have be

attached have been received with incorrect CRC. In case of no TFCI is used this criterion shall be considered only for

In-sync shal l be reported u sing th e CPHY-Sync-IND pr imit ive if bo th of the fo l lowing cr i ter ia are ful f i l led:

- The UE estimates the DPCCH quality over the previous 160 ms period to be better than a threshold Qin. Qin is defi

- At least one transport block with a CRC attached, as observed on all TrCHs using CRC, is received in a TTI ending i

CRC attached, this criterion shall be assumed to be fulfilled. In case of no TFCI is used this criterion shall be conside

Uplink synchronisation primitives

Layer 1 in the Node B shall every radio frame check synchronisation status of all radio link sets. Synchronisation stat

CPHY-Out-of Sync IND primitive. Hence, only one synchronisation status indication shall be given per radio link set.T

DPCCH quality or CRC checks. One example would be to have the same criteria as for the downlink synchronisation

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 d

- or when one or several radio links already exist, i.e. when at least one downlink dedicated physical channel is to

In Node B, each radio link set can be in three different states: in i t ia l state , out-of -sync state and in-sync state . Tr

20 last TBs trawith incorrect C

UE Sycnchronization Status

At least one TB in the last radioframe with correct CRC transmitted



Downlink radio link failure/restore

The downlink radio links shall be monitored by the UE, to trigger radio link failure procedures. Radio link failure detect

receiving N313 consecutive "out of sync" indications from layer 1 for the established DPCCH physical channel in FD

->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 bear

Radio Link Monitoring

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 dedicat

in downlink. This corresponds to the case when a dedicated physical channel is initially set up on a frequency.

The radio l ink establ ishment is as fol lows:

a) Node B considers the radio link sets which are to be set up to be in the initial state. UTRAN shall start the transmis

transmitted.The initial downlink DPCCH transmit power is set by higher layers.Downlink TPC commands are generat

b) The UE establishes downlink chip and frame synchronisation of DPCCH, using the P-CCPCH timing and timing off

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 h

uplink DPCCH transmission shall not start before the downlink physical channel has been established and the activat

d) UTRAN establishes uplink chip and frame synchronisation. Frame synchronisation can be confirmed using the fra

in-sync indications are received from layer 1, when Node B shall trigger the RL Restore procedure indicating which ra

shall be considered to be in the in-sync state.The RL Restore procedure may be triggered several times, indicating w

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

set up in the downlink. This corresponds to the case when new radio links are added to the active set and downlink tr

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 ra

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 re

b) UTRAN starts the transmission of the downlink DPCCH/DPDCH at a frame timing such that the frame timing receiv

the UE. Simultaneously, UTRAN establishes uplink chip and frame synchronisation of the new radio link. Frame syncin the initial state shall remain in the initial state until N_INSYNC_IND successive in-sync indications are received fro

obtained synchronisation. When RL Restore is triggered the radio link set shall be considered to be in the in-sync sta

obtained for different radio link sets.

c) The UE establishes chip and frame synchronisation of the new radio link. Frame synchronisation can be confirmed

layers every radio frame.



When the UE starts to set up the dedicated channel, it starts the T312 timer, and after the UE detects N312 synchron

has failed.

->When a physical dedicated channel establishment is initiated by the UE, the UE starts a timer T312 and wait for lay

->On receiving N312 "in sync" indications, the physical channel is considered established and the timer T312 is stopp

->

Uplink radio link failure/restoreThe uplink radio link sets are monitored by the Node B, to trigger radio link failure/restore procedures. Once the radio

those two states are described below.

-The uplink radio link failure/restore criteria is based on the synchronisation status primitives CPHY-Sync-IND and C

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

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_

receiving successive N_INSYNC_IND in-sync indications. If T_RLFAILURE expires, Node B shall trigger the RL Failu

triggered, the state of the radio link set change to the out-of-sync state. During the Out-of-sync state, L1 keeps on se

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 No

synchronisation. When the RL Restore procedure is triggered, the state of the radio link set change to the in-sync sta

After the BTS has established the frame synchronization to the uplink DPCH, the transmission power of the downlink

downlink dedicated physical channel are based on the SIR measurements from the uplink DPCH. (The parameters Q

in the NBAP: CONFIGURATION DATA message)

Example of 3 common cases of L1 Synchonization

ce or up a e. s con ro ng ransparen an unac now e ge mo e earers. s con ro ng ac n

->Timer T314 is started if radio bearer(s) that are associated with T314 exist or if only RRC connection exists, and sto

->Timer T315 is started only if radio bearer(s) that are associated with T315 exist, and stopped when the Cell Update

If T314 expires and T305 is not running, then all radio bearers associated with radio bearers with T314 value are loca

If T315 expires and T305 is not running, then all radio bearers associated with radio bearers with T315 value are loca

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 CE

resent for Radio link reconfiguration (this operation relates to T302 and N302). T314(T315) should be set greater tha

The timer T302 is started when UE transmits CELL UPDATE/URA UPDATE, and stopped when UE receives a CELL

UPDATE/URA UPDATE if the counter V302 is no bigger than the Maximum number of retransmissions of the CELL U



->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 syn

_ _

->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 t

The BTS tries to establish synchronization until timer in RNC expires and RNC sends NBAP:Radio Link Deletion -me



l data to establish, maintain, and release connections. The UE gets informed about the radio bearer characteristics, the

t data via the WCDMA radio interface. The RNC uses the NodeB A ppl icat ion Part (NBAP) protocol to inform the Node B

ging, RRC connection establishment and release, UE capability inquiry, security mode control, Inter-RAT handover

al channel reconfiguration, physical channel failure, etc. can be found here.

ion, active set update, and various handover procedures are covered here.

es of data, associated with these IEs.

P and FDD RF capabilities, radio access capabilities, cell update causes,etc.

rer, such as RB information to setup.

s the description of TFCs and TFCSs.

iption of CCTrCHs or compressed mode information.

re.

RAN.

higher layer protocols in the UE request a signalling connection to UTRAN. Please note, that an RRC connection

ection Setup message. The UE gets all relevant parameters regarding the signalling bearers, transport channels, and

also get all relevant parameters to serve the UE on the radio interface adequately, and to relay data between the Iub-

N specific signalling protocol NBAP to send these parameters to the Node B.

he UE via a FACH.

e to the RNC, using the transport channel DCH. Beforehand it performed a L1 Synchronization.



ection Setup message

accepts the UE„s RRC Connection Establishment request. It starts an interaction with the Node B to establish a radio link

ver the interface Iub. This interaction is also used to inform the Node B about the radio link

parameters for uplink and downlink transmission via the interface Uu. In other words, the Node B is fully

serve as intermediate mode between the mobile phone and the RNC. The UE gets the radio link configuration

with the RRC Connection Setup message, which is transmitted in the transport channel FACH. This message is used to

nalling radio bearers between the UE and the RNC.

nnection Setup message is used to specify the (signalling) radio bearer, the transport channel and the physical channel

cs both in the UL and downlink directions. The RRC Connection Setup message is sent from the RRC layer in the RNC to

er in the UE. The UE„s RRC uses management interfaces to the configure the lower“ layers accordingly.

physical layer characteristics are modified, then the RRC layer only has to interact with the PHY layer. A

may affect scrambling and modulation. A new channelisation code may be deployed for the connection, which

ct to the higher layers. The PHY layer is for instance responsible for radio measurements, and the RNC can

surement quantities or threshold values. Again, this has no impact on the higher layers.

port channels are modified, then this has an effect both on the MAC (Medium Access Control) layer and the

he MAC layer is responsible for Transport Format selection, identification of UEs on the common and shared

iphering and de-ciphering, random access control, etc.

earer is established, or modified, then following layer instances may receive parameters: - Radio Link Control

– for each radio bearer, an RLC instance is established - , - Packet Data Convergence Protocol (PDCP) layer, -

ulticast Control BMC la er instances, - Medium Access Control MAC la er instances, and - PHY la er. With

n this message:

identity to use

se the measurement results are transmitted via the transport channel RACH. The measured quantity can be set by the

measurement result list, are ordered in accordance to the measurement results,



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 byseveral 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:

nnection Setup message, we establish several signalling radio bearers for the UE, so that we won„t see the

and BMC layer relevant parameters.

tablished with this RRC message.

her words the TFCS.r to make the physical channels available.

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.

annels. This was part of the RB setup information. The information carried on radio bearers must be

can higher layer information be segmented? This is described with the information elements for

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

PDUs from several RBs (RLC layers) can be multiplexed on one transport channel. The MAC header of a MAC PDU

DCH, then field C/T is added in the MAC header to identify the logical channel, to which

.



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

annels. One of the PhyCH IEs is the carrier frequency band, where the signalling connection is

r setup. Also the available UL and DL radio resources have to be described.

hen we have a closer look to the IE Downlink information common for all radio links“, we detect

ts on neighbouring cells and at the same time receive data from the active set cells. If this is the case,

s often called Slotted Mode. In order to transmit still the user data with a given data rate, more

lls receive the UE„s signals, only one is making a transmission downlink. The UE tells the active set

his device can decide, how to set the weighting to the individual antennas. There are two different so-

dback command rate is 1 bit per timeslot. - closed loop mode 2: Phase and amplitude adjustments



.

stopped after the UE receives RRC CONNECTION SETUP message. Once the timer times out, if RRC CONNECTION

RC CONNECTION REQUEST; otherwise it will be in the idle mode,consider the procedure to be unsuccessful. The

ual to the value of the variable INITIAL_UE_IDENTITY; and if cell re-selection or expiry of timer T300 occurs;



io links, both in uplink and downlink.

order to detect a loss of the signal on Layer 1, as specified in TS 25.214. The synchronization state of

n of the incorrectly detected pilot bits to the total number of pilot bits in a radio frame), the thresholds

respectively. The synchronisation status is reported to the higher layer.

dedicated channel is considered established by higher layers

r ion is ful f i l led:

shall be assumed not to be fulfilled before 40 ms of DPCCH quality measurements have been

al physical channel BER is given in 3GPP TS 25.133)

ulf i l led:

efined implicitly by the relevant tests(def. 15% BER)

en received with incorrect CRC. In addition, over the previous 160 ms, all transport blocks with a CRC

TrCHs using CRC in all transport formats.

ed implicitly by the relevant tests(def.20% BER)

in the current frame with correct CRC. If no transport blocks are received, or no transport block has a

red only for TrCHs using CRC in all transport formats.

s is indicated to the RL Failure/Restored triggering function using either the CPHY-Sync-IND or

he exact criteria for indicating in-sync/out-of-sync is not subject to specification, but could e.g. be based on received

status primitives.

dicated physical channel are to be set up;

be set up and an uplink dedicated physical channel already exists.

ansitions between the different states is shown in figure above. The establishment of a radio link is

NodeB Radio Link Set States and Transistions

smittedRC transmitted

Out-of-syncstate

In-syncstate

Initialstate

RL Restore

RL Restore

RL Failure



ion in DL is based on counter N313 (counting “out of sync” indicator) and timer T313 in UE. In CELL_DCH State, after

the UE

r can be associated with a bearer re-establishment timer (T314 and T315), which defines the time to re-establish it after a

d physical channel is to be set up in uplink and at least one dedicated physical channel is to be set up

sion of the downlink DPCCH and may start the transmission of DPDCH if any data is to be

d.

set information notified from UTRAN. Frame synchronisation can be confirmed using the frame

igher layers consider the downlink physical channel established. If an activation time has been given,

ion time has been reached. The initial uplink DPCCH transmit power is set by higher layers.

e synchronisation word. Radio link sets remain in the initial state until N_INSYNC_IND successive

dio link set has obtained synchronisation. When RL Restore has been triggered the radio link set

hen synchronisation is obtained for different radio link sets.

DPCCH/DPDCH in the uplink, and at least one corresponding dedicated physical channel shall be

ansmission starts for those radio links.The radio link establishment is as follows:

dio link set this radio link set shall be considered to be in the state the radio link set was prior to the

ain in that state.

ed at the UE will be within T0 +/- 148 chips prior to the frame timing of the uplink DPCCH/DPDCH at

hronisation can be confirmed using the frame synchronization word. Radio link sets considered to bem layer 1, when Node B shall trigger the RL Restore procedure indicating which radio link set has

te.The RL Restore procedure may be triggered several times, indicating when synchronisation is

using the frame synchronization word. Downlink synchronisation status shall be reported to higher

Downlink Direction

Uplink Direction



ization indications from L1, it will stop the T312 timer. Once the timer times out, it means that the physical channel setup

er 1 to indicate N312 "in sync" indications

ed and reset

–

link sets have been established, they will be in the in-sync or out-of-sync states. Transitions between

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

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

IND consecutive out-of-sync indications. Node B shall stop and reset timer T_RLFAILURE upon

re procedure and indicate which radio link set is out-of-sync. When the RL Failure procedure is

rching the synchronization as long as the synchronization has been re-established or the radio link is

de B shall trigger the RL Restore procedure and indicate which radio link set has re-established

te. BTS L3 sends the NBAP:SYNCHRONIZATION INDICATION message to the RNC

DPCH is controlled based on the TPC bits transmitted by the UE. Also, the TPC bits transmitted in the

in and Qout and N_INSYNC_IND, N_OUTSYNC_IND, T_RLFAILURE are given by the RNC to the BTS

ow e ge mo e earers

pped when the Cell Update procedure has been completed.

procedure has been completed.

lly released. If additionally T315 is not running, the UE is moved to the RRC idle mode.

lly released. If additionally T314 is not running, the UE is moved to the RRC idle mode.

L UPDATE CONFIRM before the expiry of the corresponding T314 (or T315), CELL UPDATE will be

T302*N302

UPDATE CONFIRM/URA UPDATE CONFIRM. When it expires, UE should retransmit CELL

PDATE / URA UPDATE message N302, else, goes to idle mode

Successful Synchronization on UL and DL

Downlink Direction

Uplink Direction



chronization

RNC

sage

Failed Synchronization on UL and DL

Downlink Direction

Uplink Direction

ULSynchronization failed because ofno DL synchronization

Downlink Direction

Uplink Direction














>>See More details of 1,2,3

>>Synchronizat ion Parameters Descr ipt ion (Module II)




Radio Bearer(RB) ProceduresThe RB control procedures are used to establish additional radio bearers, modify them, or release them.

Radio Bearer is established, modified, and released with following RRC messages:

1.Radio Bearer Setup,

2.Radio Bearer Reconfiguration, and

3.Radio Bearer Release.

If a radio bearer is setup or reconfigured, not only the RB parameters, but also the transport channel and

physical channel 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



RB Setup, Reconfiguration, and Release

Transport Channel Reconfiguration-on existing RBs




Measurement proceduresThe UE measurements are grouped into 7 different categories, according to what the UE should meas

The dif ferent types of measurements are:

- Intra-frequency measurements: measurements on downlink physical channels at the same frequency as th

- Inter-frequency measurements: measurements on downlink physical channels at frequencies that differ fro

- Inter-RAT measurements: measurements on downlink physical channels belonging to another radio acces

- 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 mea

Cel l s tha t the UE is mon it o r ing (e.g . f o r handover measu remen ts ) a re g rouped in the UE in to th ree d if f

1. Cells, which belong to the active set: User information is sent from all these cells. In FDD, the cells in the

2. Cells, which are not included in the active set, but are monitored according to a neighbour list assig

3. Cells detected by the UE, which are neither included in the active set nor in the monitored set belong

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 ty

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 onl

type 4. The measurement control information is broadcasted with SIB type 12. SIB 4 and SIB 12 are read and

not broadcasted, then SIB 3 resp. SIB 11 parameters are used instead. In the sub-state CELL_DCH, the UE

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

measurement command links a measurement with a measurement identity, quantity, objects, reporting quantit

How does a UE perform measurements after a transition in the CELL_DCH state. Two cases have to b

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

system information, may be included in the SIB 11. If they are included, the UE can send a measurement repo

Control message including one of the above mentioned measurement types, it replaces its internal stored dat



Measurement Control Contents

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

information:

1. Measurement identity: A reference number that should be used by the UTRAN when setting up, modifying

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 abse

. _ _ - .

In the CELL_FACH sub-state, the SIB 12 (or SIB 11, if there is no SIB 12) is valid including all relevant measu

valid, as long as there was no Measurement Control message, which replaces the parameters. But what hap

it then transits to the CELL_FACH sub-state. In the CELL_FACH sub-state, the UE reads SIB 12 (SIB 11), an

CELL_DCH sub-state, the UE resumes with the measurements and associated reporting, as they they were st



The purpose of the measurement reporting procedure is to transfer measurement results fro

Initiation:

In CELL_DCH state, the UE shall transmit a MEASUREMENT REPORT message on the uplink D

measurements that are being performed in the UE.

In CELL_FACH state, the UE shall transmit a MEASUREMENT REPORT message on the uplink D

traffic volume measurement that is being performed in the UE.

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 measure

6. Reporting quantities: The quantities the UE shall include in the report in addition to the quantities that are

7. Measurement reporting criteria: The triggering of the measurement report, e.g. periodical or event-trigger

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 usin

10. Additional measurement identities: A list of references to other measurements. When this measuremen

referenced by the additional measurement identities.

Reception of Measurement Control by the UEThe UTRAN may request a measurement by the UE to be setup, modified or released with a MEASUREMEN

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 n

of setting several "Measurement identity" within a same "Measurement type", "Measurement object" can be se

When a current measurement is modified or released, UTRAN should set the IE "Measurement identity" to the

identity", it is not needed for UTRAN to indicate the IEs other than modifying IEs, and the UE continues to use

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 identi

- for measurement types "inter-RAT measurement" or "inter-frequency measurement":

-->if, according to its measurement capabilities, the UE requires compressed mode to perform the measurem

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 me

identity;

- for any other measurement type: begin measurements according to the stored control information for this me

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 ide

--> 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 variableif 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"): deactiv

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" fo

-->begin the inter-frequency and/or inter-RAT measurements corresponding to the pattern sequence measure

-->if the values of IE "TGPS reconfiguration CFN" and IE "TGCFN" are equal:start the concerned pattern sequ

- 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 varia

- And the procedure ends.

Measurement Report Procedures



In CELL_PCH or URA_PCH state, the UE shall first perform the cell update procedure, using the c

MEASUREMENT REPORT message on the uplink DCCH when the reporting criteria stored in varia

performed in the UE.

The reporting criteria are fulfilled if either:

- the first measurement has been completed for a newly initiated measurement with periodic reporti

- the time period indicated in the stored IE "Periodical reporting" has elapsed since the last measure

- an event in stored IE "Measurement reporting criteria" was triggered. Events and triggering of repo

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 meas

- set the IE "measured results" to include measurements according to the IE "reporting quantity" of t

--> 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

"additional measurements" stored in variable MEASUREMENT_IDENTITY of the measurement that

--> if more than one additional measured results are to be included:sort them in ascending order ac

- if the MEASUREMENT REPORT message was triggered by an event (i.e. not a periodical report):

The UE shall:

- transmit the MEASUREMENT REPORT message on the uplink DCCH using either AM or UM RL

that triggered the report.

When the MEASUREMENT REPORT message has been submitted to lower layers for transmi-The procedure ends.



re. (TS 25.331-360)

e active set.

m the frequency of the active set.

technology than UTRAN, e.g. PDC or GSM.

surement is controlled and reported independently of every other measurement.

rent categor ies:

active set are involved in soft handover.

ed by the UTRAN belong to the monitored set.

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

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

and responsible for cell selection and re-selection. It retrieves the parameters for cell selection from SIB

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

to the UE. This message informs the UE about the type of measurement, which has to be conducted. Each

ies, reporting criteria, type, etc.

distinguished:

Elements, which contain intra-frequency, inter-frequency, inter-RAT and traffic volume measurement

rt, when a measurement reporting criteria is fulfilled. As soon as the UE receives a Measurement

a based on the SIB11 by the parameters delivered with the Measurement Control message.



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

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

itting a MEASUREMENT CONTROL message. The latter message includes the following measurement control

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

nce of the following control information depends on the measurement type

The Measurement Control is used to setup, to modify, and to release a measurement in the UE.

The UE gets all relevant information, how to perform a specific type of measurements. A measurement is either

conducted periodically or driven by an event. Then, the UE returns a measurement report. The MeasurementControl message is transmitted on a DCCH via an RLC entity in the acknowledged mode. I.e. the UE is either in

the RRC connected sub-state CELL_DCH or CELL_FACH. If the setup of a measurement fails, the UE returns

the RRC message Measurement Control Failure. It is transmitted on an UL DCCH via an RLC entity in the acknowledged

mode.

The RRC message Measurement Report was specified to deliver measurement results from the UE to UTRAN

(RNC). This message is transmitted on a DCCH. The RLC entity can be in the acknowledged or unacknowledged

mode. The RLC entity mode is set by the RRC message Measurement Control. Measurement results can be only

transmitted in the CELL_DCH or CELL_FACH sub-state.

- CELL_DCH: If a reporting criterion is met, the UE transmits a Measurement Report. A measurement identity

identifies the measurement as specified by UTRAN. It includes measurement quantities and identifies the

measurement event.-CELL_FACH: In this sub-state, traffic volume measurements and positioning measurements are reported by the

UE. Intra-frequency measurements are reported via the RACH, whereby the UE learns from the BCCH (SIB11 or

SIB12) the maximum numbers of cells, it can report.

-CELL_PCH or URA_PCH: UE must perform a cell update. Cell update cause is uplink data transmission“. Then

they are in the CELL_FACH state, where the Measurement Report can be sent. The measurement report either

holds traffic volume measurements or positioning measurements.

rement control parameters. If the UE transits to the CELL_DCH sub-state, the system information stays

ens, if the UE was in the CELL_DCH sub-state, it has received Measurement Control messages, and

its measurement control parameters become valid. But when the UE then transits back to the

ored before the transition to the CELL_FACH (or any other RRC connected) sub-state.



the UE to UTRAN.

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

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

ents.

mandatory to report for the specific event.

ed reporting.

AM or UM RLC.

t triggers a measurement report, the UE shall also include the reporting quantities for the measurements

CONTROL message, which is transmitted on the downlink DCCH using AM RLC.The UTRAN should take the UE

ot used for other measurements. UTRAN may use several "Measurement identity" for the same "Measurement type". In case

t differently for each measurement with different "Measurement identity ".

value, which is used for the measurement being modified or released. In case of modifying IEs within a "Measurement

the current values of the IEs that are not modified.

ity";

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

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

asurement identity.

ntity indicated by the IE "measurement identity";

EASUREMENT_IDENTITY.

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

r which the "TGPS status flag" is set to "active" at the time indicated by IE "TGCFN"; and

ment purpose of each activated pattern sequence;

ence immediately at that CFN;

ble TRANSACTIONS;

Out-of-syncstateIn-syncstate InitialstateRL Restore RL RestoreRL Failure



use "uplink data transmission", in order to transit to CELL_FACH state and then transmit a

ble MEASUREMENT_IDENTITY are fulfilled for any ongoing traffic volume measurement which is being

g; or

ment report was transmitted for a given measurement; or

rts for different measurement types

rement in variable MEASUREMENT_IDENTITY;

at measurement stored in variable MEASUREMENT_IDENTITY; and

quantity" for all measurements associated with the measurement identities included in the IE

triggered the measurement report; and

ording to their IE "measurement identity" in the MEASUREMENT REPORT message;

et the IE "Event results" according to the event that triggered the report.

according to the stored IE "measurement reporting mode" associated with the measurement identity

ssion:







nc



Click to return t

"Or"

Paging Message Type 1


Paging

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

Paging Type 1 -The RRC message Paging Type 1 is used, when a paging message has to be transmitted to a

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 messa

Cause to the the paging message. Higher layers may also initiate paging, when user data has to be transmitted

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

The UE monitors the paging channels (S-CCPCHs carrying PCCH) on all paging occasions. If the UE receives

message. If so, it returns a paging response. The UTRAN may repeat the transmission of a PAGING TYPE 1 m

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., whe

One example: The user is serving in the Internet, and due to the high download, the RNC has allocated one DD

SGSN exists, and between the two network elements, dedicated transmission resources are available for the us

message to all RNCs, which participate in the LA where the UE is registered. This paging message is received

paging request to the UE. Therefore, Paging Type 2 is often called dedicated paging.

Paging includ

The CN origin

and non co-or

perform the UT

-Co-ordinatiobesides the pa

message shall

URA_PCH stat

shall be trans

-Non-co-ordin

besides the pa

specified pagin

The UTRAN o

a cell update p

a UE to trigger

For a UE in idl

a PAGING TYpaging proced



Click to return tPaging Message Type 2



o main page

>>Pag ing Proce

between UE and UTRAN.

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

ge from the CN has to be forwarded to the UE. . In this case, the UE adds the IE Paging

on an existing ps connection (PMM-IDLE or PMM-CONNECTED). UTRAN has to page the

about system information changes.

paging message, it reads the UE identity to check, whether it is the receiver of the

essage to a UE on several paging occasions message on an appropriate paging

n at least dedicated control channel resources were allocated to the UE.

CH and one DCCH to the user. Consequently, a connection between the UE and the 3G-

er. While the subscriber is serving, he receives a call. The 3G-MSC is sending a paging

y a RNC, which is currently serving the UE. It then uses the existing DCCH to forward the

es CN orignated paging and UTRAN originated paging

ated paging precedure: is used to establish a signaling connection. It is divided into co-ordination paging

ination paging. The CN indicates in the RANAP paging message whether the RNC shall

RAN co-ordination paging

paging, the RNC shall check whether the UE has other CN domain signaling connectionsging domain connection. If so and the UE is in Cell_DCH or Cell_FACH state, the paging

be transmitted on the already connected DCCH on the radio interface. if so and the UE is in Cell_PCH or

e,the paging message shall be transmitted on the PCCH on the radio interface. If no, the paging message

itted on the PCCH.

ating paging, the RNC need not check whether the UE has other CN domain signaling connections

ging domain connection but directly transmit the paging message on the PCCH in the CN

g area.

ignated paing : The UTRAN may initiate paging for a UE in Cell_PCH or URA_PCH state to trgiger

rocedure to enable the transition to Cell_FACH state. In additon,the UTRAN may initiate paging for

reading 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 there by transmitting a PAGING TYPE 2 message on the DCCH



o main page



ure and Parameters Descript ion (Module II)



1

2

1.

2.

3

1.

2.

3.

4.

5.

6.


System Schedul ing Block 2 (SB2)

System Information Block 2 (SIB2)


System Information Block (SIB)

System Information (3GPP-25.331)

Master Information Block (MIB)

System Scheduling Block 1 (SB1)



Scheduling Block (SB)


, , ,

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



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 Monitor Mechanism

System Information Broadcast

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

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

UENode B

UTRAN

RNCNBAP: BCCH



Each step is explained as follows:

1) The RNC sends a NBAP: SYSTEM INFORMATION UPDATE REQUESTmessage 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

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


Cell



System Information Block type 18 Cell

Additonal Information

There is a huge amount of SIBs, which have to be

references and scheduling information about the

For most of the SIBs used within the system, the

corresponding system information has not been meach occurrence (based on Timer). Scheduling in

There are two ways of notifying a UE of syste

1) Notification by a Value Tag

For SIBs using value tags, UTRAN should notify t

- To notify a UE in idle mode, CELL_PCH state

transmit the new MIB value tag.

- To notify a UE in CELL_FACH state, UTRAN s

Upon reception of the PAGING TYPE 1 messag

according to the new MIB value tag.

2) Notification by a Timer

Other types of SIBs have timers respectively. Wh

new SIB information. Notification by a Timer consi

postpone reading the SIB until the content is need

Please note, that UEs in the CELL_DCH sub-st

Actions upon reception of the Master Informati

When selecting a new cell, the UE shall read the

block in the cell.

Action upon reception of the master informati

1. if the "PLMN type" in the variable SELECTED_

- check the IE "PLMN identity" in the master infor

- if the "PLMN type" in the variable SELECTED_P

- store the ANSI-41 Information

2.compare the value tag in the master information

3.if the value tags differ , or if no IEs for the master

and store scheduling information included in the

4. if the value tags are the same the UE may use

valid system information.

System Information Modificatio



For all system information blocks or schedulin

shall perform the following actions:

1.for all system information blocks with area s

->compare the value tag read in scheduling infor

information block;

- if the value tags differ , or if no IEs for the corre

information block into the variable VALUE_TAG; r- if the value tags are the same ,the UE may use

2 for all system information blocks or scheduli

-> compare the value tag read in scheduling infor

that system information block or scheduling block;

- if the value tags differ, or if no IEs for the corre

that system information block or scheduling block

- if the value tags are the same, the UE may use

information.

For system information blocks, not supported by

- skip reading this system information block;

- skip monitoring changes to this system informati

Actions upon reception of system information

The UE may use the scheduling information inclu

acquired.

The UE should only expect one occurrence of the

However, to enable future introduction of new syst

within the scheduling information. The UE may ign

If the UE

- receives a system information block in a position

- this system information block uses a value tag a

the UE shall:

- store the content of the system information block

- consider the content of the system information bl

most for 6 hours after reception.If the UE

- receives a system information block in a position

- this system information block does not use a val

the UE shall:

- store the content of the system information block

- start an expiration timer for that system informat

- consider the content of the system information bl

If the UE

- receives a system information block at a position

- receives a system information block for which sc

- this system information block uses a value tag a

the UE may:

- store the content of the system information block- consider the content of the system information bl

information or at most for 6 hours after reception.

If the UE does not find a scheduling block in a

at that position, the UE shall read the scheduling i

If the UE does not find the master information

the UE shall,

- consider the master information block as not fou

- consider the cell to be barred according to [4] an

"



-



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.

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 i t 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.

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

includes rapidly changed parameters (UL interference and dynamic persistence level. This SIB holds fast changing parameters. Therefore novalue 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

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

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

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.

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 oneof the scheduling blocks

includes ANSI-41 relevant information

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



includes PLMN identity of neighbor cell

read by the UE. This requires a lot of battery power. Therefore, a Master Information Block (MIB) was introduced, which gives

IBs. 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).

IB 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

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 withormation is used to inform the UE, where and when a specific system information is transmitted.

information modification: by a value tag and by a timer

e new value tag for the MIB to the UE.

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

ends a SYSTEM INFORMATION CHANGE INDICATION message on the BCCH to transmit the new MIB value tag.

e or SYSTEM INFORMATCHANGE INDICATION message from UTRAN, the UE shall read the changed information

n the timer expires, the UE shall consider the stored system information content invalid,start the timer, and re-acquire

der the stored system information content invalid, start the timer, and re-acquire new SIB information. The UE may

ed

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

on Block and Scheduling Block(s):

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

n block, the UE shall:

LMN has the value "GSM-MAP" and the IE "PLMN Type" has the value "GSM-MAP" or "GSM-MAP and ANSI-41",:

ation block and verify that it is the selected PLMN, stored as "PLMN identity" in the variable SELECTED_PLMN.

LMN has the value "ANSI-41 "and the IE "PLMN Type" has the value "ANSI-41" or "GSM-MAP and ANSI-41",:

block with the value tag stored for this cell and this PLMN in the variable VALUE_TAG.

information block are stored: store the value tag into the variable VALUE_TAG for the master information block; read

aster information block;

stored system information blocks and scheduling blocks using value tag that were stored in this cell and this PLMN as

Notification



g blocks that are supported by the UE referenced in the master information block or the scheduling blocks, the UE

ope PLMN that use value tags:

ation for that system information block with the value stored within the variable VALUE_TAG for that system

sponding system information block are stored,:store the value tag read in scheduling information for that system

ead and store the IEs of that system information block.stored system information blocks using value tag that were stored in this PLMN as valid system information.

ng blocks with area scope cell that use value tags:

ation for that system information block or scheduling block with the value stored within the variable VALUE_TAG for

sponding system information block or scheduling block are stored,store the value tag read in scheduling information for

into the variable VALUE_TAG; read and store the IEs of that system information block or scheduling block;

stored system information blocks using value tags that were stored in this cell and this PLMN as valid system

the UE, but referenced either in the master information block or in the scheduling blocks, the UE may

on block

blocks:

ed within the master information block and the scheduling blocks to locate each system information block to be

scheduling information for a system information block in the master information block and any of the scheduling blocks.

em information blocks, the UE shall also be able to receive system information blocks other than the ones indicated

ore contents of such system information block.

according to the scheduling information for the system information block; and

cording to the system information block type

together with the value of its value tag in the scheduling information for the system information block; and

lock valid until, if used, the value tag in the scheduling information for the system information block is changed or at

according to the scheduling information for the system information block; and

e tag according to the system information block type

; and

ion block type; and

lock valid until, the expiration timer expires.

different from its position according to the scheduling information for the system information block; or

heduling information has not been received; and

cording to the system information block type

with a value tag set to the value NULL; and lock as valid until it receives the same type of system information block in a position according to its scheduling

position where it should be according to its scheduling information, but a transport block with correct CRC was found

nformation for this scheduling block.

block in a position fulfilling (SFN mod (MIB_REP*4) = 0),(but a transport block with correct CRC was found at that position),

nd.

d

" " " " "



- - , .



UE mode/state when block is valid UE mode/state when block is read

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



Idle mode,CELL_FACH,CELL_PCH,

URA_PCH,CELL_DCHIdle

URA_PCH URA_PCH

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

CELL_FACH, CELL_PCH, URA_PCH CELL_FACH, CELL_PCH, URA_PCH

Idle mode, (CELL_FACH, CELL_PCH, URA_PCH,

CELL_DCH (TDD only))

Idle mode, (CELL_FACH, CELL_PCH, URA_PCH,

CELL_DCH (TDD only))

CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH

(TDD only)

CELL_FACH, CELL_PCH, URA_PCH, CELL_DCH

(TDD only)

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



CELL_DCH CELL_DCH

Idle mode (CELL_FACH, CELL_PCH, URA_PCH,

CELL_DCH)Idle mode (CELL_FACH, CELL_PCH, URA_PCH)

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

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





Idle Mode, CELL_FACH, CELL_PCH, URA_PCH,

CELL_DCH

Idle Mode, CELL_FACH, CELL_PCH, URA_PCH,

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,

CELL_DCHIdle mode, CELL_FACH, CELL_PCH, URA_PCH








Scheduling informationModification of system

information

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

(TDD),SIB_OFF=2Value tag

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

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

Specified by the IE "Scheduling information" Value tag






Specified by the IE "Scheduling information"

ms],SIB_REP *


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









Specified by the IE "Scheduling information"

xp ra on mer =

ms], SIB_REP *

Ex irationTimeFactor

















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 inCELL_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 2 (SIB 2)




















System Information Block 11(SIB 11)












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

value=hex 2dec(0)=0 , h ex2dec(1)=1 --> MNC=01







>>Paging Procedure and Parameters Descr ipt ion (Module II)



value=3000ms

value=3

value=40ms

value=40ms

value=0

value=250ms

value=6s

value=50

value=20s

value=30s

value=inf in i ty

value=2000ms

value=3

value=6s

value=1


value=hex2dec(0065)=101


Cell Identity =RNCid(12bits)+Cellid(16bits) value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 an d Cellid=bin2dec(0111011

value=2dB(step of 2 dB )

>>>Cel l Select ion and Reselect ion Algor i thm and parameters descr ipt ion (Module II)



value=10dB(step of 2 d B)



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


value=-7dB (relat ive to the PCPICH)

value=-6dB (relat ive to the PCPICH)

>>>Cel l Acc ess Restr ic t ion parameters descr ipt ion (Module II)

>>>Cel l Channel Po wer Conf igurat ion Parameters (Module II)

>>>Access Precedures and parameters descr ipt ion (Module II)







value=33dBm

value=-20dBm


value=20attempts

value=8attempts

value=

>>>Open Loo p Pow er Control Algor i thm and parameters descr ipt ion (Module II)










value=-105dBm


Value= InterFreqMeasurem ent is unav ailable

Value= IntraFreqMeasu remen t is based o n CPICH Ec/No

>>> IntrafreqMeasurem ent descripti on (Module II)

>>>see "Parameters descr ipt io n"



value=hex2dec(3b)=59 (Serv ing Cel l 's Pr imary Scrambl ing Code)

value=hex2dec(43)=67(Neighbo ur Cel l 's Pr imary Scrambl ing Code)

Value= InterRATMeasurem ent



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













110010010)=30610




2.NBAP:Radio Link Setup Req

3.NBAP:Radio Link Setup Resp.



NBAP:Synchonization Indicator

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

5.RRC: Uplink Direct Transfer

Start Tx

6.RRC: RRC Connection Setup (FACH)

L1 Synch onization

1.RRC: RRC Connection Release

L3 Messages - Location Upd

UE NodeB S-R

1.RRC: RRC Connection Request (RACH)

Start Rx

5.ALCAP: Iub User Plane Setup

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

7.RRC: RRC Connection Setup Completed (DCH)

2.RRC: RRC Connection Release Complete

Optional : Authentication and Securitty Mode Control may exist depends on



3.NBAP: Radio Link Deletion

Request

. : a o n e et on

Response


ALCAP: Iub User Plane Release

Note the fo l lowing in format ion about th e 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 afterradio links are set up or deleted.



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

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

6.RANAP: Direct Transfer

1.RANAP: Iu Release Command

2..RANAP: Iu Release Complete

ate Procedure

C

>>RRC Pro

CN

ALCAP: Iu User Plane Release

RRC Con

Locat ion

Iu relea

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



RRC conn



The Iu release procedure is performed for the CN to release an

The location update procedure is performed to update the loca

Triggering Conditions : An RRC connection is set up between the

The procedure is descr ibed as fo l lows:

1.The UE sends an INITIAL DIRECT TRANSFER message to the S

2.The SRNC sends an INITIAL UE MESSAGE to the CS service do

Mobile Subscriber Identity (TMSI),International Mobile Subscriber Id

routing area update. The message indicates ATTACH REQUEST a

3.The CN updates the location area information of the UE and save

indicates LOCATION UPDATE ACCEPT and contains the TMSI tha

authentication and ciphering. Then, the CN sendsa DIRECT TRANS

4.The SRNC transparently sends the contents of the DIRECT TRAN

5.The UE receives the LOCATION UPDATE ACCEPT information aarea update, it is the ATTACH ACCEPT information that the UE rec

6.The SRNC transparently sends the contents of the UPLINK DIRE

For routing area update, it is ATTACH COMPLETE that the DIR

RRC connection setup procedure is performed for the UE to s

Triggering Conditions : The UE in idle mode intitiates the RRC

When the SRNC receives an RRC CONNECTION REQUEST mess

If accepting the request, the RRM module further determines wheth

the DCH.

The procedure shown is descr ibed as fo l lows:

1.The UE sends an RRC CONNECTION REQUEST message to the

2.Based on the cause in the RRC connection request and the syste

resources, and L1 and L2 resources. Then the SRNC sends a RADI

resources required for an RRC connection.

3.The NodeB responds with a RADIO LINK SETUP RESPONSE me

4.The SRNC uses the ALCAP protocol to set up the Iub user plane t

for the ATM-based Iub interface only.5.The SRNC sends an RRC CONNECTION SETUP message to the

6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:S

7. The UE sends an RRC CONNECTION SETUP COMPLETE mes

RRC connection setup procedure ends.

If the RNC judges that the RRC connection request cannot be set u

indicates the reject reason in the message

edure description

ect ion Setup

Update

e



r gger ng on t ons: e u re ease proce ure can e tr ggere

example,sending an IU RELEASE REQUEST message,The Serving


1.The CN sends an IU RELEASE COMMAND message to the SRN

NOTE After sending the IU RELEASE COMMAND message, the C

2.The SRNC releases the related UTRAN resources and then sends

The RRC Connection Release procedure is performed to release

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

release procedure.

The procedure shown is descr ibed as fo l lows: based on the res

connection from DCH and release of an RRC connection from CCH

connection on the CCH is released)

1.The SRNC sends an RRC CONNECTION RELEASE message to

(NOTE: The SRNC may send the RRC CONNECTION RELEASE

and the transmission intervals are determined by the SRNC. If the S

COMPLETE message from the UE after sending the RRC CONNE

2.The UE sends an RRC CONNECTION RELEASE COMPLETE m

3.The SRNC sends a RADIO LINK DELETION REQUEST message

4.After releasing the resources, the NodeB sends a RADIO LINK DE

5.(Optional; required for the ATM-based Iub interface only) The SRN

ends.

ection Release



Iu connection and all the UTRAN resources related only to that Iu connection.

tion of a UE.

UE and the Serving RNC (SRNC)

NC through the RRC connection. The message contains the Non Access Stratum (NAS) information to be

ain of the CN through the Iu interface. The message indicates LOCATION UPDATE REQUEST and contai

ntity (IMSI), and Location Area Identity (LAI).The SRNC sends an INITIAL UE MESSAGE to the PS service

d contains the Routing Area Identity (RAI)

the new LAI. The CN might also perform authentication and ciphering. Then, the CN sends a DIRECT TRA

is assigned to the UE.For routing area update, the CN updates the routing area information of the UE and s

FER message to the SRNC. The message indicates ATTACH ACCEPTand contains the TMSI that is assig

SFER message to the UE through a DOWNLINK DIRECT TRANSFER message.

nd sends an UPLINK DIRECT TRANSFER message to the SRNC. The message contains the information sives.

T TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSFER me

CT TRANSFER message indicates.

et up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has

onnection setup procedure when the NAS of the UE requests the establishment of a signaling connection

age from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to acce

r to set up the RRC connection on a Dedicated Channel (DCH)or on a Common Channel (CCH), based on

SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.

resource status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio N

O LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link

ssage to the SRNC after successfully preparing the resources.

ransport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is opti

UE through the downlink CCCH (FACH). The message contains the information about the DCH allocated b

ynchonization Indicator message to SRNC when the uplink enter "In-Sync" state

age to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message in

(for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to



n one o t e o ow ng con t ons: e transact on etween t e an t e s comp ete, e req

Radio Network Subsystem (SRNS) is relocated.4.The SRNS relocation is canceled after a relocation resou

to initiate the Iu release procedure. The message indicates the cause for the release of the signaling conn

will not send further RANAP connection-oriented messages on this particular connection.

an IU RELEASE COMPLETE message to the CN.

he signaling connection and all radio bearers between UE and the UTRAN

whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not

uce occupied by the RRC connection,there are two types of RRC connection release procedure: release of

(If an RRC connection needs to be released after a successful outgoing call,, the RRC connection on the D

the UE through the DCCH.

essage several times to increase the probability of proper reception of the message by the UE. The RRC S

RNC does not receive an RRC CONNECTION RELEASE

TION RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)

ssage to the SRNC.

to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.

LETION RESPONSE message to the SRNC.

C uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC



sent to the CN by the UE.

nsthe UE information, such as the Temporary

domain of the CN throughthe Iu interface for

NSFER message to the SRNC. The message

avesthe new RAI. The CN might also perform

ed to the UE

uchas the NAS information and the CN ID.For routing

sageindicates TMSI REALLOCATION COMPLETE.

a maximum of one RRC connection at a time.

t or reject theRRC connection request, based on a specific algorithm.

a specific RRM algorithm. Typically, an RRC connection is set up on

etworkTemporary Identity(RNTI),radio

onal. It is required

y the SRNC.

dicates that the

he UE, and



ests t e to re ease t e resources on t e u nter ace y, or

rce allocation procedure iscomplete.

ction.

carry other RAB of the UE,the SRNC initiates an RRC connection

an RRC

H is released and if a radio bearers fails to be setup ,the RRC

s of these messages are the same. The number of retransmissions

connection release procedure




value=

value=

value=

value=

value=(

value=

value=

RRC:RRC Connection Request (RACH)

>>"Geo

>>"RRC



value=

value=

value=

value=

RRC:RRC Connection Setup (FACH)

>>"Geo

>>"RRC



value=

value=

value=



value=



value=





value=









value=

value=

value=(

value=

value=

value=



value=

value=

value=

Cell Ide



value=

RRC:RRC Connection Setup Complete (DCCH) >>"RRC



value=

value=

value=

value=



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



ex2d ec(4)=4 , hex 2dec (5)=5 ,hex2d ec(6)=6 --> MCC=456

ex2d ec(0)=0 , hex 2dec (2)=2 --> MNC=02

ex2dec(75 AA )= 30122

regist rat ion(Locat ion update)

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

ex2dec(91)=145 (Neighbour 's Pr imary Scrambl in g Code)

PICH Ec/Io inv alid

raphical and UTRAN En ti ty Ident i f iers"

Connect ion Request Descr ipt ion"



ex2d ec(4)=4 , hex 2dec (5)=5 ,hex2d ec(6)=6 --> MCC=456

ex2d ec(0)=0 , hex 2dec (2)=2 --> MNC=02

ex2dec(75 AA )= 30122

E capable to sup port FDD , not TDD

raphical and UTRAN En ti ty Ident i f iers"

Connect ion Setup Descr ipt ion"



E capable to suppo rt GSM

ignal ing Radio Bearer Informat ion Setup ,RB-1

adio Bearer Mapping




















LER Target= -20 dB

axAl lowedULTxPow er=24 dBm

-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

use Closed Loop Power Cont ro l A lgor i thm1

use long SC on Upl ink

preading Factor 64 (Upl ink)



preading Factor 128 (Down l ink)

r imary Scrambl ing c ode=385

preading Factor 128 (Down l ink)

ntity=RNCid(12bits)+Cell id(16bits)



00000000001 0101101011001010 => RNCid=bin2dec(000000000001)=1 an d Cellid=bin2dec(011101111001

Connect ion Setup Com plete Descr ipt ion"



UE (Powerclass3) maximum transm it ted power =24 dBm

sup por t GSM (Dual Mode UMTS<>GSM)

Chiper ing Algor i thm A 5/3

suppo rt Compressed Mode (CM) upl ink and do wnl ink



value= MCC=456



value= MNC=02

value=hex2dec(75AA)=30122





























PCPICH Power UL Interference UL DPCCH Initial Power

33 -85 633 -85 -4

UE in RRC Connection Setup.





010)=23242












































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


6.RRC: Security Mode Command

L3 Messages - AMR Voice (MOC

UE NodeB S-R


Start Rx


Start Tx

7.RRC: Security Mode Completed

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


L1 Synch onization

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

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



3.NBAP: Radio LinkReconfiguration Prepare

4.NBAP: Radio Link

Reconfiguration Ready

7.NBAP: Radio Link

Reconfiguration Commit

RRC:Measurement Report

Call Establ ish ed

8.RRC: Radio Bearer Setup Complete


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

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

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

Intra-Frequency Soft Handover

Inter-Frequency Hard Handover

Inter-RAT Hard Handover

RRC:Measurement Control

6.RRC: Radio Bearer Setup

Apply new transport format set

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




Request


Response


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

5,.ALCAP: Iub User Plane Release

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

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

2.RRC:RRC Connection Release Complete

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




SCCP: CR (Connection Request)

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

3.SCCP: CC (Connection Confirm)

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

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

RANAP: Common ID (IMSI)

5.RANAP: Security Mode Command

8.RANAP: Security Mode Complete

2.RANAP: Direct Transfer (CC: Setup)

Call Procedure

C

>>RRC Proc

CN

1.RRC Co

2.Signalli

3.AuthenSecurity



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

1.RANAP: RAB Assignment Request

2.ALCAP : Iu User Plane Setup

9.RANAP: RAB Assignment Response

6.RANAP: Direct Transfer (CC: Alerting)

8.RANAP: Direct Transfer (CC: Connect)

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

6.Convers

4.Cal

5. Radio Be



2.RANAP: Direct Transfer (CC: Disconnect)

3.RANAP: Direct Transfer (CC: Release)

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


9.RANAP: Iu Release Complete

8.ALCAP: Iu User Plane Release

7.Call R

8.RRC C



RRC connection setup procedure is performed for the UE to set up a

connection at a time.

Triggering Conditions : The UE in idle mode intitiates the RRC connect

REQUEST message from the UE, the Radio Resource Management (RRM)

algorithm. If accepting the request, the RRM module further determines wh

algorithm. Typically, an RRC connection is set up on the DCH.


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

2.Based on the cause in the RRC connection request and the system resou

Identity(RNTI),radio resources, and L1 and L2 resources. Then the SRNC s

required for an RRC connection.

3.The NodeB responds with a RADIO LINK SETUP RESPONSE message t

4.The SRNC uses the ALCAP protocol to set up the Iub user plane transpor

for the ATM-based Iub interface only.5.The SRNC sends an RRC CONNECTION SETUP message to the UE thr

6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchoni

7. The UE sends an RRC CONNECTION SETUP COMPLETE message to

RRC connection setup procedure ends.

If the RNC judges that the RRC connection request cannot be set up (for in

The signaling connection setup procedure is performed to exchang

Triggering Conditons: The UE sends a direct transfer message to initiate


1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC th

2.The SRNC receives the INITIAL DIRECT TRANSFER message from the

to be sent to the CN by the UE. The content of the NAS information is CM

3.The CN sends a response message to the SRNC.

-If accepting the request, the CN sends a CONNECTION CONFIRM (CC)

confirms that the signaling connection is set up.

-If rejecting the request, the CN sends a CONNECTION REJECT (CJ) m

confirms that the signaling connection fails to be setup and then initiates th

The authentication and security mode control procedure is perfo

algorithm and ciphering algorithm. This procedure ensures integrity and cor

Triggerring Conditions: The UE and the CN exchange signaling. The net


1.The CN sends a DIRECT TRANSFER message to the SRNC. The messa

2.The SRNC transparently sends the contents of the DIRECT TRANSFER

3.The UE sends an UPLINK DIRECT TRANSFER message to the SRNC.

edure Description

nnection Setup

ng Connection Setup

tication & Mode Control



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

Triggering Conditions: The UE initiates a call



2.The SRNC transparently sends the contents of the UPLINK DIRECT TRA



5. A Radio Access Bearer (RAB) is set up. (see more details in RAB Setup

6. When the called terminal rings, the CN sends a DIRECT TRANSFER me





11.The SRNC transparently sends the contents of the UPLINK DIRECT TR

The Radio B earer Setup p rocedure shown is descr ibed as fo l lows:

1.The CN sends an RAB ASSIGNMENT REQUEST message to the SRNC

2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNC

characteristic parameters. Based on the AAL2 link characteristic parameter

3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE mess

4.The NodeB allocates the associated resources and then sends a RADIO

5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP

by exchanging uplink and downlink synchronization frames in the DCH fram

6.The SRNC sends a RADIO BEARER SETUP message to the UE.

7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT messa

8.After performing the radio bearer setup, the UE sends a RADIO BEARER

9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to the C

The procedure when RAB Setup Fai lure shown is d escr ibed as fo l lows




Subscriber Identity Module (USIM) judges that the authentication is success

5.The CN sends a SECURITY MODE COMMAND message to the SRNC to

protection algorithms.

6.The SRNC sends a SECURITY MODE COMMAND message to the UE to

7.The UE sends a response message to the SRNC.

- If the in tegr i ty protect ion and cipher ing algor i thms are conf igured su

MODE COMMAND COMPLETE message to the CN.The message contain- If the UE does not s upport the in tegr i ty protect ion and cipher ing algo

information and the reason for the failure. The SRNC then sends a SECURI

The call release procedure is performed to release services and resou

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

The procedure shown is described as follows:



ation

l Setup

arer Setup



The RRC Connection Release procedure is performed to release the sign

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

RRC connection release procedure.

The procedure shown is descr ibed as fo l lows: based on the resouce oc

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

fails to be setup ,the RRC connection on the CCH is released)

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

(NOTE: The SRNC may send the RRC CONNECTION RELEASE message

the same. The number of retransmissions and the transmission intervals ar

UE after sending the RRC CONNECTION RELEASE message for four tim

2.The UE sends an RRC CONNECTION RELEASE COMPLETE message

3.The SRNC sends a RADIO LINK DELETION REQUEST message to the

4.After releasing the resources, the NodeB sends a RADIO LINK DELETIO

5.(Optional; required for the ATM-based Iub interface only) The SRNC uses

procedure ends.





7.The CN sends an IU RELEASE COMMAND message to the SRNC to req

8.(Optional; applicable to the ATM-based Iu-CS interface only) The ALCAP

9.The SRNC sends an IU RELEASE COMPLETE message to the CN.

elease

onnection Release



signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a ma

ion setup procedure when the NAS of the UE requests the establishment of a signaling connection When t

module of the RNC determines whether to accept or reject theRRC connection request, based on a speci

ther to set up the RRC connection on a Dedicated Channel (DCH)or on a Common Channel (CCH),based

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 Networ

ends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the spe

o the SRNC after successfully preparing the resources.

t bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. I

ough the downlink CCCH (FACH). The message contains the information about the DCH allocated by the

zation 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 indicate

tance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to the U

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 and sends an INITIAL UE MESSAGE to the CN over the Iu interface. The INITIAL UE MESSAGE cont

ERVICE REQUEST.

message to the SRNC. The message indicates that the SCCP connection is set up. After receivingthe me

ssage to the SRNC. The message indicates that the SCCP connection fails to be set up. After receiving th

RRC release procedure.

rmed for the UE and the network to implement bi-directional authentication and to negotiate and configure

ectness of signaling

ork initiates the authentication and securitymode control procedure

ge indicates AUTHENTICATION REQUEST.

essage to the UE through a DOWNLINK DIRECT TRANSFER message.



he message contains the number of the called party and the information about the bearer capability of the

NSFER messageto the CN through a DIRECT TRANSFER message.

ge indicates CALL PROCEEDING and contains the information about the negotiated bearer capability of t


rocedure below)

ssage to the SRNC. The message indicates ALERTING.


ge indicates CONNECT, which means that the called party has answered the call.


NSFER message to the CN through a DIRECT TRANSFER message, indicating CONNECT ACKNOWL

to initiate the RAB setup procedure.

aps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and r

,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure.

ge to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio link

INKRECONFIGURATION READY message to the SRNC.

at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perfo

e protocol.

e to theNodeB.

SETUP COMPLETE message to the SRNC.

. The RAB isset up.

:


. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.

NSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RES

ful, the UE returns a message with an XRES IE.

initiate the security mode control procedure. The message contains the information about the supported c

inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.

cessfu l ly , the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The SRN

the information about the integrity protection and ciphering algorithms that the UE uses. i thms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The message c

TY MODE COMMAND REJECT message to the CN

ces after a call ends.

NSFER messageto the CN through a DIRECT TRANSFER message, indicating DISCONNECT. This cont



aling connection and all radio bearers between UE and the UTRAN

r the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry

cupied by the RRC connection,there are two types of RRC connection release procedure: release of an R

r 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 t

e determined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE COMPLETE

s, the SRNC judges that the UE has released the RRC connection.)

o the SRNC.

odeB,requesting the NodeB to delete the radio link resources in the NodeB.

RESPONSE message to the SRNC.

the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC conn

ge indicates RELEASE to request release of the call.


NSFER messageto the CN through a DIRECT TRANSFER message, indicating RELEASE COMPLETE.

uest call release on the Iu interface. The message indicates the reason for the Iu release

protocol on the Iu interface initiates an Iu data transport bearer release procedure.



imum of one RRC

he SRNC receives an RRC CONNECTION

ic

on a specific RRM

Temporary

ific radio link resources

t is required

RNC.

s that the

, and indicates the reject

E.

ins the NAS information

ssage, the SRNC

e message, the SRNC

he integrity protection



call.

e call.

DGE.

dio resource

for carrying the RAB.

rm synchronization

ONSE. If the UMTS

iphering and integrity

C then sends a SECURITY

ntains the error

nt informs the CN that the UE has hanged up.



other RAB of the UE,the SRNC initiates an

C connection from DCH and release of an

hese messages are

message from the

ction release




value

value

value

valu e

value

value

value

RRC:RRC Connection Request (RACH) >>" RR

>>" Ge



value

value

value

RRC:RRC Connection Setup (FACH) >>" RR

>>" Ge



value

value

value

value



value





value



value









value

value

value

valu e

valu e



value

value

value



value

Cell Id

value

RRC:RRC Connection Setup Complete (DCCH) >>" RR



valu e

valu e



valu e

valu e

valu e

valu e





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

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



RRC: Uplink Direct Transfer (MM: Authentication Response)

RANAP: Direct Transfer (MM: Authentication Request)

RRC: Downlink Direct Transfer (MM: Authentication Request)



RANAP: Direct Transfer (MM: Authentication Response)

RRC: Security Mode Command



RANAP: Direct Transfer (CC: Setup)

RRC: Security Mode Complete



RRC: Uplink Direct Transfer (CC: Setup)



RRC: Downlink Direct Transfer (CC: Call Proceeding)

RANAP: Direct Transfer (CC: Call Proceeding)



RRC: Radio Bearer Setup



























RANAP: Direct Transfer (CC: Alerting)

RRC: Radio Bearer Setup Complete



RRC: Downlink Direct Transfer (CC: Connect)

RRC: Downlink Direct Transfer (CC: Alerting)

RANAP: 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)



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

RANAP: Direct Transfer (CC: Release Complete)

RRC: Uplink Direct Transfer (CC: Release Complete)



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



hex 2dec (5)=5 , hex 2dec (2)=2 ,hex2d ec(0)=0 --> MCC=520

hex 2dec (0)=0 , hex 2dec (1)=1 --> MNC=01

hex2d ec(2908)= 10504

Originat ingCo nversat ionalcal l (CS MOC)

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

hex2dec(60)=96(Neighbour 's Pr imary Scramb l ing Code)

CPICH Ec/Io in valid


graphical and UTRAN Enti ty Ident i f iers"





hex2d ec(2908)= 10504





UE capable to supp ort FDD , not TDD

UE capable to suppo rt GSM

Signal ing Radio Bearer Informat ion Setup ,RB-1

Radio Bearer Mapping




















BLER Target= -20 dB

MaxAl lowedULTxPower=24 dBm

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

-22 -94 -80

-22 -94 -70

Note :DPCCH_Power_offset is configured by RNC and delivered t





Spreading Factor 64 (Upl ink)

Spreading Factor 128 (Downl ink )

Pr imary Scrambl ing cod e=97




entity=RNCid(12bits)+Cellid(16bits)


Connect ion Setup Com plete Descr ipt ion"



not su ppo rt GSM (Locked UMTS Mode)

Chiper ing Algor i thm A5/3



UE suppo rt Band fdd 2100 MHz

UE (Powerclass3) maximum transmit ted pow er =24 dBm















value= Call B-Party numb er = 0812713339





>>"Radio Bearer Descript io n"

























value= SF64(uplin k)-> AMR 12.2

value=Primary Scrambl in g co de=97



value= SF128(down link )-> AMR 12.2

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

value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 an d Cel l id=bin2de




































33 -105 -14

33 -105 -24






10)=30610















































(0111011110010010)=30610






















































































*** The different messages between MOC & MTC are highlighted in "Red" color





1. RRC: RRC Connection Request (RACH)



4. ALCAP: Iub User Plane Setup

Start Tx

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


5. RRC: RRC Connection Setup (FACH)

6. RRC: RRC Connection Setup Completed (DCH)

Start Rx

2. RRC: Paging Type 1


L3 Messages -AMR Voice Call (M

L1 Synchonization

UE NodeB S-



. : a o n

Reconfiguration Prepare

4. NBAP: Radio Link


7. NBAP: Radio Link


RRC: Uplink Direct Transfer (CC: Release)



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

Call Establ ish ed

RRC: Downlink Direct Transfer (CC: Disconnect)

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


8. RRC: Radio Bearer Setup Complete

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

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

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

5. ALCAP: Iub User Plane Setup

6. RRC: Radio Bearer Setup



: a o n e et on

Request

NBAP: Radio Link Deletion

Response



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 theIu-CS

interface after an RAB is set up or a call is released





RRC: Downlink Direct Transfer (CC: Release Complete)





1. RANAP: Paging

2.SCCP: CR (Connection Request)

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







>>RRC Proc

C) Call Procedure

NC CN

2.RRC C

3.Signal

4.AutheMode C

1.Paging



1. RANAP: Direct Transfer (CC: Setup)

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

1. RANAP: RAB Assignment Request

2. ALCAP: Iur User Plane Setup


7. RANAP: Direct Transfer (CC: Alerting)

9. RANAP: Direct Transfer (CC: Connect)

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



6.Conve

4.Cal

5.Radio




RANAP: Iu Release Command

RANAP: Iu Release Complete

ALCAP: Iur User Plane Release

7.Call R

8.RRC





The signaling connection setup procedure is performed to

Triggering Conditions: The UE sends a direct transfer me


RRC connection setup procedure is performed for the UE to

maximum of one RRC connection at a time.

Triggering Conditions: The UE in idle mode intitiates the RRC

When the SRNC receives an RRC CONNECTION REQUEST me

reject theRRC connection request, based on a specific algorithm. I

Channel (DCH)or on a Common Channel (CCH), based on a speci

The procedure shown is descr ibed as fo l lows: 1.The UE sends an RRC CONNECTION REQUEST message to t

2.Based on the cause in the RRC connection request and the syst

NetworkTemporary Identity (RNTI), radio resources, and L1 and L

NodeB to allocate the specific radio link resources required for an

3.The NodeB responds with a RADIO LINK SETUP RESPONSE

4.The SRNC uses the ALCAP protocol to set up the Iub user plane

It is required for the ATM-based Iub interface only.

5.The SRNC sends an RRC CONNECTION SETUP message to t

SRNC.

6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:

7. The UE sends an RRC CONNECTION SETUP COMPLETE me

indicates that the RRC connection setup procedure ends.If the RNC judges that the RRC connection request cannot be set

edure Description

Paging Procedure The paging procedure is performed when th

Triggering Conditions: A Terminal calls the UE

The Paging Proc edure in Idle, Cel l_PCH and URA-PCH mo des

1.The CN sends a PAGING message to the SRNC.

2.The SRNC initiates the paging procedure by sending a PAGING

paging occasion is related to the International Mobile Subscriber Id

proper receptionof the paging message by the UE.)

3.The UE in idle mode or in PCH state monitors the paging and re

Th e Pag in g Pro ced ur e in Cel l_DCH an d Cell_FACH mod e is d

1.The CN sends a PAGING message to the SRNC.

2.The SRNC initiates the paging procedure by sending a PAGING

3.The UE receives the PAGNG TPYE 2 message, reads it, and the

procedure ends onnectionSetup

ling Connection Setup

ntication & Securityontrol



Call Setup Procedure(Incoming Call) is performed to setup

Triggering Conditions : A UE receiveds a call from the CN


1.The CN sends a DIRECT TRANSFER message to the SRNC. T

2.The SRNC transparently sends the contents of the DIRECT TRA

3.The UE sends an UPLINK DIRECT TRANSFER message to the

4.The SRNC transparently sends the contents of the UPLINK DIRmessageindicates CALL CONFIRM and contains the information a

5. A Radio Access Bearer (RAB) is set up. (see more details in RA

6. The UE sends an UPLINK DIRECT TRANSFER message to the

7.The SRNC transparently sends the contents of the UPLINK DIR

called terminal to ring.



meansthat the called party has answered the call.

1.The UE sends an INITIAL DIRECT TRANSFER message to the

UE.

2.The SRNC receives the INITIAL DIRECT TRANSFER message

contains the NAS information to be sent to the CN by the UE. The


-If accepting the request, the CN sends a CONNECTION CONFI

message, the SRNC confirms that the signaling connection is set

-lf rejecting the request, the CN sends a CONNECTION REJECmessage, the SRNC confirms that the signaling connection fails t

The authentication and security mode control procedur protection algorithm and ciphering algorithm. This procedure ensur

Triggerring Conditions: The UE and the CN exchange signaling.



2.The SRNC transparently sends the contents of the DIRECT TRA3.The UE sends an UPLINK DIRECT TRANSFER message to the


RESPONSE. If the UMTS Subscriber Identity Module (USIM) judg

5.The CN sends a SECURITY MODE COMMAND message to the

ciphering and integrity protection algorithms.

6.The SRNC sends a SECURITY MODE COMMAND message to


-If the i n teg r it y pro tect ion and c ipher ing al gor it hms are con fi g

then sends a SECURITY MODE COMMAND COMPLETE messa

UE uses.

-If the UE does no t suppo r t the in teg r it y p rotec t ion and c i pher

contains the error information and the reason for the failure. The S

The RANAP:Common ID messa e is used to trans ort the er

rsation

ll Setup

earer Setup



The RRC Connection Release procedure is performed to releas

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

other RAB of the UE,the SRNC initiates an RRC connection releas

The procedure shown is descr ibed as fo l lows: based on the re

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

bearers fails to be setup ,the RRC connection on the CCH is relea

1.The SRNC sends an RRC CONNECTION RELEASE message t

(NOTE: The SRNC may send the RRC CONNECTION RELEASE

these messages are the same. The number of retransmissions an

RELEASE COMPLETE message from the UE after sending the R

connection.)

. .

11.The SRNC transparently sends the contents of the DIRECT TR

The Radio Bearer Setup pro cedure shown is desc ribed as fol l

1.The CN sends an RAB ASSIGNMENT REQUEST message to t

2.(Optional; applicable to the ATM-based Iu-CS interface only) The

radio resource characteristic parameters. Based on the AAL2 link

3.The SRNC sends a RADIO LINK RECONFIGURATION PREPA

links for carrying the RAB.4.The NodeB allocates the associated resources and then sends a

5.(Optional; required for the ATM-based Iub interface only) The Iub

perform synchronization by exchanging uplink and downlink synch

6.The SRNC sends a RADIO BEARER SETUP message to the U

7.The SRNC sends a RADIO LINK RECONFIGURATION COMMI

8.After performing the radio bearer setup, the UE sends a RADIO

9.The SRNC sends an RAB ASSIGNMENT RESPONSE messag

The procedure when RAB Setup Fai lure shown is descr ibed a

1.The CN sends an RAB ASSIGNMENT REQUEST message to th

2.The SRNC sends an RAB ASSIGNMENT RESPONSE message

The Call Release procedure is performed to release servic

Triggering Conditions: A call ends and the calling party ha






RELEASE which requests release of the call.



7.The CN sends an IU RELEASE COMMAND message to the SR

8.(Optional; applicable to the ATM-based Iu-CS interface only) The

9.The SRNC sends an IU RELEASE COMPLETE message to the

lease

onnection Release



2.The UE sends an RRC CONNECTION RELEASE COMPLETE

3.The SRNC sends a RADIO LINK DELETION REQUEST messa

4.After releasing the resources, the NodeB sends a RADIO LINK

5.(Optional; required for the ATM-based Iub interface only) The S

connection release procedure ends.



exchange the NAS (Non Access Stratum) information between the UE and the CN.

sage to initiate the signaling connection setup procedure.

set up a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE h

connection setup procedure when the NAS of the UE requests the establishment of a signaling connection

sage from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to ac

f accepting the request, the RRM module further determines whether to set up the RRC connection on a D

ific RRM algorithm. Typically, an RRC connection is set up on the DCH.

e SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.

m 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 t

RC connection.

essage to the SRNC after successfully preparing the resources.

transport bearer and performs the synchronization between the SRNC and the NodeB. This procedure is o

e UE through the downlink CCCH (FACH). The message contains the information about the DCH allocate

Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state

ssage to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message

p (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message

CN calls a UE.

i s descr ibed as fo l lows;

TYPE 1 message to the UE through the Paging Control Channel (PCCH) on an appropriate occasion.(NOT

entity (IMSI) of the UE. The UTRAN may page the same UE on several occasions to increase the probabilit

eives the paging message from the network layer.The paging procedure ends.

scr ibed as fo l lows;

TYPE 2 message to the UE through the DCCH.

n reports to the NAS the information such as the paging cause and the paging record type identifier.The pa



call.

e message indicates SETUP and contains the number of the calling party and the bearer capability of the

NSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.

SRNC.

CT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSFERbout the negotiated bearer capability of the call.

B Setup Procedure below)

SRNC.

CT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating ALERTING to req

SRNC.

CT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating CONNECT. This

SRNC through the RRC connection. The message contains the initial NAS information to be sent to the CN

rom the UE and sendsan INITIAL UE MESSAGE to the CN through the Iu interface. The INITIAL UEMESS

content ofthe NAS information is PAGING RESPONSE .

RM (CC) message tothe SRNC. The message indicates that the SCCP connection is set up. After receivin

p.

(CJ) message to the SRNC. The message indicates that the SCCP connection fails to be set up. After recbe setup and then initiates the RRC release procedure.

is performed for the UE and the network to implement bi-directional authentication and to negotiate and c

es integrity and correctness of signaling.

The network initiates the authentication and securitymode control procedure

e message indicates AUTHENTICATION REQUEST.

NSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.SRNC.

CT TRANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATI

s that the authentication is successful, the UE returns a message with an XRES IE.

SRNC to initiate the security mode control procedure. The message contains the information about the sup

the UE to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.

ured successfu l ly , the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC.

e to the CN.The message contains the information about the integrity protection and ciphering algorithms t

ing algor i thms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The me

RNC then sends a SECURITY MODE COMMAND REJECT message to the CN

manent UE Identit IMSI to SRNC



the signaling connection and all radio bearers between UE and the UTRAN

s whether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does

e procedure.

souce occupied by the RRC connection,there are two types of RRC connection release procedure: release

connection needs to be released after a successful outgoing call,, the RRC connection on the DCH is rele

ed)

the UE through the DCCH.

message several times to increase the probability of proper reception of the message by the UE. The RRC

the transmission intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNEC

C CONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC

.

ANSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.

ws:

e SRNC to initiate the RAB setup procedure.

SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic paramete

haracteristic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup pro

RE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing r

RADIO LINKRECONFIGURATION READY message to the SRNC.

ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SR

onization frames in the DCH frame protocol.

.

message to the NodeB.

EARER SETUP COMPLETE message to the SRNC.

to the CN. The RAB isset up.

fo l lows:

e SRNC to initiate the RAB setup procedure.

to the CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.

es and resources after a call ends.

ngs up.

e message indicates DISCONNECT to inform the UE that the calling party has hanged up.

NSFER message to the UE through a DOWNLINK DIRECT TRANSFER message.

SRNC.

CT TRANSFER messageto the CN through a DIRECT TRANSFER message. The DIRECT TRANSFER

e message indicatesRELEASE COMPLETE.

NSFER message to theUE through a DOWNLINK DIRECT TRANSFER message.

C to request call releaseon the Iu interface. The message indicates the reason for the Iu release.

ALCAP protocol on theIu interface initiates an Iu data transport bearer release procedure.

CN.



essage to the SRNC.

e to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.

ELETION RESPONSE message to the SRNC.

NC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the R



as a

ept or

dicated

he

ptional.

by the

o the

E The

y of

ging



all.

uest the

by the

AGE

the

eiving the

nfigure the integrity

N

ported

he SRNC

hat the

ssage



ot carry

of an RRC connection

ased and if a radio

SNs of

ION

rs and

cedure.

adio

C

essageindicates



C




RRC: Paging Type 1

RRC: RRC Connection Request (RACH)



RRC: RRC Connection Setup (FACH)























RRC:RRC Connection Setup Complete (DCCH)









RANAP: Initial UE Message (MM: Paging Response)

RRC: Initial Direct Transfer (MM: Paging Response)







RRC: Downlink Direct Transfer (CC: Setup)



RANAP: Direct Transfer (CC: Call Confirmed)





RRC: Uplink Direct Transfer (CC: Call Confirmed)






























RRC: Uplink Direct Transfer (CC: Alerting)






RRC:Downlink Direct Transfer (CC: Connect Acknowledge)

RRC: Uplink Direct Transfer (CC: Connect)










RRC: Downlink Direct Transfer (CC: Disconnect)



RRC: Uplink Direct Transfer (CC: Release)









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





value=hex 2dec(2908)= 10504

value= terminat ingConv ersat ionalcal l (CS MTC)

>>"RRC Connect ion Request Descr ipt ion"

>>"Geographical and UTRAN Enti ty Ident i f iers"



valu e=(-24+ (44/2))=-2.0 d B

value=hex2dec(6d)=109(Neighbour 's Pr imary Scrambl ing Code)

value=CPICH Ec/Io in valid

>>"RRC Connect ion Setup Descr ipt ion"

>>"Geographical and UTRAN Enti ty Ident i f iers"





value=hex 2dec(2908)= 10504

value=UE capable to sup port FDD , not TDD

value=UE capable to sup port GSM

value=Signal ing Radio Bearer Informat ion Setup ,RB-1



value=Radio Bearer Mapping




















value=BL ER Target= -20 dB

value=MaxAl lowedULTxPow er=24 dBm

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

-22 -96 -80

-22 -96 -70

value= use Closed Loop Pow er Control Algor i thm1 Note :DPCCH_Power_offset is configured by RN

value= use long SC on Upl ink

value=Spreading Factor 64 (Upl ink)



value=Spreading Factor 128 (Down l ink)

value=Primary Scrambl in g cod e=97

value=Spreading Factor 128 (Down l ink)

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

value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 an d Cellid=bin2dec(01110111100100

>>"RRC Connect ion Setup Com plete Descr ipt ion"





value= not sup port GSM (Locked UMTS Mode)

value= Chiper ing Alg or i thm A 5/3

value= UE support B and fdd2100 MHz

value= UE (Powerclass3) maximum transmit ted pow er =24 dBm

value= support Comp ressed Mode (CM) upl ink and dow nl ink














>>"Radio Bearer Descript ion "

























value= SF64(uplin k)-> AMR 12.2




value= SF128(down link )-> AMR 12.2









































PCPICH Power UL Interference DPCCH Initial Power

33 -107 -16

33 -107 -26

C and delivered to UE in RRC Connection Setup.



10)=30610











































10)=30610
























































































L1 Synch onization

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


L3 Messages - Video Call (CS64

UE NodeB S-R


Start Rx


Start Tx

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








3.NBAP: Radio LinkReconfiguration Prepare

4.NBAP: Radio Link


7.NBAP: Radio Link



6.RRC: Radio Bearer Setup

8.RRC: Radio Bearer Setup Complete


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

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

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

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


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


Call Establ ish ed




Request


Response



set up on the DCH as an example.

2. If IP transport is applied to the Iub interface, no ALCAP procedure is

5,.ALCAP: Iub User Plane Release

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

2.RRC:RRC Connection Release Complete


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




SCCP: CR (Connection Request)

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







2.RANAP: Direct Transfer (CC: Setup)

Call Procedure

C

>>RRC Proc

CN

1.RRC Co

2.Signalli

3.AuthenSecurity



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

1.RANAP: RAB Assignment Request

2.ALCAP : Iu User Plane Setup


6.RANAP: Direct Transfer (CC: Alerting)

8.RANAP: Direct Transfer (CC: Connect)

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

6.Convers

4.Cal

5. Radio Be



2.RANAP: Direct Transfer (CC: Disconnect)

3.RANAP: Direct Transfer (CC: Release)

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


9.RANAP: Iu Release Complete

8.ALCAP: Iu User Plane Release

7.Call R

8.RRC C



RRC connection setup procedure is performed for the UE to set up a


Triggering Conditions : The UE in idle mode intitiates the RRC connect

receives an RRC CONNECTION REQUEST message from the UE, the Ra

request, based on a specific algorithm. If accepting the request, the RRM

Dedicated Channel (DCH)or on a Common Channel (CCH),based on a spe


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

2.Based on the cause in the RRC connection request and the system resou

resources, and L1 and L2 resources. Then the SRNC sends a RADIO LINK

3.The NodeB responds with a RADIO LINK SETUP RESPONSE message t

4.The SRNC uses the ALCAP protocol to set up the Iub user plane transpor

for the ATM-based Iub interface only.

5.The SRNC sends an RRC CONNECTION SETUP message to the UE thr6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Synchoni

7. The UE sends an RRC CONNECTION SETUP COMPLETE message to

indicates that the RRC connection setup procedure ends.

If the RNC judges that the RRC connection request cannot be set up (for in

theUE, and indicates the reject reason in the message

edure Description

The signaling connection setup procedure is performed to exchang

Triggering Conditons: The UE sends a direct transfer message to initiate


1.The UE sends an INITIAL DIRECT TRANSFER message to the SRNC th

2.The SRNC receives the INITIAL DIRECT TRANSFER message from the

CN by the UE. The content of the NAS information is CM SERVICE REQU


-If accepting the request, the CN sends a CONNECTION CONFIRM (CC)

SRNC confirms that the signaling connection is set up.

-If rejecting the request, the CN sends a CONNECTION REJECT (CJ) m

the SRNC confirms that the signaling connection fails to be setup and then

The authentication and security mode control procedure is perfo

the integrity protection algorithm and ciphering algorithm. This procedure e

Triggerring Conditions: The UE and the CN exchange signaling. The net





nnection Setup

ng Connection Setup

tication & Mode Control



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

Triggering Conditions: The UE initiates a call




3.The CN sends a DIRECT TRANSFER message to the SRNC. The messa4.The SRNC transparently sends the contents of the DIRECT TRANSFER

5. A Radio Access Bearer (RAB) is set up. (see more details in RAB Setup

6. When the called terminal rings, the CN sends a DIRECT TRANSFER me





11.The SRNC transparently sends the contents of the UPLINK DIRECT TR

The Radio B earer Setup p rocedure shown is descr ibed as fo l lows:


2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRNCparameters. Based on the AAL2 link characteristic parameters,the ALCAP o

3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE mess

4.The NodeB allocates the associated resources and then sends a RADIO

5.(Optional; required for the ATM-based Iub interface only) The Iub ALCAP

uplink and downlink synchronization frames in the DCH frame protocol.


7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT messa

8.After performing the radio bearer setup, the UE sends a RADIO BEARER


The procedure when RAB Setup Fai lure shown is d escr ibed as fo l lows



The call release procedure is performed to release services and resou

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




han ed


Module (USIM) judges that the authentication is successful, the UE returns

5.The CN sends a SECURITY MODE COMMAND message to the SRNC to

algorithms.

6.The SRNC sends a SECURITY MODE COMMAND message to the UE to


- If the in tegr i ty protect ion and cipher ing algor i thms are conf igured su

then sends a SECURITY MODE COMMAND COMPLETE message to the- If the UE does not s upport the in tegr i ty protect ion and cipher ing algo

contains the error information and the reason for the failure. The SRNC the

ation

l Setup

arer Setup



The RRC Connection Release procedure is performed to release the sign

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

UE,the SRNC initiates an RRC connection release procedure.

The procedure shown is descr ibed as fo l lows: based on the resouce oc

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

bearers fails to be setup ,the RRC connection on the CCH is released)

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

(NOTE: The SRNC may send the RRC CONNECTION RELEASE message

number of retransmissions and the transmission intervals are determined b

COMPLETE message from the UE after sending the RRC CONNECTION

2.The UE sends an RRC CONNECTION RELEASE COMPLETE message

3.The SRNC sends a RADIO LINK DELETION REQUEST message to the

4.After releasing the resources, the NodeB sends a RADIO LINK DELETIO

5.(Optional; required for the ATM-based Iub interface only) The SRNC uses

up.





7.The CN sends an IU RELEASE COMMAND message to the SRNC to req

8.(Optional; applicable to the ATM-based Iu-CS interface only) The ALCAP

9.The SRNC sends an IU RELEASE COMPLETE message to the CN.

elease

onnection Release



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 t

io Resource Management (RRM) module of the RNC determines whether to accept or reject theRRC con

odule further determines whether to set up the RRC connection on a

ific 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 Networ

SETUP REQUEST message to the NodeB, requesting the NodeB to allocate the specific radio link resour

o the SRNC after successfully preparing the resources.

t bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional. I

ough the downlink CCCH (FACH). The message contains the information about the DCH allocated by thezation 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

tance, 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 and sends an INITIAL UE MESSAGE to the CN over the Iu interface. The INITIAL UE MESSAGE cont

ST.

message to the SRNC. The message indicates that the SCCP connection is set up. After receivingthe me

ssage to the SRNC. The message indicates that the SCCP connection fails to be set up. After receiving th

initiates the RRC release procedure.

rmed for the UE and the network to implement bi-directional authentication and to negotiate and configure

sures integrity and correctness of signaling

ork initiates the authentication and securitymode control procedure

ge indicates AUTHENTICATION REQUEST.




he message contains the number of the called party and the information about the bearer capability of the

NSFER messageto the CN through a DIRECT TRANSFER message.

ge indicates CALL PROCEEDING and contains the information about the negotiated bearer capability of tessage to the UE through a DOWNLINK DIRECT TRANSFER message.

rocedure below)

ssage to the SRNC. The message indicates ALERTING.


ge indicates CONNECT, which means that the called party has answered the call.


NSFER message to the CN through a DIRECT TRANSFER message, indicating CONNECT ACKNOWL


aps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and rn the Iu interface initiates an Iu user plane transport bearer setup procedure.

ge to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio link

INKRECONFIGURATION READY message to the SRNC.

at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC perfo

e to theNodeB.

SETUP COMPLETE message to the SRNC.

. The RAB isset up.

:


. 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 cont

NSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RES

message with an XRES IE.

initiate the security mode control procedure. The message contains the information about the supported c

inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.

cessfu l ly , the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The SRN

CN.The message contains the information about the integrity protection and ciphering algorithms that thei thms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The message

n sends a SECURITY MODE COMMAND REJECT message to the CN



aling connection and all radio bearers between UE and the UTRAN

r the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not carry

cupied by the RRC connection,there are two types of RRC connection release procedure: release of an R

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 t

the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE

ELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)

o the SRNC.

odeB,requesting the NodeB to delete the radio link resources in the NodeB.

RESPONSE message to the SRNC.

the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC conn

ge indicates RELEASE to request release of the call.


NSFER messageto the CN through a DIRECT TRANSFER message, indicating RELEASE COMPLETE.

uest call release on the Iu interface. The message indicates the reason for the Iu release

protocol on the Iu interface initiates an Iu data transport bearer release procedure.



he SRNC

ection

Temporary Identity(RNTI),radio

es required for an RRC connection.

t is required

RNC.

E.

ins the NAS information to be sent to the

ssage, the

e message,



call.

e call.

DGE.

dio resource characteristic

for carrying the RAB.

rm synchronization by exchanging

nt informs the CN that the UE has

ONSE. If the UMTS Subscriber Identity

iphering and integrity protection

C

E uses.



other RAB of the

C connection from DCH and release of

hese messages are the same. The

ction release procedure ends.




value

value

value

valu e

value

RRC:RRC Connection Request (RACH) >>" RR

>>" Ge



value

value

value

value

value

RRC:RRC Connection Setup (FACH) >>" RR

>>" Ge



value

value



value



value





value









value

value

value

valu e

valu e

value



value

value

value

Cell Id

value



RRC:RRC Connection Setup Complete (DCCH) >>" RR



valu e

valu e

valu e



valu e

valu e

valu e



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



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


















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: Uplink Direct Transfer (CC: Connect Acknowledge)

RRC: Downlink Direct Transfer (CC: Connect)





RRC: Uplink Direct Transfer (CC: Disconnect)




RRC: Downlink Direct Transfer (CC: Release)













hex2d ec(2908)= 10504

Originat ingCo nversat ionalcal l (CS MOC)

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







hex2d ec(2908)= 10504

UE capable to supp ort FDD , not TDD

UE capable to suppo rt GSM






Radio Bearer Mapping




















BLER Target= -20 dB

MaxAl lowedULTxPower=24 dBm

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

-22 -96 -80

-22 -96 -70




Spreading Factor 64 (Upl ink)




Pr imary Scrambl ing cod e=97


entity=RNCid(12bits)+Cellid(16bits)




Connection Setup Complete Descript ion "



not su ppo rt GSM (Locked UMTS Mode)

Chiper ing Algor i thm A5/3




UE (Powerclass3) maximum transmit ted pow er =24 dBm




















>>"Radio Bearer Descript io n"













value= SF16(uplin k)-> CS64 (VP)



value=Primary Scrambl in g co de=97

value= SF32(down link )-> CS64 (VP)

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

value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 an d Cel l id=bin2de




































33 -107 -16

33 -107 -26




10)=30610





































(0111011110010010)=30610











































































Start Rx

RRC: Downlink Direct Transfer (GMM: GP

RRC: Initial Direct Transfer (GMM: A

RRC: Uplink Direct Transfer (MM: Authenticatio

RRC: Uplink Direct Transfer (GMM: GPRS

RRC: Security Mode Com

RRC: Security Mode Compl

RRC: Downlink Direct Transfer (MM: Authentica

8.RRC: RRC Connection Setup Com

L1 Synch onization

UE NodeB

Start Tx

1.RRC: RRC Connection Reque

5.RRC: RRC Connection Setup

If UE alreadyattached toGPRS CN, the UEwill only send"GMM:Service

Request"message to N/W



RRC: Radio Bearer Setup Co

RRC: Downlink Direct Transfer (SM: Activat

RRC:Measurement Contr

RRC:Measurement Repo

RRC: Downlink Direct Transfer (MM:

RRC: Uplink Direct Transfer (MM: Att

RRC: Radio Bearer Setu

RRC: Uplink Direct Transfer (SM: Activate P



RRC: Uplink Direct Transfer (SM: Deactivate

RRC: Downlink Direct Transfer (SM: Deactiva

RRC: Uplink Direct Transfer (CC: RRC Connec

RRC: Downlink Direct Transfer (CC: RRC

RRC: Uplink Direct Transfer (CC: RRC Connec

RRC: Radio Bearer Relea

RRC: Downlink Direct Transfer (MM:

RRC: Radio Bearer Release Co

RRC: Uplink Direct Transfer (MM: De

RRC: Radio Bearer Reconfig

RRC: Radio Bearer Reconfiguratio







7.NBAP:Synchonization Indicator

L3 Messages - PS(R99) Call Pr


S Identity Request)

tach Request)

n & Ciphering Response)

Identity Response)

and

leted

ion & Ciphering Request)

pleted (DCH)

t (RACH)

(FACH)

S-RNC



NBAP: Radio Link Reconfiguration

Prepare


Ready


Commit

: a o n econ gura on

Prepare


Ready


Commit

mplete

PDP Context Accept)

ol

rt

ALCAP: Iub User Plane Setup

PS Session Establ ished

Attach Accept)

ch Completed)



p

DP Context Request)




Prepare


Ready


Commit


Request


Response

PDP Context Request)

e PDP Context Accept)

tion Release Complete)

onnection Release)



ion Release Complete)

se

etach Accept)

mpleted

tach Request)

ration

n Complete





RANAP: Initial UE Message GMM: (Attach Request)

RANAP: GMM: GPRS Identity Request

RANAP: GMM: GPRS Identity Response

RANAP: MM: Authentication & Ciphering Request

RANAP:MM: Authentication&Ciphering Response

RANAP: Security Mode Command

RANAP: Security Mode Complete

RANAP: Common ID(IMSI)

>>RRC Procedure Desc

cedure

CN

1.RRC Connection

2.GPRS Attach Pr

3.Authentication &



RANAP: MM: Attach Accept

RANAP: MM: Attach Completed

RANAP: SM: Activate PDP Context Request

RANAP: RAB Assignment Request

ALCAP : Iu User Plane Setup

RANAP: RAB Assignment Response

RANAP: SM: Activate PDP Context Accept

6.Downlink and U

4.PS Session Setu

5. Radio Bearer Setu



RANAP: SM: Deactivate PDP Context Request

RANAP: SM: Deactivate PDP Context Accept

RANAP: MM: Detach Request

RANAP: MM: Detach Accept




7.PS Session Rel

8.RRC Connectio

Radio Bearer ReconUpgrade/Downgrad





ription

RRC connection setup procedure is performed for the UE to set u


Triggering Conditions : The UE in idle mode intitiates the RRC con

SRNC receives an RRC CONNECTION REQUEST message from theconnection request, based on a specific algorithm. If accepting the requ

(DCH)or on a Common Channel (CCH),based on a specific RRM algori


1.The UE sends an RRC CONNECTION REQUEST message to the S

2.Based on the cause in the RRC connection request and the system re

NetworkTemporary Identity(RNTI),radio resources, and L1 and L2 reso

allocate the specific radio link resources required for an RRC connectio

3.The NodeB responds with a RADIO LINK SETUP RESPONSE messa

4.The SRNC uses the ALCAP protocol to set up the Iub user plane tran

is required for the ATM-based Iub interface only.

5.The SRNC sends an RRC CONNECTION SETUP message to the U6. UE and NodeB initiate L1 Synchronization. NodeB sends NBAP:Sync

7. The UE sends an RRC CONNECTION SETUP COMPLETE messag


If the RNC judges that the RRC connection request cannot be set up (fo

The GPRS Attach procedure is performed in order to make UE pre

data paging via the SGSN, and notification of incoming PS Data.In the a

PS attach and combined PS / CS attach.The identity provided to the net

Triggering Conditons: The UE sends a GPRS Attach Request messa


1.UE initiates the attach procedure by the transmission of an Attach Re

available. RNC opens an SCCP (Signalling Connection Control Part) co

2.If the UE identifies itself with P-TMSI and the SGSN has changed sinc

request the IMSI. The old SGSN responds with Identification Response

3.If the UE is unknown in both the old and new SGSN, the SGSN sends

4. The new SGSN asks the HLR to authenticate the UE. HLR sends ba

subscriber information The SGSN sends the Authentication and Cipheri

and AUTN (Authentication Token) to the UE. At reception of this messa

Authentication and Ciphering response (RES) message to the SGSN. D

Integrity Key, IK. These keys are stored together with the CKSN (Cipher

transmission security. A known bit stream is encrypted and decrypted in5. If the SGSN number has changed since the GPRS detach, or if it is t

-The SGSN sends an Update Location (SGSN Number, SGSN Address

-The HLR sends Cancel Location (IMSI, Cancellation Type) to the old S

-The old SGSN acknowledges with Cancel Location Ack (IMSI). If there

the MM (Mobility Management) and PDP contexts

-The HLR sends Insert Subscriber Data (IMSI, GPRS subscription data)

-The new SGSN validates the UE's presence in the (new) RA (Routing

Subscriber Data Ack (IMSI) message to the HLR.

Establishment

cedure

Security Mode Control



The authentication and security mode control procedure is p

the integrity protection algorithm and ciphering algorithm. This procedu

Triggerring Conditions: The UE and the CN exchange signaling. The


1.The CN sends a DIRECT TRANSFER message to the SRNC. The m

2.The SRNC transparently sends the contents of the DIRECT TRANSF

3.The UE sends an UPLINK DIRECT TRANSFER message to the SRN

4.The SRNC transparently sends the contents of the UPLINK DIRECT

UMTS Subscriber Identity Module (USIM) judges that the authenticatio

5.The CN sends a SECURITY MODE COMMAND message to the SRN

and integrity protection algorithms.

6.The SRNC sends a SECURITY MODE COMMAND message to the U


-If the integri ty protectio n and ciphering algori thm s are con figured

then sends a SECURITY MODE COMMAND COMPLETE message to

- If the UE does not s upport th e in tegr ity protect ion and cipher ing a

contains the error information and the reason for the failure. The SRNC

The RANAP:Common ID message is used to transport the perman

-The HLR acknowledges the Update Location message by sending an

If the Update Location is rejected by the HLR, the SGSN rejects the Atta

6. If Attach Type in step 1 indicated PS Attach while already CS attache

SGSN starts the location update procedure towards the new MSC/VLR

the VLR.

a. The SGSN sends a Location Update Request (new LAI, IMSI, SGSN

indicated combined PS / CS attach. Otherwise, Location Update Type sb. If the LA update is inter-MSC, the new VLR sends Update Location (I

c. If the LA update is inter-MSC, the HLR sends a Cancel Location (IMS

d. The old VLR acknowledges with Cancel Location Ack (IMSI). If there

removing the MM and PDP contexts.

e. If the LA update is inter-MSC, the HLR sends Insert Subscriber Data

f. The VLR acknowledges with Insert Subscriber Data Ack (IMSI).

g. After finishing the inter-MSC location update procedures, the HLR res

h. The VLR responds with Location Update Accept (VLR TMSI) to the S

7. The SGSN sends an Attach Accept (P-TMSI, VLR TMSI, P-TMSI Sig

Request cannot be accepted, the SGSN returns an Attach Reject (IMSI

8. If P-TMSI or VLR TMSI was changed, the UE acknowledges the rece

9. If VLR TMSI was changed, the SGSN confirms the VLR TMSI re-allo

The PS Session Setup procedure is performed to set up a PS ses

Triggering Conditions: The UE send Activate PDP context request m

Mobility Management Connected that enables the user to transmitt and

virtual data channel between a terminal connected to a UE and a GGSN

bearer establishes on request of the SGSN in order to realize the air int

(Temporary Logical Link Identity) associated to IMSI.

link Data Transfer

p



IP addresses can be allocated dynamically or statistically. If allocated dy

enables subscribers to provide their own IP addresses. This can be use

QoS enables the operator to differentiate GPRS services.

When dynamic addressing from the home PLMN or the Visitor PLMN is


1.The UE sends an Activate PDP Context Request (NSAPI, TI(TeardowOptions) message to the SGSN The UE shall use PDP Address to indic

2. The SGSN sends a RAB Assignment Request message to the RNC t

3.The RNC establishes the appropriate radio bearer In WCDMA, RAB s

4.The RNC returns a RAB Assignment Response message to the SGS

5. The SGSN validates the active PDP Context Request using PDP Typ

records.The SGSN sends a Create PDP Context Request message to t

Name to find an external network and optionally to activate a service for

6. The GGSN creates a new entry in its PDP context table and generate

the SGSN and the external PDP network, and to start charging

7.The SGSN inserts the Network layer Service Access Point Identifier,

SGSN selects Radio Priority and Packet flow Id based on QoS Negotiat

theGGSN and the UE and to start charging

The Radio Bearer Setup proc edure show n is described as fol lows:

1.The CN sends an RAB ASSIGNMENT REQUEST message to the SR

2.(Optional; applicable to the ATM-based Iu-CS interface only) The SRN

characteristic parameters. Based on the AAL2 link characteristic param

3.The SRNC sends a RADIO LINK RECONFIGURATION PREPARE m

RAB.

4.The NodeB allocates the associated resources and then sends a RA

5.(Optional; required for the ATM-based Iub interface only) The Iub ALC

synchronization by exchanging uplink and downlink synchronization fra


7.The SRNC sends a RADIO LINK RECONFIGURATION COMMIT me8.After performing the radio bearer setup, the UE sends a RADIO BEA

9.The SRNC sends an RAB ASSIGNMENT RESPONSE message to th

The procedure when RAB Setup Fai lure show n is descr ibed as fo l l

1.The CN sends an RAB ASSIGNMENT REQUEST message to the SR

2.The SRNC sends an RAB ASSIGNMENT RESPONSE message to th

The PS session release procedure is performed to release servic

Triggering Conditions : The UE send Deactivate PDP context reques

deactivation,the UE has the state Active. After the PDP Context deactiv

PDP contexts activated.PDP Deactivation may be initiated by a:UE proc


1.The UE sends a Deactivate PDP Context Request (TI, Teardown Indi

2.The SGSN sends a Delete PDP Context Request (TEID, NSAPI, Tear

message, then the SGSN deactivates all PDP contexts associated with

3.The GGSN removes the PDP context(s) and returns a delete PDP Co

4.The SGSN returns a Deactivate PDP Context Accept (TI) message to

5. In Iu mode, radio access bearer release is done by the RAB Assignm

6. The SCCP connection between RNC and SGSN is released. At GPR

ase

Release

figuration toBit Rate



The RRC Connection Release procedure is performed to release the

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

of the UE,the SRNC initiates an RRC connection release procedure.

The procedure shown is descr ibed as fo l lows: based on the resouc

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

a radio bearers fails to be setup ,the RRC connection on the CCH is rel

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

(NOTE: The SRNC may send the RRC CONNECTION RELEASE mes

the same. The number of retransmissions and the transmission interval

COMPLETE message from the UE after sending the RRC CONNECTI

2.The UE sends an RRC CONNECTION RELEASE COMPLETE mess

3.The SRNC sends a RADIO LINK DELETION REQUEST message to

4.After releasing the resources, the NodeB sends a RADIO LINK DELE5.(Optional; required for the ATM-based Iub interface only) The SRNC u

procedure ends.



p a signaling connection to the SRNC. RRC connection setup is always initiated by the UE. One UE has a

nection setup procedure when the NAS of the UE requests the establishment of a signaling connection When

E, the Radio Resource Management (RRM) module of the RNC determines whether to accept or reject theest, the RRM module further determines whether to set up the RRC connection on a Dedicated Channel

hm. Typically, an RRC connection is set up on the DCH.

NC through the uplink CCCH(RACH), requesting the establishment of an RRC connection.

source status, the SRNC determines to set up the RRC connection on a DCH and allocates the Radio

rces. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, requesting the Nod

.

ge to the SRNC after successfully preparing the resources.

port bearer and performs the synchronization between the SRNC and the NodeB. This procedure is optional

through the downlink CCCH (FACH). The message contains the information about the DCH allocated by thhonization Indicator message to SRNC when the uplink enter "In-Sync" state

to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. The message

r instance, due to insufficient resources), it directly sends an RRC CONNECTION REJECT message to

sence known to the network by performing a Packet Service Attach (GPRS attach). This makes the UE avail

ttach procedure, the UE shall provide its identity and an indication of which type of attach that is to be execut

work shall be the UE's Packet TMSI (P-TMSI) or IMSI

e to initiate the signaling connection setup procedure.

uest message to the RNC. IMSI shall be included if the UE does not have a valid P-TMSI (Packet Temporar

nnection and sends the Attach request to SGSN

e detach, the new SGSN sends an Identification Request (P-TMSI, old RAI, old P-TMSI Signature) to the old

(IMSI, Authentication vector). The old SGSN also validates the old P-TMSI

an Identity Request (Identity Type = IMSI) to the UE. The UE responds with Identity Response (IMSI).

k to SGSN the Authentication data received from AUC (Authentication Center). The HLR contains GSM and

ng Request to the UE. At authentication of a WCDMA subscriber, the SGSN transmitts the RAND (Random

e, the UE (USIM, WCDMA Subscriber Identity module in the UE) verifies AUTN and if accepted the UE retu

uring generation of authentication vectors, the USIM in the UE also computes a new Ciphering Key. CK, and

ing key sequence number of Kc) until CKSN is updated at the next authentication. The SGSN verifies the

SGSN and UE.e very first attach, then the SGSN informs the HLR:

, IMSI) to the HLR.

SN with Cancellation Type set to Update Procedure.

are any ongoing procedures for that UE, the old SGSN shall wait until these procedures are finished before r

to the new SGSN.

rea). If all checks are successful then the SGSN constructs an MM context for the UE and returns an Insert



erformed for the UE and the network to implement bi-directional authentication and to negotiate and configur

e ensures integrity and correctness of signaling

network initiates the authentication and securitymode control procedure

ssage indicates AUTHENTICATION REQUEST.

R message to the UE through a DOWNLINK DIRECT TRANSFER message.

C.

RANSFER messageto the CN through a DIRECT TRANSFER message, indicating AUTHENTICATION RE

is successful, the UE returns a message with an XRES IE.

C to initiate the security mode control procedure. The message contains the information about the supported

E to inform the UE of the integrity protection and ciphering algorithms that the UTRAN selects.

successfu l ly , the UE sends a SECURITY MODE COMMAND COMPLETE message to the SRNC. The SR

the CN.The message contains the information about the integrity protection and ciphering algorithms that the

lgor i thms, the UE sends a SECURITY MODE COMMAND FAILURE message to the SRNC. The message

then sends a SECURITY MODE COMMAND REJECT message to the CN

nt UE Identity(IMSI) to SRNC

pdate Location Ack to the SGSN after the canceling of old MM context and insertion of new MM context are

ch Request from the UE with an appropriate cause code

, or combined PS/CS attach, then the VLR shall be updated. The VLR number is received from the RA infor

upon receipt of the first Insert Subscriber Data message from the HLR. This operation marks the UE as GPR

Number, Location Update Type) message to the VLR. Location Update Type shall indicate CS attach if Attac

hall indicate normal location update. The VLR creates an association with the SGSN by storing SGSN NumbMSI, new VLR) to the HLR.

I) to the old VLR.

are any ongoing procedures for that MS, the old SGSN shall wait until these procedures are finished before

(IMSI, GSM subscriber data) to the new VLR.

ponds with Update Location Ack (IMSI) to the new VLR.

GSN.

nature, Radio Priority SMS) message to the UE. P-TMSI is included if the SGSN allocates a new P-TMSI. If t

, Cause) message to the UE

ived TMSI(s) with Attach Complete (P-TMSI, VLR TMSI).

ation by sending TMSI Reallocation Complete (VLR TMSI) to the VLR.

sion

ssage to RNC. PDP Context Activation is performed when the UE initiates a packet call setup. The UE has t

receive data while moving within a PLMN. and starts the PDP context activation procedure used to set up an

. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS, parameters. A Ra

rface connection. At the end the UE has an IP address NSAPI (Network layer Service Access Point Identifie



namically, this significantly reduces the total number of IP addresses required per PLMN. Support of static IP

ul when accesing secure networks that use the calling IP address as a form of security check. The support o

used, it is the responsibility of the GGSN to allocate and release the dynamic PDP address.

n Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Requested, PDP Coate whether it requires the use of a static PDP address or whether it requires the use of a dynamic PDP addr

o establish a RABs

etup is done by the RAB Assignment procedure

e (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and the PDP context sub

he affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. The GGSN may use

this APN

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

SAPI along with the GGSN address in its PDP context and informs the UE via RNC that the PDP Context is

d, and returns an Activate PDP Context Accept message to the UE. The SGSN is now able to route PDP P

NC to initiate the RAB setup procedure.

C maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristic parameters and

ters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup procedure.

essage to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to the existing radio lin

IO LINKRECONFIGURATION READY message to the SRNC.

AP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB and the SRNC per

es in the DCH frame protocol.

sage to theNodeB. ER SETUP COMPLETE message to the SRNC.

e CN. The RAB isset up.

ows:

NC to initiate the RAB setup procedure.

e CN. The message indicates the ID of the RAB that fails to be set up and the reason for the failure.

s and resources after a session ends.

t message to RNC. A PDP Context Deactivation is performed when the UE terminates a packet call. Before t

tion procedure the state becomes Packet Mobility Management Connected.The RAB will be released if ther

edure,SGSN procedure,GGSN procedure

ation) message to the SGSN via the RNC

down Indication) message to the GGSN. If Teardown Indication was included by the UE in the Deactivate PD

this PDP address by including Teardown Indication in the Delete PDP Context Request message

ntext Response (TEID) message to the SGSN. The Delete PDP Context messages are sent over the backbo

the UE via the RNC

ent procedure

S detach, all PDP contexts for the UE are implicitly deactivated



signaling connection and all radio bearers between UE and the UTRAN

ether the RRC connection carries any other RAB or the UE. If judging that the RRC connection does not car

occupied by the RRC connection,there are two types of RRC connection release procedure: release of an

n needs to be released after a successful outgoing call,, the RRC connection on the DCH is released and if

eased)

UE through the DCCH.

age several times to increase the probability of proper reception of the message by the UE. The RRC SNs o

are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION RELEASE

N RELEASE message for four times, the SRNC judges that the UE has released the RRC connection.)

ge to the SRNC.

he NodeB,requesting the NodeB to delete the radio link resources in the NodeB.

ION RESPONSE message to the SRNC.ses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. Then, the RRC con



the

RRC

B to

. It

SRNC.

ble for SMS over PS

ed.

IMSI)

SGSN to

WCDMA

umber)

ns an

a new

emoving



PONSE. If the

ciphering

NC

UE uses.

finished.

mation. The

S-attached in

h Type

r.

e Attach

e state Packet

remove a

dio Access

) and a TLLI



address allocation

f

figurationess.

scription

Access Point

its) between

Accepted. The

Us between

radio resource

ks for carrying the

orm

he

are no other

P Context Request

ne network



y other RAB

RC connection from

these messages are

nection release




value=hex2de

value=hex2de

value=hex2de

value= Origina

value=(-24+ (3

>>" RRC Connec

>>"Geograph ica




value=hex2de

value=hex2de

value=hex2de

>>" RRC Connec

>>"Geograph ica




value=UE cap

value=UE cap

v alu e=Sig nali

value=Rad io B



v alu e=Sig nali





v alu e=Sig nali



v alu e=Sig nali









value=BLER T

value=MaxAl lo

value=(-48*2)=

value= use Cl

v al ue= use l on



v alu e=Sp read i

v alu e=Sp read i

value=Primary



v alu e=Sp read i

Cell Identity =

value= 000000

>>" RRC ConnecRRC:RRC Connection Setup Complete (DCCH)



value= no t su

v alu e= Ch ip eri



value= UE sup

value= UE (Po

va lue= suppor

value= UE sup





value= no t su

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: Uplink Direct Transfer (SM: Activate PDP Context Request)





























RRC: Downlink Direct Transfer (SM: Activate PDP Context Accept)



RRC: Radio Bearer Reconfiguration









RRC: Radio Bearer Reconfiguration Complete



RRC: Uplink Direct Transfer (SM: Deactivate PDP Context Request)



RRC: Downlink Direct Transfer (SM: Deactivate PDP Context Accept)



RRC: Radio Bearer Release







RRC: Radio Bearer Release Completed




RRC: Uplink Direct Transfer (MM: Detach Request)




RANAP: MM: Detach Request

RANAP: MM: Detach Accept

RRC: Downlink Direct Transfer (MM: Detach Accept)





(5)=5 , hex 2dec (2)=2 ,hex2d ec(0)=0 --> MCC=520

(0)=0 , hex 2dec (1)=1 --> MNC=01

(2908)= 10504

t ingBackg round Cal l (PS MOC)

/2))=-7.5 dB

t ion Request Descr ipt ion"

l and UTRAN Enti ty Ident i f iers"



(5)=5 , hex 2dec (2)=2 ,hex2d ec(0)=0 --> MCC=520

(0)=0 , hex 2dec (1)=1 --> MNC=01

(2908)= 10504

t ion Setup Descr ipt ion"

l and UTRAN Enti ty Ident i f iers"



ble to supp ort FDD , not TDD

ble to supp ort GSM

g Radio Bearer Informat ion Setup ,RB-1

earer Mappin g




















arget= -20 dB

wedULTxPower=24 dBm

-96 dBm (step of 2 dB) Default Constant DPCCH_Power_offset CPICH_RSCP

-22 -96 -80

-22 -96 -70


sed Loop Power Contro l A lgor i thm1

g SC on Upl ink



ng Factor 64 (Upl ink)

ng Factor 128 (Downl ink )

Scrambl ing cod e=97



ng Factor 128 (Downl ink )

NCid(12bits)+Cell id(16bits)


t ion Setup Comp lete Descr ipt ion"



port GSM (Locked UMTS Mode)

ng Algor i thm A5/3



port Band fdd2100 MHz

werclass3) maximu m transmit ted power =24 dBm

t Compressed Mode (CM) upl ink and dow nl ink

port Band fdd1800 MHz





port HSDPA
































value= SF16(uplin k)-> PS64




value= SF32(down link )-> PS64


value= 000000001011 0111011110010010 => RNCid=bin2dec(000000001011)=11 an d Cel l id=bin2dec(0














value= SF16(down link )-> PS128








































33 -107 -16

33 -107 -26






10)=30610









































111011110010010)=30610



















































































































Prepare


Ready


S-


L1 Syncho nization

UE NodeB

RRC: Initial Direct Transfer (GMM: Service Request)


L3 Messages - PS(HSDPA)


Start Rx

Start Tx


RRC: Security Mode Completed





Commit


Prepare


Ready

NBAP: Radio Link ReconfigurationCommit


Prepare


Ready

RRC: Physical Channel Reconfiguration (DCCH)








PS Session Establ is



RRC:Physical Channel Reconfiguration Complete (DCCH)

RRC:Measurement Report (e1d)



: a o n econ gurat on

Commit


Request


Response










RANAP: GMM:Service Request







NC CN

all Procedure

>>RRC Proc

1.RRC C

2.PS Se







ed

HSDPA's

3. Radio

4. Downl






5.PS Se

6.RRC



edure Description

RRC connection setup procedure is performed for the


Triggering Conditions : The UE in idle mode intitiates th

SRNC receives an RRC CONNECTION REQUEST messagconnection request, based on a specific algorithm. If accept

(DCH)or on a Common Channel (CCH),based on a specific


1.The UE sends an RRC CONNECTION REQUEST messa

2.Based on the cause in the RRC connection request and th

NetworkTemporary Identity(RNTI),radio resources, and L1 a

allocate the specific radio link resources required for an RR

3.The NodeB responds with a RADIO LINK SETUP RESPO

4.The SRNC uses the ALCAP protocol to set up the Iub use


5.The SRNC sends an RRC CONNECTION SETUP messa6. UE and NodeB initiate L1 Synchronization. NodeB sends

7. The UE sends an RRC CONNECTION SETUP COMPLE


If the RNC judges that the RRC connection request cannot

The PS Session Setup procedure is performed to set

Triggering Conditions: The UE send Activate PDP context

Mobility Management Connected that enables the user to tr

virtual data channel between a terminal connected to a UE a

bearer establishes on request of the SGSN in order to realiz


IP addresses can be allocated dynamically or statistically. If

enables subscribers to provide their own IP addresses. This


When dynamic addressing from the home PLMN or the Visi


1. The UE initiates the PS Session by using the Service Req

sets-up an SCCP connection with the SGSN and transfers t

2 .The UE sends an Activate PDP Context Request (NSAPI,

Options) message to the SGSN The UE shall use PDP Add3. The SGSN sends a RAB Assignment Request message t

4.The RNC establishes the appropriate radio bearer In WC

5.The RNC returns a RAB Assignment Response message

6. The SGSN validates the active PDP Context Request usi

records.The SGSN sends a Create PDP Context Request

Name to find an external network and optionally to activate

7. The GGSN creates a new entry in its PDP context table a

the SGSN and the external PDP network, and to start chargi

8.The SGSN inserts the Network layer Service Access Point

onnection Establishment

ssion Setup



The RRC Connection Release procedure is performed to

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

of the UE,the SRNC initiates an RRC connection release pr

The procedure shown is descr ibed as fo l lows: based on

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

a radio bearers fails to be setup ,the RRC connection on th

1.The SRNC sends an RRC CONNECTION RELEASE mes

(NOTE: The SRNC may send the RRC CONNECTION REL

the same. The number of retransmissions and the transmis

COMPLETE message from the UE after sending the RRC

2.The UE sends an RRC CONNECTION RELEASE COMP

The PS session release procedure is performed to rel

Triggering Conditions : The UE send Deactivate PDP co

deactivation,the UE has the state Active. After the PDP Con

PDP contexts activated.PDP Deactivation may be initiated b


1.The UE sends a Deactivate PDP Context Request (TI, Te

2.The SGSN sends a Delete PDP Context Request (TEID,

message, then the SGSN deactivates all PDP contexts asso

3.The GGSN removes the PDP context(s) and returns a del

4.The SGSN returns a Deactivate PDP Context Accept (TI)

5. In Iu mode, radio access bearer release is done by the R6. The SCCP connection between RNC and SGSN is releas

SGSN selects Radio Priority and Packet flow Id based on Q


The Radio Bearer Setup proc edure show n is described

1.The CN sends an RAB ASSIGNMENT REQUEST messa

2.(Optional; applicable to the ATM-based Iu-CS interface on

characteristic parameters. Based on the AAL2 link characte

3.The SRNC sends a RADIO LINK RECONFIGURATION PRAB.

4.The NodeB allocates the associated resources and then s

5.(Optional; required for the ATM-based Iub interface only)

synchronization by exchanging uplink and downlink synchro

6.The SRNC sends a RADIO BEARER SETUP message to

7.The SRNC sends a RADIO LINK RECONFIGURATION C

8.After performing the radio bearer setup, the UE sends a R

9.The SRNC sends an RAB ASSIGNMENT RESPONSE m

The p r ocedu re when RAB Setup Fai lu re shown is desc r


erving Cell Change

earer Setup

ink and Uplink Data Transfer



3.The SRNC sends a RADIO LINK DELETION REQUEST

4.After releasing the resources, the NodeB sends a RADIO


procedure ends.

sion Release

onnection Release



UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the U

e RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling

e from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to aing the request, the RRM module further determines whether to set up the RRC connection on a Dedi

RRM algorithm. Typically, an RRC connection is set up on the DCH.

ge to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection

e system resource status, the SRNC determines to set up the RRC connection on a DCH and allocate

nd L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, re

connection.

NSE message to the SRNC after successfully preparing the resources.

r plane transport bearer and performs the synchronization between the SRNC and the NodeB. This pro

e to the UE through the downlink CCCH (FACH). The message contains the information about the DNBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state

E message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. Th

e set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJEC

p a PS session

request message to RNC. PDP Context Activation is performed when the UE initiates a packet call se

nsmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure

nd a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS,

e the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Acc

allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN.

can be useful when accesing secure networks that use the calling IP address as a form of security ch

or PLMN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP addres

uest (Service Type=Data) message. After the RR setup completion the UE asks for initial direct transf

he initial service request (Authentication and ciphering may performed depends on operator's setting)

TI(Teardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Re

ess to indicate whether it requires the use of a static PDP address or whether it requires the use of a do the RNC to establish a RABs

MA, RAB setup is done by the RAB Assignment procedure

to the SGSN

g PDP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and th

essage to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. Th

service for this APN

nd generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Poin

ng

Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that th



release the signaling connection and all radio bearers between UE and the UTRAN

judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC conne

cedure.

the resouce occupied by the RRC connection,there are two types of RRC connection release procedu

C connection needs to be released after a successful outgoing call,, the RRC connection on the DCH

CCH is released)

sage to the UE through the DCCH.

EASE message several times to increase the probability of proper reception of the message by the UE

ion intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION REL

ONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC

ETE messa e to the SRNC.

ease services and resources after a session ends.

text request message to RNC. A PDP Context Deactivation is performed when the UE terminates a p

ext deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will

y a:UE procedure,SGSN procedure,GGSN procedure

rdown Indication) message to the SGSN via the RNC

SAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in

ciated with this PDP address by including Teardown Indication in the Delete PDP Context Request me

te PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are se

message to the UE via the RNC

B Assignment procedureed. At GPRS detach, all PDP contexts for the UE are implicitly deactivated

S Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now abl

s fo l lows:

e to the SRNC to initiate the RAB setup procedure.

ly) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristi

istic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup proced

REPARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to th

ends a RADIO LINKRECONFIGURATION READY message to the SRNC.

he Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB

ization frames in the DCH frame protocol.

the UE.

OMMIT message to theNodeB.

ADIO BEARER SETUP COMPLETE message to the SRNC.

ssage to the CN. The RAB isset up.

bed as fo l lows:




essage to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.

LINK DELETION RESPONSE message to the SRNC.

he SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. T



. One UE has a

connection When the

cept or reject the RRCated Channel

.

s the Radio

questing the NodeB to

cedure is optional. It

H allocated by the SRNC.

e message

message to

tup. The UE has the state Packet

used to set up and remove a

parameters. A Radio Access

ess Point Identifier) and a TLLI

upport of static IP address allocation

ck. The support of

.

r to the serving node. The RNC

quested, PDP Configuration

ynamic PDP address.

PDP context subscription

e GGSN may use Access Point

t Protocol Data Units) between

e PDP Context is Accepted. The



tion does not carry other RAB

re: release of an RRC connection from

is released and if

. The RRC SNs of these messages are

EASE

connection.)

cket call. Before the

e released if there are no other

the Deactivate PDP Context Request

ssage

t over the backbone network

e to route PDP PDUs between

ic parameters and radio resource

ure.

e existing radio links for carrying the

nd the SRNC perform



hen, the RRC connection release




value=hex

value=hex

value=hex

value= Ori

va lue=(-24

>>"RRC Co

>>"Geog rap




value= HS

value=hex

value=hex

value=hex

>>"RRC Co

>>"Geog rap




value=UE

value=UE

value=Sign

v alu e=Rad



value=Sign





value=Sign



value=Sign









v al ue=B LE

value=Max

value=(-48

value= use

value= use



value=Spr

value=Spr

value=Prim



value=Spr

Cell Identit

value= 000

>>"RRC CoRRC:RRC Connection Setup Complete (DCCH)



value=sup

value= Chi



value= sup



value= sup









































































dec (4)=4 , hex 2dec (1)=1 ,hex2d ec(3)=3 --> MCC=413

dec (0)=0 , hex2d ec(1)=1 --> MNC=01

dec (7594)= 30100

inat ingBackgro undCal l (PS MOC)

+ (37/2))=-5.5 dB

nect ion Request Descr ipt ion"

hical and UTRAN Enti ty Ident i f iers"



PA Release5


dec (0)=0 , hex2d ec(1)=1 --> MNC=01

dec (7594)= 30100

nect ion Setup Descr ipt ion"




apable to support FDD , not TDD

apable to supp ort GSM

al ing Radio B earer Informat ion Setup ,RB-1

io Bearer Mapping




















R Target= -20 dB

AllowedULTxPow er=24 dBm

*2)= -96 dBm (step of 2 dB )

Default Constant DPCCH_Power_offset CPICH_RSCP

-22 -96 -80

-22 -96 -70


Closed Loo p Power Cont ro l A lgor i thm1

long SC on Upl ink



ading Factor 64 (Upl ink)

ading Factor 128 (Downl ink)

ary Scrambl ing cod e=30




y=RNCid(12bits)+Cell id(16bits)

000000001 0001010100101111 => RNCid=bin2dec(000000000001)=1 an d Cellid=bin2dec(0001010100101111)=5

nect ion Setup Comp lete Descr ipt ion"



ort GSM (Dual Mod e GSM<>UMTS)

er ing Algor i thm A5/3



port Comp ressed Mode (CM) upl ink and dow nl ink



por t HSDPA, UE Category 6





























value= HSDPA Chann el Informat ion

value= h s-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 H



value= SF256(down l ink)

value= HSDPA Serving Cell 's Prim ary SC = 30

value= SF256(down l ink)

Cell Identi ty=RNCid(12bits)+Cell id(16bits)










value= PrimarySC=30, no longer a HSDPA serv ing cel l ( HSDPA Serving Cel l Change)

(Old HSDPA's Serving Cell)



value= PrimarySC=9 is a n ew HSDPA serv ing cel l ( HSDPA Serving Cel l Change)



(New HSDPA's Serving Cell)






































33 -107 -16

33 -107 -26






423

































S-SCCH channels simultaneously. So one cell only configure up to 4 HS-SCCH channels



01010100101111)=5423









01010100101111)=5423



1000111011100)=4572















































































Prepare


Ready

RRC: Security Mode Completed


L3 Messages - PS(HSUPA)


Start Rx

Start Tx


S-


L1 Syncho nization

UE NodeB







Commit


Prepare


Ready

NBAP: Radio Link ReconfigurationCommit


Prepare


Ready

PS Session Establ is















: a o n econ gurat on

Commit


Request


Response

















>>RRC Proc

all Procedure

NC CN

1.RRC C

2.PS Se







ed

HSPA's S

3. Radio

4. Downl






5.PS Se

6.RRC



RRC connection setup procedure is performed for the


Triggering Conditions : The UE in idle mode intitiates th

SRNC receives an RRC CONNECTION REQUEST messagconnection request, based on a specific algorithm. If accept

(DCH)or on a Common Channel (CCH),based on a specific


1.The UE sends an RRC CONNECTION REQUEST messa

2.Based on the cause in the RRC connection request and th

NetworkTemporary Identity(RNTI),radio resources, and L1 a

allocate the specific radio link resources required for an RR

3.The NodeB responds with a RADIO LINK SETUP RESPO

4.The SRNC uses the ALCAP protocol to set up the Iub use


5.The SRNC sends an RRC CONNECTION SETUP messa6. UE and NodeB initiate L1 Synchronization. NodeB sends

7. The UE sends an RRC CONNECTION SETUP COMPLE


If the RNC judges that the RRC connection request cannot

edure Description

The PS Session Setup procedure is performed to set

Triggering Conditions: The UE send Activate PDP context

Mobility Management Connected that enables the user to tr

virtual data channel between a terminal connected to a UE a

bearer establishes on request of the SGSN in order to realiz


IP addresses can be allocated dynamically or statistically. If

enables subscribers to provide their own IP addresses. This


When dynamic addressing from the home PLMN or the Visi


1. The UE initiates the PS Session by using the Service Req

sets-up an SCCP connection with the SGSN and transfers t

2 .The UE sends an Activate PDP Context Request (NSAPI,

Options) message to the SGSN The UE shall use PDP Add3. The SGSN sends a RAB Assignment Request message t

4.The RNC establishes the appropriate radio bearer In WC

5.The RNC returns a RAB Assignment Response message

6. The SGSN validates the active PDP Context Request usi

records.The SGSN sends a Create PDP Context Request

Name to find an external network and optionally to activate

7. The GGSN creates a new entry in its PDP context table a

the SGSN and the external PDP network, and to start chargi

8.The SGSN inserts the Network layer Service Access Point

onnection Establishment

ssion Setup



The RRC Connection Release procedure is performed to

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

of the UE,the SRNC initiates an RRC connection release pr

The procedure shown is descr ibed as fo l lows: based on

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

a radio bearers fails to be setup ,the RRC connection on th

1.The SRNC sends an RRC CONNECTION RELEASE mes

(NOTE: The SRNC may send the RRC CONNECTION REL

the same. The number of retransmissions and the transmis

COMPLETE message from the UE after sending the RRC

2.The UE sends an RRC CONNECTION RELEASE COMP

The PS session release procedure is performed to rel

Triggering Conditions : The UE send Deactivate PDP co

deactivation,the UE has the state Active. After the PDP Con

PDP contexts activated.PDP Deactivation may be initiated b


1.The UE sends a Deactivate PDP Context Request (TI, Te

2.The SGSN sends a Delete PDP Context Request (TEID,

message, then the SGSN deactivates all PDP contexts asso

3.The GGSN removes the PDP context(s) and returns a del

4.The SGSN returns a Deactivate PDP Context Accept (TI)

5. In Iu mode, radio access bearer release is done by the R6. The SCCP connection between RNC and SGSN is releas

SGSN selects Radio Priority and Packet flow Id based on Q


The Radio Bearer Setup proc edure show n is described


2.(Optional; applicable to the ATM-based Iu-CS interface on

characteristic parameters. Based on the AAL2 link characte

3.The SRNC sends a RADIO LINK RECONFIGURATION PRAB.

4.The NodeB allocates the associated resources and then s


synchronization by exchanging uplink and downlink synchro

6.The SRNC sends a RADIO BEARER SETUP message to

7.The SRNC sends a RADIO LINK RECONFIGURATION C

8.After performing the radio bearer setup, the UE sends a R

9.The SRNC sends an RAB ASSIGNMENT RESPONSE m

The p r ocedu re when RAB Setup Fai lu re shown is desc r


rving Cell Change

earer Setup

ink and Uplink Data Transfer



3.The SRNC sends a RADIO LINK DELETION REQUEST

4.After releasing the resources, the NodeB sends a RADIO


procedure ends.

sion Release

onnection Release



UE to set up a signaling connection to the SRNC. RRC connection setup is always initiated by the U

e RRC connection setup procedure when the NAS of the UE requests the establishment of a signaling

e from the UE, the Radio Resource Management (RRM) module of the RNC determines whether to aing the request, the RRM module further determines whether to set up the RRC connection on a Dedi

RRM algorithm. Typically, an RRC connection is set up on the DCH.

ge to the SRNC through the uplink CCCH(RACH), requesting the establishment of an RRC connection

e system resource status, the SRNC determines to set up the RRC connection on a DCH and allocate

nd L2 resources. Then the SRNC sends a RADIO LINK SETUP REQUEST message to the NodeB, re

connection.

NSE message to the SRNC after successfully preparing the resources.

r plane transport bearer and performs the synchronization between the SRNC and the NodeB. This pro

e to the UE through the downlink CCCH (FACH). The message contains the information about the DNBAP:Synchonization Indicator message to SRNC when the uplink enter "In-Sync" state

E message to the SRNC through the uplink Dedicated Control Channel (DCCH) that is just set up. Th

e set up (for instance, due to insufficient resources), it directly sends an RRC CONNECTION REJEC

p a PS session

request message to RNC. PDP Context Activation is performed when the UE initiates a packet call se

nsmitt and receive data while moving within a PLMN. and starts the PDP context activation procedure

nd a GGSN. PDP contexts deal with allocation of IP addresses to the UE and Quality of Service, QoS,

e the air interface connection. At the end the UE has an IP address NSAPI (Network layer Service Acc

allocated dynamically, this significantly reduces the total number of IP addresses required per PLMN.

can be useful when accesing secure networks that use the calling IP address as a form of security ch

or PLMN is used, it is the responsibility of the GGSN to allocate and release the dynamic PDP addres

uest (Service Type=Data) message. After the RR setup completion the UE asks for initial direct transf

he initial service request (Authentication and ciphering may performed depends on operator's setting)

TI(Teardown Indication), PDP Type, Address, APN (Access Point Name), QoS (Quality of Service) Re

ess to indicate whether it requires the use of a static PDP address or whether it requires the use of a do the RNC to establish a RABs

MA, RAB setup is done by the RAB Assignment procedure

to the SGSN

g PDP Type (optional), PDP Address, APN (Access Point Name (optional) provided by the UE and th

essage to the affected GGSN. Access Point Name shall be the APN Network Identifier of the APN. Th

service for this APN

nd generates a Charging Id. The new entry allows the GGSN to route PDP PDUs (Policy Decision Poin

ng

Identifier, NSAPI along with the GGSN address in its PDP context and informs the UE via RNC that th



release the signaling connection and all radio bearers between UE and the UTRAN

judges whether the RRC connection carries any other RAB or the UE. If judging that the RRC conne

cedure.

the resouce occupied by the RRC connection,there are two types of RRC connection release procedu

C connection needs to be released after a successful outgoing call,, the RRC connection on the DCH

CCH is released)

sage to the UE through the DCCH.

EASE message several times to increase the probability of proper reception of the message by the UE

ion intervals are determined by the SRNC. If the SRNC does not receive an RRC CONNECTION REL

ONNECTION RELEASE message for four times, the SRNC judges that the UE has released the RRC

ETE messa e to the SRNC.

ease services and resources after a session ends.

text request message to RNC. A PDP Context Deactivation is performed when the UE terminates a p

ext deactivation procedure the state becomes Packet Mobility Management Connected.The RAB will

y a:UE procedure,SGSN procedure,GGSN procedure

rdown Indication) message to the SGSN via the RNC

SAPI, Teardown Indication) message to the GGSN. If Teardown Indication was included by the UE in

ciated with this PDP address by including Teardown Indication in the Delete PDP Context Request me

te PDP Context Response (TEID) message to the SGSN. The Delete PDP Context messages are se

message to the UE via the RNC

B Assignment procedureed. At GPRS detach, all PDP contexts for the UE are implicitly deactivated

S Negotiated, and returns an Activate PDP Context Accept message to the UE. The SGSN is now abl

s fo l lows:


ly) The SRNC maps the Quality of Service (QoS) parameters for the RAB to the AAL2 link characteristi

istic parameters,the ALCAP on the Iu interface initiates an Iu user plane transport bearer setup proced

REPARE message to the NodeB, requesting the NodeB to prepare for adding one or more DCHs to th

ends a RADIO LINKRECONFIGURATION READY message to the SRNC.

he Iub ALCAP at the SRNC initiates an Iub user plane transport bearer setup procedure. The NodeB

ization frames in the DCH frame protocol.

the UE.

OMMIT message to theNodeB.

ADIO BEARER SETUP COMPLETE message to the SRNC.

ssage to the CN. The RAB isset up.

bed as fo l lows:




essage to the NodeB,requesting the NodeB to delete the radio link resources in the NodeB.

LINK DELETION RESPONSE message to the SRNC.

he SRNC uses the ALCAP protocol to initiate an Iub user plane transport bearer release procedure. T



. One UE has a

connection When the

cept or reject the RRCated Channel

.

s the Radio

questing the NodeB to

cedure is optional. It

H allocated by the SRNC.

e message

message to

tup. The UE has the state Packet

used to set up and remove a

parameters. A Radio Access

ess Point Identifier) and a TLLI

upport of static IP address allocation

ck. The support of

.

r to the serving node. The RNC

quested, PDP Configuration

ynamic PDP address.

PDP context subscription

e GGSN may use Access Point

t Protocol Data Units) between

e PDP Context is Accepted. The



tion does not carry other RAB

re: release of an RRC connection from

is released and if

. The RRC SNs of these messages are

EASE

connection.)

cket call. Before the

e released if there are no other

the Deactivate PDP Context Request

ssage

t over the backbone network

e to route PDP PDUs between

ic parameters and radio resource

ure.

e existing radio links for carrying the

nd the SRNC perform



hen, the RRC connection release




value=hex

value=hex

value=hex

value= Ori

va lue=(-24

value=Prim

va lue=(-24

RRC:RRC Connection Request (RACH) >>"RRC Co

>>"Geog rap



value= HS

value= UE

value=hex

value=hex

value=hex

>>"Geog rap

RRC:RRC Connection Setup (FACH) >>"RRC Co



value=UE

value=Sign

v alu e=Rad



value=Sign





value=Sign





value=Sign









v al ue=B LE

value=Max

value=(-47

value= use



value= use

value=Spr

value=Spr

value=Prim



value=Spr

Cell Identit

value= 000

RRC:RRC Connection Setup Complete (DCCH)





value= not

value= Chi

value= sup



value= sup


































































































dec (9)=9 , hex2d ec(9)=9 --> MNC=99

dec(03EA)= 1002

inat ingBackgro undCal l (PS MOC)

+ (39/2))=-4.5 dB

ary Scrambl ing Code=60 ( Neighbour 's SC)

+ (37/2))=-5.5 dB

nect ion Request Descr ipt ion"




A Release6

supp ort HSDPA and E-DCH (HSUPA)


dec (9)=9 , hex2d ec(9)=9 --> MNC=99

dec(03EA)= 1002


nect ion Setup Descr ipt ion"



apable to support FDD , not TDD


io Bearer Mapping






















R Target= -20 dB

AllowedULTxPow er=24 dBm

*2)= -94 dBm (step of 2 dB )

Default Constant CCH_Power_off CPICH_RSCP

Closed Loop Power Cont ro l A lgor i thm1 -22 -94 -80

-22 -94 -70

Note :DPCCH_Power_offset is configured by RNC and deliver



long SC on Upl ink

ading Factor 64 (Upl ink)


ary Scrambl ing cod e=60




y=RNCid(12bits)+Cell id(16bits)

001100110 0000010100101001 => RNCid=bin2dec(000001100110)=102 an d Cellid=bin2dec(0000010100101001)=132

>>"RRC Connect ion Setup Com plete Descr ipt ion"





supp ort GSM (Locked UMTS Mode)

er ing Algor i thm A5/3

port Comp ressed Mode (CM) upl ink and dow nl ink



por t HSDPA, UE Category 8


































value= Uplink e-DPDCH (HSUPA) chan nel infor matio n



value= Downl ink HS-PDSCH chann el informat ion



value= HSDPA and HSUPA Serving Cell 's Primary SC = 68











value= PrimarySC=68, no longer a HSDPA & HSUPA serv ing cel l ( HSPA Serving Cel l Change)

value= PrimarySC=60 is a new HSDPA&HSUPA serv ing cel l ( HSPA Serving Cel l Change)



















































PCPICH Power UL Interference CCH Initial Power

33 -105 -14

33 -105 -24

ed to UE in RRC Connection Setup.





1












"or"

Intra-Frequency Soft Hando ver w ithin NodeB(Softer-



RRC:Measurement Report (e1b)

RRC:Measurement Report (e1c)

1.RRC: Active Set Update (DCCH)

2. RRC: Active Set Update Complete (DCCH)



UE NodeB1

RRC:Measurement Report (e1a)

L3 Messages - Intra-Frequency Soft Handover Pr



*Source

"or"









L3 Messages - Intra-Frequency Soft Handover Pr

UE NodeB1 NodeB2


Intra-Frequency Soft Handover b etween NodeBs in a



*Target

"or"

2.NBAP:Radio Link Setup Request

L3 Messages - Intra-Frequency

RRC:Measurement R

RRC:Measuremen

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.

UE D-RNC

In tra-Frequen cy So ft Hando

NodeB2

RRC:Measurement R



3.NBAP:Radio Link Setup Response

1.QAAL2 Establish Request

2.QAAL2 Establish Confirm

1.NBAP:Radio Link Restore Indication

NBAP:Radio Link Deletion Req

NBAP:Radio Link Deletion Resp

QAAL2 Release Request

QAAL2 Release Confirm

RRC:Measurement R

2.RRC: Active Set Update


1.RRC: Active Set Up

RRC:Measuremen


1.RRC: Active Set Up

2. RRC: Active Set Update



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











2.NBAP:Radio Link Setup Resp

1.NBAP:Radio Link Deletion Req

2.NBAP:Radio Link Deletion Resp

Measurem

changed, t

Measurem

the results

HO)

The activ

Triggerin

The proce

1.The SRNdeleted, th

2.The UE

message.

3.The UE

-lf adding

Link Contr

-If the AC

Radio Lin

Decision todelete old

radio link

Radio Lin

Triggering

The proce

1.The CR

the new ra2.The Nod

-If all the r

andsends

-If any rad

Decision to

setup new

radio link

Radio Li

Triggerin

The proce

1.The CR

2.The Nod

-If the radi

-If the radi

>>Intra-Frequency SHO Algorithm and related parameters (Modu

S-RNC

cedure

Radio Link A ddi t ion

Radio Link Deletion

Measurement Contro l

& Measurement Report



Activ e Set Update

Act ive Set Update




*Target



QAAL2 Establish Request

QAAL2 Establish Confirm

NBAP:Radio Link Restore Indication


Measurem

changed, t

Measuremthe results

The Iub u

Triggering

1. The co

2. The dedThe proce

1.The CR

2.The Nod

-If the Iub

-If an Iub

The activ

Triggerin

The proce

1.The SRN

deleted th

The radio

Triggering

The proce

1.The CR

new radio l

2.The Nod-If the radi

RADIOLIN

-If the radi

cedure

S-RNC

Decision to

delete old

radio link


The radio

synchroniz

Triggering

After perfo

Decision to

setup new

radio link

RNC

Radio Link Setup

Act ive Set Update

Radio Link Deletion

Iub user plane Setup

Iub radio l ink restore Indic ation





Activ e Set Update






Click to ret

*Target *Source

Decision

to setup

new radio

link


Radio Li

Triggerin

The proce

1.The CR

2.The Nod

-If the radi

-If the radi

NodeB1

oft Handover Procedure

eport (e1c)

t Control

The Iub u

Triggerin

The proce

1.The CR

2.The Nod

-If the Iub

-lf an Iub

ver between RNCs

2.The UE

message.

3.The UE

-lf adding

Link Contr

-If the AC

Radio Lin

eport (e1a)

1.RNSAP:Radio Link Setup Request

S-RNC

Iub us er plane release

Measur

& Meas



Decision

to delete

old radio

link

eport (e1b)

omplete (DCCH)

ate (DCCH)

t Control


2.RNSAP:Radio Link Restore Indication

4.RNSAP:Radio Link Setup Response

ate (DCCH)


ALCAP: Iur User Plane Setup

omplete (DCCH)

1.RNSAP:Radio Link Deletion Req

Act ive

Iu b us e

Iur Radio

Iur user

Iub Rad

Act ive

Measur

& Meas

Iu b u serelease

Rad io L

Radio







Iu r us









ent Control: is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event

e RNC notifies the UE of new conditions.

ent Report: the UE continue measure the radio link condition of serving and neighbour cell and when the mea

to the RNC as an event. The Measurement report is also can be sent in periodic mode.

e set update procedure is performed to update the active set of radio links between theUE and the UTRAN.

Conditions: The active set update procedure can be triggered in either of the following conditions: Radio link

dure is descr ibed as fo l lows:

C sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicatemessage indicates radio link deletion.

dds or deletes the radio links according to the Radio Link Addition Informationor Radio Link Removal Informatio

ends a response message to the SRNC.

or deleting the radio links successfully, the UE sends an ACTIVE SETUPDATE COMPLETE message on th

l (RLC).

IVE SET UPDATE message contains the configuration not supported by the UE or if the active set does

Removal Information IE, the UE sends an ACTIVE SET UPDATE FAILURE message.

Addition Procedure is performed to add one or more radio links towards a UE.

Conditions: The CRNC sends a RADIO LINK ADDITION REQUEST message.

dure of rad io l ink setup is descr ibed as fo l lows:

C sends a RADIO LINK ADDITION REQUEST message to the NodeB. After receiving the message, the Node

io link or links according to the parameters given in the message. B sends a response message to the CRNC.

equested radio links are added, the NodeB saves the value of the Configuration Generation ID IE contained i

RADIO LINK ADDITION RESPONSE message.

io link fails to be added, the NodeB sends a RADIO LINK ADDITION FAILURE message. The message conta

k Deletion Procedure is performed to release resources in a NodeB for one or more established radio links

Conditions: The CRNC sends a RADIO LINK DELETION REQUEST message.

dure of rad io l ink delet ion is descr ibed as fo l lows:

C sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB d

eB sends a response message to the CRNC.

o link are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message.

o link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The message c

le II)



ent Control: is used to notify the UE of the objects to be measured, neighbor cell list, report method, and event

e RNC notifies the UE of new conditions.

ent Report: the UE continue measure the radio link condition of serving and neighbour cell and when the meato the RNC as an event. The Measurement report is also can be sent in periodic mode.

er plane setup procedure is performed to set up bearers for data transmission on the Iub interface

Conditions: The Iub user plane setup procedure can be triggered in one of the following conditions:

mon transport channels are setup

icated transport channels are setupdure is descr ibed as fo l lows:

C uses the ALCAP protocol to send a QAAL2 ESTABLISH REQUEST messageto the NodeB.

B uses the ALCAP protocol to send a response message to the CRNC.

data transport bearers are set up, the NodeB sends a QAAL2 ESTABLISH CONFIRM message.

ata transport bearer fails to be set up, the NodeB sends a QAAL2 ESTABLISH RELEASE CONFIRM mess

e set update procedure is performed to update the active set of radio links between theUE and the UTRAN.

Conditions: The active set update procedure can be triggered in either of the following conditions: Radio link


C sends an ACTIVE SET UPDATE message to the UE. If a radio link needs to be added, the message indicate

messa e indicates radio link deletion.

link setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up a radio

Conditions: The CRNC sends a RADIO LINK SETUP REQUEST message.

dure of rad io l ink setup is descr ibed as fo l lows:

C sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB re

ink according to the parameters given in the message.

B sends a response message to the CRNC.o link is set up, the NodeB saves the value of the Configuration Generation ID IE contained in the RADIO LIN

K SETUP RESPONSE message.

o link fails to be set up, the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains

link restoration procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed for a Nod

ation of one or more radio links is achieved or re-achieved

Conditions: The nodeB detect UL signals from the UE. That is ,the NodeB finishs UL synchronization with the

rming UL synchronization with the UE, the NodeB sends a RADIO LINK RESTORE INDICATION message to th



urn to main page

The radio link setup procedure for inter-RNC handover is performed to

Triggering Conditions: The SRNC sends a RADIO LINK SETUP REQU


1.The SRNC sends a RADIO LINK SETUP REQUEST message to the DR

2.The DRNC sends a RADIO LINK SETUP REQUEST message to the tar

3.The NodeB reserves the necessary resources and configures the new ra

k Deletion Procedure is performed to release resources in a NodeB for one or more established radio links

Conditions: The CRNC sends a RADIO LINK DELETION REQUEST message.

dure of rad io l ink delet ion is descr ibed as fo l lows:

C sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the NodeB d

eB sends a response message to the CRNC.

o link are deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message.

o link fails to be deleted, the NodeB sends a RADIO LINK DELETION RESPONSE message. The message c

ser plane release procedure is performed to release data transport bearers from the Iub interface.

Conditions: The transport channels on the Iub user plane need to be removed


C uses the ALCAP protocol to send a QAAL2 RELEASE REQUEST messageto the NodeB.

eB uses the ALCAP protocol to send a response message to the CRNC.

data transport bearers are released, the NodeB sends a QAAL2 RELEASE CONFIRM message to confirm th

ata transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message that indi

dds or deletes the radio links according to the Radio Link Addition Informationor Radio Link Removal Informatio

ends a response message to the SRNC.

or deleting the radio links successfully, the UE sends an ACTIVE SETUPDATE COMPLETE message on th

l (RLC).

IVE SET UPDATE message contains the configuration not supported by the UE or if the active set does

Removal Information IE, the UE sends an ACTIVE SET UPDATE FAILURE message.

Measurement Control: is used to notify the UE of the objects to be meas

changed, the RNC notifies the UE of new conditions.

Measurement Report: the UE continue measure the radio link condition o

results to the RNC as an event. The Measurement report is also can be seement Contro l

urement Report



The Iur user plane setup procedure is performed to set up bearers for d

Triggering Conditons: The DCHs are set up


1.The SRNC uses the ALCAP protocol to send a QAAL2 ESTABLISH RE

2.The DRNC uses the ALCAP protocol to send a response message to the

-If the Iur data transport bearers are set up, the DRNC sends a QAAL2

-If an Iur data transport bearer fails to be set up, the DRNC sends a Q

The active set update procedure is performed to update the active set of

Triggering Conditions: The active set update procedure can be triggered


1.The SRNC sends an ACTIVE SET UPDATE message to the UE. If a rad

themessage indicates radio link deletion.

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 Configuratio

SETUP RESPONSE message.

-If the radio link fails to be set up , the NodeB sends a RADIO LINK SET

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 RES

-If the radio link fails to be set up, the DRNC sends a RADIO LINK SET

The Iub user plane setup procedure is performed to set up bearers for d

Triggering Conditions: The Iub user plane setup procedure can be tri

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 RE

2.The NodeB uses the ALCAP protocol to send a response message to th

-If the Iub data transport bearers are set up, the NodeB sends a QAAL2-If an Iub data transport bearer fails to be set up , the NodeB sends a Q

The radio link restoration procedure for inter-RNC handover is perfor

achieved or re-achieved.

Triggering Conditons: The NodeB detects UL signals from the UE. That i


1.After performing UL synchronization with the UE, the NodeB sends a RA

2.The DRNC sends a RADIO LINK RESTORE INDICATION message to t

et Update

plane Setup

Link Restore Indication

plane Setup

io Link Restore Indication

et Update

ement Contro l

urement Report

r plane

ink Setup

Link Deletion



. e a s or e e es e ra o n s accor ng o e a o n


-lf adding or deleting the radio links successfully, the UE sends an AC

Control (RLC).

-If the ACTIVE SET UPDATE message contains the configuration not

Link Removal Information IE, the UE sends an ACTIVE SET UPDATE F

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

Triggering Conditions: The CRNC sends a RADIO LINK DELETION RE


1.The CRNC sends a RADIO LINK DELETION REQUEST message to the

2.The NodeB sends a response message to the CRNC.

-If all the radio links are deleted, the NodeB sends a RADIO LINK DELE

-If any radio link fails to be deleted, the NodeB sends a RADIO LINK DE

cause.

The Iub user plane release procedure is performed to release data trans

Triggering Conditions: The transport channels on the Iub user plane nee


1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQU


-If the Iub data transport bearers are released, the NodeB sends a QAA

-If an Iub data transport bearer fails to be released, the NodeB sends a

The Iur user plane release procedure is performed to releaseto release

Triggering Conditions: The transport channels on the Iub user plane nee


1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE REQU


-If the Iub data transport bearers are released, the NodeB sends a QAA

-If an Iub data transport bearer fails to be released, the NodeB sends a

r plane release









parameters.When measurement conditions are

urement reporting criterias are met, the UE reports

ddition or Radio link deletion

s radio link addition. If a radio link needs to be

n IE contained in the ACTIVE SET UPDATE

e DCCH by using Acknowledged Mode (AM)Radio

not contain the radio links specified by the

reserves the necessary resources and configures

the RADIO LINK ADDITION REQUEST message

ins the failure cause in the Cause IE.

towards a UE

letes the radio links specified by the message

ontains the failure cause.



s

parameters.When measurement conditions are

urement reporting criterias are met, the UE reports

ge.

ddition or Radio link deletion

s radio link addition. If a radio link needs to be

link in an SRNC-controlled NodeB for a UE

serves the necessary resources and configures the

SETUP REQUEST message and sends a

the failure cause.

B to notify the CRNC that the uplink

UE

e CRNC.



set up a radio link in a DRNC-controlled NodeB for a UE

ST message

NC.

et NodeB.

dio link accordingto the parameters given in the message.

towards a UE

letes the radio links specified by the message

ontains the failure cause.

e release.

cates the failure cause

n IE contained in the ACTIVE SET UPDATE

e DCCH by using Acknowledged Mode (AM)Radio

not contain the radio links specified by the

red, neighbor cell list, report method, and event parameters.When measurement conditions are

f serving and neighbour cell and when the measurement reporting criterias are met, the UE reports the

nt in periodic mode.



ta transmission on the Iur interface

UEST messageto the DRNC.

SRNC.

ESTABLISHCONFIRM message.

AL2 ESTABLISHRELEASE CONFIRM message.

radio links between the UE and the UTRAN.

in either of the following conditions: Radio link addition or Radio link deletion

io link needs to be added, the message indicates radio link addition. If a radio link needs to be deleted,

GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK

UP FAILURE message.

ONSEmessage.

P FAILUREmessage, indicating the failure cause.

ata transmission on the Iub interface

ggered in one of the following conditions:

UEST messageto the NodeB.

CRNC.

ESTABLISH CONFIRM message.AL2 ESTABLISH RELEASE CONFIRM message.

ed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is

is, the NodeB finishes UL synchronizationwith the UE.

DIO LINKRESTORE INDICATION message to the DRNC.

e SRNC.



on n orma onor a o n emova n orma on con a ne n e message.

IVE SETUPDATE COMPLETE message on the DCCH by using Acknowledged Mode (AM)Radio Link

upported by the UE or if the active set does not contain the radio links specified by the Radio

ILURE message.

NodeB for one or more established radio links towards a UE.

UEST message.

NodeB. After receiving the message, the NodeB deletes the radio links specified by the message.

ION RESPONSE message

LETIONRESPONSE message. The Criticality Diagnostics field in the message indicates the failure

port bearers from the Iub interface.

d to be removed.

EST messageto the NodeB.

CRNC.

L2 RELEASECONFIRM message to confirm the release.

QAAL2 RELEASECONFIRM message that indicates the failure cause.

ata transport bearers from the Iur interface.

d to be removed.

EST messageto the NodeB.

CRNC.

L2 RELEASECONFIRM message to confirm the release.

QAAL2 RELEASECONFIRM message that indicates the failure cause.




















































RRC: Active Set Update (DCCH)



RRC: Active Set Update Complete (DCCH)





RRC: Active Set Update (DCCH)



RRC: Active Set Update Complete (DCCH)



value=int raFrequencyMeasurement

value=int raFrequencyCel l L ist

value=IntraFreqCellID of Serving Cell=0

value=Primary Scrambl in g Code o f Serv ing Cel l=74

>>"Measurement Control and Measurement Report"



value=Int raFreqCel l ID of Serv ing 1st neighbo urCel l=1

value=CIO=0 (No of fset on this neigh bour cel l )

value=Primary Scrambl in g Code o f 1st Neighbour Cel l=106

















value=Intra-freq meas L3 filter coeff=3

value=Intra-freq Measure Quan tity u se CPICH Ec/No

>>Int ra-Frequency SHO Algo r i thm and related parameters (Module I I)



val ue=event 1a tr ig ger ed by det ec ted and Mon i to rSe t Cel ls ( DETSET_ADD_TO_ACTSET_SWITCH and DETSET_RPR _

value=3 dB (IntraRelThdFo r1A),step: 0.5

value=0

value=Maximum act ive set size =3 ( i f number o f cel l in Ac t ive Set more than 2 then cann ot t r igger e1a)

value=16

value=4000ms

value=0

value=320ms

value=UE repor t All Ac tive Set Cells + 6 Monito r/Detected Set Cells

value=event1b tr iggered b y Ac t ive Set Cells Only

value=6 dB (IntraRelThd For1B) ,step: 0.5

value=0

value=0

value=640ms

value=UE report Al l 3 Acti ve Set Cells

value=event1C tr iggered when A ct ive Set is ful l (Maximum 3 cel ls in Ac t ive Set)

value=16

value=4000ms

value=4 dB (1C hysteres is),step: 0.5

value=640ms

value=UE repor t All Ac tive Set Cells + 6 Monito r/Detected Set Cells

value=4dB (1D hys teresis),step: 0.5

value=640ms



value=UE report Al l Active Set Cells +3 Monito r Set Cells

value=event1f t r iggered by Act ive Set Cel ls Only

value= 1F event absolute EcNo th reshold = -24 dB

value= 4 dB ,step: 0.5

value=640ms

value=UE report Al l 3 Acti ve Set Cells

>>"Measurement Report"



valu e=CPICH Ec/No= -24+(25/2) = -11.5 dB

value=CPICH RSCP= -115+32= -83 dBm





value=Event1a is t r iggered

value=To add neighbou r Pr imary Scrambl ing Cod e=13 into Act ive Set









value=Event1b is t r iggered

value=To delete neighbou r Pr imary Scrambl ing Cod e=74 from Ac t ive Set







valu e=CPICH Ec/No= -24+(20/2) = -14 dB




valu e=CPICH Ec/No= -24+(8/2) = -20 dB


value=Event1c is t r iggered

value=To replace Cell Pr imary Scramb l ing Co de=56 by Cel l Pr imary Scrambl ing Code=106

































_ _SWITCH is " Ac ti ve" )




*Source

2.NBAP:Radio Lin

L3 Messages - Intra-Frequency Hard Handover

UE NodeB1 Nod

In t ra-Frequency Hard Handover between NodeBs i



Start

Start

1.RRC: Physical Channel Reconfiguration (DCCH)

2. RRC:Physical Channel Reconfiguration Complete (DC

1.NBAP:Radio Lin

Stop Rx/Tx



*Target




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


ALCAP: Iub User

1.QAAL2 Rele

2.QAAL2 Rele

D-R

In tra-Frequency Hard Ha

RRC:Measure

L3 Messages - Intra-Frequenc

NodeB2UE

RRC:Measureme

Start Rx







Start Tx

2. RRC:Physical Channel Recon

1. RRC:Physical Channel





2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface






*Target






k Deletion Resp

>>Intra-Frequency HHO Algorithm and related parameters

Procedure

B2 S-RNC

a RNC

Tx

Decision todelete old

radio link

Decision to

setup new

radio link

Rx


H)

k Deletion Req

Radio Link Setup

Physical Reconfigu ration

Radio Link Deletion


Iub radio l ink restore Indication


& Measurement Repor t



*Target *Source *S

Plane Release

se Request

se Confirm

>>

C NodeB1

dover between RNCs

ent Control

Hard Handover Procedure

S-RNC

t Report (e1d)


Decision to

setup new

radio link






1.QAAL2 Release Request

2.QAAL2 Release Confirm

Stop

Rx/Tx







figuration Complete (DCCH)

Decision to

delete old

radio link



econfiguration (DCCH)






The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interf


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.lIf the Iub data transport

ESTABLISH CONFIRM message.If an Iub data transport bearer fails to be set up, the NodeB sends a QA

Measurement Contro l is used to notify the UE of the objects to be measured, neighbor cell list, report met

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

met, the UE reports the results to the RNC as an event. The Measurement report is also can be sent in peri

The rad io l ink setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to

for a UE

The procedure of rad io l ink setup is descr ibed as fo l lows:

1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the messag

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 valu

in the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SETUP RESPONSE message.I

sends a RADIO LINK SETUP FAILURE message. The message contains the failure cause.

The radio l ink restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)is performe

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

The physica l ch annel reconf igurat ion procedure is performed to set up, reconfigure, or releasea physica


1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfig

2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sen

->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGUR

CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC




urce

The radio l ink deletion procedure is performed to release resources in a NodeB for one or more establish


1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the mes

by the message.

2.The NodeB sends a response message to the CRNC.lf all the radio links are deleted, the NodeB sends a

message.

3. lf any radio link fails to be deleted, the NodeB sends a R ADIO LINK DELETION RESPONSE message.

indicates the failure cause.

easurement Control&Report Description

The Iub us er plane release procedure is performed to release data transport bearers from the Iubinterfac


1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE 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 released, the NodeB sends a QAAL2 RELEASE CONFIRM messag

->lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM mes

->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATIO

the old physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE

value of the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE mes

Measurement Control is used to notify the UE of the obje

notifies the UE of new conditions.

Measurement Report, the UE continue measure the radi

the RNC as an event. The Measurement report is also can

The radio link setup procedure for inter-RNC handover is pThe procedure is descr ibed as fo l lows:

1.The SRNC sends a RADIO LINK SETUP REQUEST me

2.The DRNC sends a RADIO LINK SETUP REQUEST me

3.The NodeB reserves the necessary resources and confi

DRNC.

->If the radio link is set up, the NodeB saves the value of t

RESPONSE message.

->If the radio link fails to be set up, the NodeB sends a RA

4.The DRNC reports the radio link setup result to the SRN





The Iub user plane setup procedure is performed to set


1.The CRNC uses the ALCAP protocol to send a QAAL2

2.The NodeB uses the ALCAP protocol to send a respons

->If the Iub data transport bearers are set up, the NodeB s

->If an Iub data transport bearer fails to be set up, the Nod

The r adio l ink restoration procedure for inter-RNC hand

achieved.

1.After performing UL synchronization with the UE, the No

2.The DRNC sends a RADIO LINK RESTORE INDICATIO

-> e ra o n s se up, e sen s a

->If the radio link fails to be set up, the DRNC sends a RA

The physica l ch annel reconf iguration procedure is perf


1.The SRNC sends a PHYSICAL CHANNEL RECONFIGU

2.The UE saves the IEs of the UE, Radio Bearer (RB), tra

->If successfully reconfiguring the physical channels specif

COMPLETE message on the uplink DCCH by using AM R

->If failing to reconfigure the physical channels specified b

configuration and sends a PHYSICAL CHANNEL RECON

CHANNEL RECONFIGURATION FAILURE message is "p

The radio l ink deletion procedure is performed to releas


1.The CRNC sends a RADIO LINK DELETION REQUES


->lf all the radio links are deleted, the NodeB sends a RAD

->lf any radio link fails to be deleted, the NodeB sends a R

The Iur user plane setup procedure is performed to set u


1.The SRNC uses the ALCAP protocol to send a QAAL2 E

2.The DRNC uses the ALCAP protocol to send a response

->If the Iur data transport bearers are set up, the DRNC se

->If an Iur data transport bearer fails to be set up, the DRN

Physica l Reconf igurat ion


Iur Radio Link Restore Indication

Iur user plane Setup

Iub Radio Link Restor e Indication

Radio Link Deletion


Radio Link Setup

Iur us er plane release



The Iur us er plane release procedure is performed to rel


1.The SRNC uses the ALCAP protocol to send a QAAL2


->If the Iur data transport bearers are released, the DRNC

->If an Iur data transport bearer fails to be released, the D

The Iub us er plane release procedure is performed to rel




->If the Iub data transport bearers are released, the Node

->lf an Iub data transport bearer fails to be released, the N



ace

bearers are set up, the NodeB sends a QAAL2

L2 ESTABLISH RELEASE CONFIRM message.

hod, and event parameters.When measurement

when the measurement reporting criterias are

iodic mode.

et up a radio link in an SRNC-controlled NodeB

, the NodeB reserves the necessary resources

of the Configuration Generation ID IE contained

f the radio link fails to be set up, the NodeB

for a NodeB to notify the CRNC that the uplink

message to the CRNC.

l channel

uration of a physical channel.

ds a response message to the SRNC.

TION message, the UE sends a PHYSICAL



ed radio links towards a UE.

sage, the NodeB deletes the radio links specified

RADIO LINK DELETION RESPONSE

he Criticality Diagnostics field in the message

.

to confirm the release.

age that indicates the failure cause

message, the UE restores the configuration to

message on the DCCH by using AM RLC. The

age is "physical channel failure".

cts to be measured, neighbor cell list, report method, and event parameters.When measurement conditions

link condition of serving and neighbour cell and when the measurement reporting criterias are met, the UE r

be sent in periodic mode.

erformed to set up a radio link in a DRNC-controlled NodeB for a UE

ssage to the DRNC.

ssage to the target NodeB.

ures the new radio link according to the parameters given in the message.The NodeB reports the radio link

e Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a R

DIO LINK SETUP FAILUREmessage.

C.



p bearers for data transmission on the Iub interface

STABLISH REQUEST messageto the NodeB.


ends a QAAL2 ESTABLISH CONFIRM message.

eB sends a QAAL2 ESTABLISH RELEASE CONFIRM message

ver is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is

eB sends a RADIO LINKRESTORE INDICATION message to the DRNC.

N message to the SRNC.

message.

IO LINK SETUP FAILURE message, indicating the failure cause.

ormed to set up, reconfigure, or releasea physical channel

RATION message to the UE to request reconfiguration of a physical channel.

sport channel, and physical channel.The UE sends a response message to the SRNC.

ied by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSICAL CHANNELRE

LC

the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old phy

IGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failure cause IE contain

hysical channel failure".

resources in a NodeB for one or more established radio links towards a UE.

message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the me

IO LINK DELETION RESPONSE message.

ADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message indicates the

p bearers for data transmission on the Iur interface

STABLISH REQUEST message to the DRNC.

message to the SRNC.

nds a QAAL2 ESTABLISHCONFIRM message.

C sends a QAAL2 ESTABLISHRELEASE CONFIRM message.



ase data transport bearers from the Iur interface

ELEASE REQUEST messageto the DRNC.


sends a QAAL2 RELEASECONFIRM message to confirm the release.

NC sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.

ease data transport bearers from the Iubinterface.

ELEASE REQUEST messageto the NodeB.


sends a QAAL2 RELEASE CONFIRM message to confirm the release.

odeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause





are changed, the RNC

eports the results to

etup result to the

DIOLINK SETUP



achieved or re-

CONFIGURATION

icalchannel

d in the PHYSICAL

sage.

ailure cause.






*Source

RRC:Physical Channel Reconfiguration (DCCH)

L3 Messages - Inter-Frequency Hard Handover Pr

UE NodeB1 NodeB2

Inter-Frequency Hard Handover between NodeBs in a






NBAP: Compressed Mod


NBAP: Radio Link Reconfig

NBAP: Radio Link Reconfi

NBAP: Radio Link Reconfig

Start Rx



2.NBAP:Radio Link De

*Target

Stop Rx/Tx


1.The radio link setup procedure shown in the figure applies when the source and target cellsof thehandover 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 interface


UE

1.RRC: Physical Channel Reconfiguration (DCCH)

2. RRC:Physical Channel Reconfiguration Complete (DCCH)

Start Tx

1.NBAP:Radio Link De

ALCAP: Iub User Plan

1.QAAL2 Release

2.QAAL2 Release

L3 Messages - Inter-Frequency H

NodeB2 D-RNC








Start Rx

In ter-Frequen cy Hard Hando

Start Tx

1. RRC:Physical Channel Reco

2. RRC:Physical Channel Reconfigur






2. If IP transport is applied to the Iub interface, no ALCAP procedure is performed on the Iub interface






*Target






>>Intrer-Frequency HHO Algorithm and related parameters

cedure

S-RNC

NC

Decision to

setup new

radio link

>>Compressed Mode Description Module II

e Command

uration Prepare

uration Ready

uration Commit


Radio Link Setup


Iub radio l ink restore Indication


& Measurem ent Report

Ini t ia l Comp ressed Mode Configu ration

Inter-Freq Neighb our cel ls measurement



letion Resp

*Target *Source *Source

letion Req

Decision to

delete old

radio link

e Release

equest

onfirm

ard Handover Procedure

NodeB1 S-RNC

Physical Reconfigu ration


Radio Link Deletion





Decision to

setup new

radio link

ver between RNCs

figuration (DCCH)

ation Complete (DCCH)

Stop

Rx/Tx






Decision to

delete oldradio link

Phys ic

Iub us

Iu r Radio L i

Iub R

Radio

Rad i










Iub u

Iu r u



Measurement Contro l is used to notify the UE of the objects to be measured, neighbor cell list, report method,

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 UE reports the results to the RNC as an event. The Measurement report is also can be sent in periodic mode

The rad io l ink setup procedure (intra-RNC handover or GSM to WCDMA CS handover) is performed to set up

UE

The procedure of rad io l ink setup is descr ibed as fo l lows:

1.The CRNC sends a RADIO LINK SETUP REQUEST message to the NodeB. After receiving the message, the

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 t

the RADIO LINK SETUP REQUEST message and sends a RADIOLINK SETUP RESPONSE message.If the ra

RADIO LINK SETUP FAILURE message. The message contains the failure cause.

Compressed Mode was introduced to WCDMA to allow inter-frequency and Inter-RAT Handovers. It is used to

during which neighbour cells measurements on another frequency can be made.

The Iub user plane setup procedure is performed to set up bearers for data transmission on the Iub interface


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.lIf the Iub data transport bear

ESTABLISH CONFIRM message.If an Iub data transport bearer fails to be set up, the NodeB sends a QAAL2 E

The radio l ink restoration procedure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a

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 mes

The physica l ch annel reconf iguration procedure is performed to set up, reconfigure, or releasea physical cha





1.The SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguratio

2.The UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.The UE sends a

->If successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATIO

CHANNELRECONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC

->If failing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION me

old physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message

the Failure cause IE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is "physi

The radio l ink deletion procedure is performed to release resources in a NodeB for one or more established ra


1.The CRNC sends a RADIO LINK DELETION REQUEST message to the NodeB. After receiving the message,

the message.

2.The NodeB sends a response message to the CRNC.lf all the radio links are deleted, the NodeB sends a RAD

3. lf any radio link fails to be deleted, the NodeB sends a R ADIO LINK DELETION RESPONSE message. The

indicates the failure cause.

The Iub us er plane release procedure is performed to release data transport bearers from the Iubinterface.


1.The CRNC uses the ALCAP protocol to send a QAAL2 RELEASE 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 released, the NodeB sends a QAAL2 RELEASE CONFIRM message to c

->lf an Iub data transport bearer fails to be released, the NodeB sends a QAAL2 RELEASECONFIRM message



The Iub user plane setup procedure is performed to set



2.The NodeB uses the ALCAP protocol to send a respons->If the Iub data transport bearers are set up, the NodeB s

->If an Iub data transport bearer fails to be set up, the Nod

The radio link setup procedure for inter-RNC handover is p


1.The SRNC sends a RADIO LINK SETUP REQUEST me

2.The DRNC sends a RADIO LINK SETUP REQUEST me

3.The NodeB reserves the necessary resources and confi

DRNC.

->If the radio link is set up, the NodeB saves the value of t

RESPONSE message.->If the radio link fails to be set up, the NodeB sends a RA

4.The DRNC reports the radio link setup result to the SRN

->If the radio link is set up, the DRNC sends a RADIO LIN

->If the radio link fails to be set up, the DRNC sends a RA

The Iur user plane setup procedure is performed to set u


1.The SRNC uses the ALCAP protocol to send a QAAL2 E


->If the Iur data transport bearers are set up, the DRNC se

->If an Iur data transport bearer fails to be set up, the DRN

The r adio l ink restoration procedure for inter-RNC hand

achieved.

1.After performing UL synchronization with the UE, the No

2.The DRNC sends a RADIO LINK RESTORE INDICATIO

The physica l ch annel reconf iguration procedure is perf

The procedure is descr ibed as fo l lows: 1.The SRNC sends a PHYSICAL CHANNEL RECONFIGU

2.The UE saves the IEs of the UE, Radio Bearer (RB), tra

->If successfully reconfiguring the physical channels specif

COMPLETE message on the uplink DCCH by using AM R

->If failing to reconfigure the physical channels specified b

configuration and sends a PHYSICAL CHANNEL RECON

CHANNEL RECONFIGURATION FAILURE message is "p

al Reconfigu ration

er plane Setup

nk Restore Indication

Iur user plane Setup

dio L ink Restore Ind icat ion

Link Deletion

o Link Setup



The Iur us er plane release procedure is performed to rel


1.The SRNC uses the ALCAP protocol to send a QAAL2


->If the Iur data transport bearers are released, the DRNC

->If an Iur data transport bearer fails to be released, the D

The radio l ink deletion procedure is performed to releas


1.The CRNC sends a RADIO LINK DELETION REQUES


->lf all the radio links are deleted, the NodeB sends a RAD

->lf any radio link fails to be deleted, the NodeB sends a R

The Iub us er plane release procedure is performed to rel




->If the Iub data transport bearers are released, the Node

->lf an Iub data transport bearer fails to be released, the N

er plane release

er plane release



and event parameters.When measurement

the measurement reporting criterias are met,

.

a radio link in an SRNC-controlled NodeB for a

NodeB reserves the necessary resources and

e Configuration Generation ID IE contained in

io link fails to be set up, the NodeB sends a

create idle periods (gaps) in the transmission

ers are set up, the NodeB sends a QAAL2

STABLISH RELEASE CONFIRM message.

NodeB to notify the CRNC that the uplink

age to the CRNC.

nnel



n of a physical channel.

response message to the SRNC.

N message, the UE sends a PHYSICAL

ssage, the UE restores the configuration to the

on the DCCH by using AM RLC. The value of

al channel failure".

dio links towards a UE.

, the NodeB deletes the radio links specified by


riticality Diagnostics field in the message

nfirm the release.

hat indicates the failure cause



p bearers for data transmission on the Iub interface

STABLISH REQUEST messageto the NodeB.

message to the CRNC.ends a QAAL2 ESTABLISH CONFIRM message.

eB sends a QAAL2 ESTABLISH RELEASE CONFIRM message

erformed to set up a radio link in a DRNC-controlled NodeB for a UE

ssage to the DRNC.

ssage to the target NodeB.

ures the new radio link according to the parameters given in the message.The NodeB reports the radio link

e Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST message and sends a R

DIO LINK SETUP FAILUREmessage.

C.

SETUP RESPONSEmessage.

IO LINK SETUP FAILURE message, indicating the failure cause.

p bearers for data transmission on the Iur interface

STABLISH REQUEST message to the DRNC.


nds a QAAL2 ESTABLISHCONFIRM message.

C sends a QAAL2 ESTABLISHRELEASE CONFIRM message.

ver is performed for a NodeB to notify the SRNC that the uplink synchronization of one or more radio links is

eB sends a RADIO LINKRESTORE INDICATION message to the DRNC.

N message to the SRNC.

ormed to set up, reconfigure, or releasea physical channel

RATION message to the UE to request reconfiguration of a physical channel.

sport channel, and physical channel.The UE sends a response message to the SRNC.

ied by the PHYSICALCHANNEL RECONFIGURATION message, the UE sends a PHYSICAL CHANNELRE

LC

the PHYSICAL CHANNELRECONFIGURATION message, the UE restores the configuration to the old phy

IGURATION FAILURE message on the DCCH by using AM RLC. The value of the Failure cause IE contain

hysical channel failure".



ase data transport bearers from the Iur interface

ELEASE REQUEST messageto the DRNC.


sends a QAAL2 RELEASECONFIRM message to confirm the release.

NC sends a QAAL2 RELEASECONFIRM message that indicates the failure cause.

resources in a NodeB for one or more established radio links towards a UE.

message to the NodeB. After receiving the message, the NodeB deletes the radio links specified by the me


ADIO LINK DELETION RESPONSE message. The Criticality Diagnostics field in the message indicates the

ease data transport bearers from the Iubinterface.

ELEASE REQUEST messageto the NodeB.


sends a QAAL2 RELEASE CONFIRM message to confirm the release.

odeB sends a QAAL2 RELEASECONFIRM message that indicates the failure cause







etup result to the

DIOLINK SETUP

achieved or re-

CONFIGURATION

icalchannel

d in the PHYSICAL



sage.

ailure cause.




NBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

NBAP: Radio Link Reconfiguration Commit

NBAP: Compressed Mode Command

S-RNC

7.RRC: Handover from UTRAN Command




In ter-RAT CS Han

2. RRC: Physical Channel Reconfiguration Complete (DCCH)


Decision

to HO to

GSM cell

1. RRC:Physical Channel Reconfiguration (DCCH)

RRC:Measurement Report (e2f)



NodeB

L3 Messages - Inte

UE



NBAP:Radio Link Deletion Request

NBAP:Radio Link Deletion Response



5.NBAP:Radio Link setup Response

9.Han

In ter-RAT CS Han

UE NodeB S-RNC

L3 Messages - Inte


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.




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 hasbeen 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

17.RRC: Security Mode Complete(DCCH)

23.RRC: UTRAN Mobility Information (DCCH)

9.Inter-System to

12.RRC: Handover to UTRAN Complete(DCCH)

13.RRC: UE Capability Enquiry(DCCH)

14.RRC: UE Capability Information (DCCH)

16.RRC: Security Mode Command(DCCH)

15.RRC: UE Capability Information Confirm (DCCH)







1.RANAP: Relocation Required

2.Prepare Handover

3.Handover Request

4.Handover Request

Acknowledge

5.Prepare Handover

Response

6.RANAP:Relocation Command

MSC

2G

over from WCDMA to GSM

MSC 3G

r-RAT Handover Procedure



8.Handover Detect

10.Handover Complete

11.Send End Signal

Request

12.RANAP: IU Release Command

13.RANAP: IU Release Complete

14.Send End Signal

Response

1.Handover Required

2.Prepare Handover

3.RANAP: Relocation Request

6.RANAP:Relocation Request

Acknowledge

7.Prepare Handover

Response

dover Completed

over from GSM to WCDMA

MSC-2GMSC-3G

r-RAT Handover Procedure



8.Handover Command

9.Handover Complete

11.RANAP:Relocation Detect

. : e oca on

Complete

19.Send End Signal

Request

20.Clear Command

21.Clear Complete

22.Send End Signal

Response

UTRAN Handover Command







The Inter-RAT Handover procedu

1. The SRNC sends the 3G MSC a

2. As indicated in the received mes

Handover"

3. The 2G MSC forwards the reque

4. The BSC responds to this reque

5. Once the initial procedures are c

6. The 3G MSC sends the SRNC a

7. The SRNC send the UE and RR

several other systems

8. The BSC performs handover de

reference and is subject to the act

9. The UE send the BSC a "Hando

10. The BSC sends the MSC a 'Ha

Measurement Contro l is used tochanged, the RNC notifies the UE

Measurement Report, the UE co

the results to the RNC as an event.

Compressed Mode was introduce

neighbour cells measurements on

>>Compressed Mode Description

The relocation preparation proce

The procedur e is described as f

1.The SRNC sends a RELOCATIO

source LAC,source SAC, target PL

2.The CN interacts with the target

3.The CN sends a response mess

->If the target RNC or the target necomplete. The message contains t

->If the resources partially or totall

BSC

2G

>>Measurement Control&Report (Inter-RAT) Description

>>Inter-RAT HO Algorithm and related parameters


& Measurement Repor t

Ini t ia l Comp ressed Mode Configu ration

GSM RSSI Measurem ent

and BSIC Veri f ication

Relocation Preparation



The radio l ink deletion procedure


1.The CRNC sends a RADIO LINK

2.The NodeB sends a response m

->If all the radio links are deleted, t

->If any radio link fails to be delete

cause.

11. After detecting the UE in the co

12. The CN sends the former SRN

13. After the bearer resource is rel

14. After the call ends, the CN sen

The Iu release procedure is perfor


1.The CN sends an IU RELEASE

connection.

NOTE: After sending the IU RELE

2.The SRNC releases the related

BSC

2G

The relocation resourc e al locati

The relocation resource allocation

1. During an SRNS relocation, the

2. During an inter-RAT CS handov


1.The CN sends a RELOCATION

cell identifier, encryption, integrity p

2.The target RNC allocates radio r

3.The target RNC sends a respons

->If the resources are allocated, th

parameters allocated to the UE. Th

encryption algorithm, and chosen i

->If the resources artiall or totall

>>Inter-RAT HO Algorithm and related parameters

Handover

Iu release

Radio Link Delet ion

Relocation Resource al location



The secur i ty mode contro l proce

triggered conditon is when the ciph


1.Through a SECURITY MODE C

theRBs or one CN domain and for

2.The UE sends a response mess

->If the UE completes configuring

COMPLETE message to inform th

->If the SECURITY MODE COMM

information, the UE sends a SECU

The UTRAN m obi l i ty in format ion

TemporaryIdentifier (C-RNTI) to a

1.The SRNC sends a UTRAN MO

2.The UE starts to update the relat

3.The UE sends a response mess

The UE capabi l i ty enquiry proce

data configuration based on the U


1.The SRNC sends a UE CAPABI

2.The UE sends a UE CAPABILIT

capabilities.

3.The SRNC reads the UE capabiliUMRLC.

The radio l ink setup procedure (i


1.The CRNC sends a RADIO LINK

new radio link according to the par2.The NodeB sends a response m

->If the radio link is set up, the Nod

LINK SETUP RESPONSE messag

->If the radio link fails to be set up,

The radio l ink restoration proced

one or moreradio links is achieved

After performing UL synchronizatio

FAILURE message,indicating the f

UTRAN Mobil i ty Information

Radio Link Restoration

UE Capabi l i ty Enqu iry

Securi ty Mode Contro l



->If the UE succeeds in conducting

CONFIRM message.

->If the UE fails to conduct the ope

message, indicating the failure cau





re is described as follows:

RANAP message "Relocation Required" if the condition of Inter-RAT Outgoing HO is met

sage,the 3G MSC forwards this request to the 2G MSC on the MAP/E interface through a MAP message "Pre

st to the BSC. The message shown in the figure is for reference only and is subject to the actual conditon of th

st. The message shown in the figure is for reference only and is subject to the actual conditon of the GSM

ompleted in the 2G MSC/BSS,the 2G MSC returns a MAP/E message 'Prepare Handover Response"

RANAP message "Relocation Command"

C message "Handover from UTRAN" through the existing RRC connection. This message may include inform

ection. The figure does not show such procedures as GSM BSS synchronization. The message shown in the fi

ual conditon of GSM

er Complete" message

ndover Complete" message. The message shown in the figure for reference only and is subject to the actual c

otify the UE of the objects to be measured, neighbor cell list, report method, and event parameters.When mef new conditions.

tinue measure the radio link condition of serving and neighbour cell and when the measurement reporting crite

. The Measurement report is also can be sent in periodic mode.

d to WCDMA to allow inter-frequency and Inter-RAT Handovers. It is used to create idle periods (gaps) in the t

another frequency can be made.

dure is performed to prepare resources for relocation of the SRNS

l lows:

N REQUIRED message to the CN. The message contains certain information such as relocation type, relocati

MN, and target CI,LAC.

NC or the target network system, such as the GSM system, to prepare relevant resources.

ge to the SRNC.

twork system prepares the relevant resources successfully, the CN sends a RELOCATION COMMAND messe L3 information IE, which carries the information about the relevant resources allocated by the target RNC or

fail to be allocated, the CN sends a RELOCATIONPREPARATION FAILURE message.



is performed to release resources in a NodeB for one or more established radio links towards a UE.

l lows:

DELETION REQUEST message to the NodeB. After receiving the message, the NodeB deletes the radio link

ssage to the CRNC.

he NodeB sends a RADIO LINK DELETION RESPONSE message.

, the NodeB sends a RADIO LINK DELETIONRESPONSE message. The Criticality Diagnostics field in the m

verage area of the GSM,the MSC sends the CN a MAP/E message "Send End Signal Request"

C and "Iu Release Command" message , requesting the former SRNC to release the allocated resource

ted in the UMTS, the former SRNC sends the CN an "Iu Release Complete" message

s the MSC a MAP/E message "Send End Signal Response"

med for the CN to release an Iu connection and all the UTRANresources related only to that Iu connection

l lows:

OMMAND message to the SRNC to initiate the Iu release procedure. The message indicates the cause for th

SE COMMAND message, the CN will not send further RANAP connection-oriented messages on this particul

TRAN resources and then sends an IU RELEASE COMPLETE message to the CN.

n procedure is performed to allocate resources from the targetRNS for an SRNS relocation.

rocedure can be triggered in either of the followingconditions:

CN applies for resources from the target RNC

r from GSM to WCDMA, the CN applies for resources from the target RNC

l lows:

EQUEST message to the target RNC. The message contains certain information, such as the IMSI of the UE,

rotection, Iu signaling connection ID, handover cause, andRAB parameters.

sources for the relocation.

e message to the CN.

target RNC sends a RELOCATION REQUEST ACKNOWLEDGE message. The message contains the radio

e parameters include the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and phys

tegrity protection algorithm.

fail to be allocated or the tar et RNC re ects the SRNS relocation for some reason the tar et RNC sends a R



dure is performed to configure or reconfigure one or both of the ciphering algorithm and the integrity protection

ering algorithm or the integrity protection algorithm has changed

l lows:

MMAND message sent to the UE, the SRNC starts or reconfigures one or both of the ciphering and integrity p

all Signaling Radio Bearers (SRBs).

ge to the SRNC.

r reconfiguring the relevant parameters for one orboth of the ciphering and integrity protection algorithms, the

SRNC of the completion.

ND message contains neither Ciphering mode info IE nor Integrity protection mode info IE or if each of the tw

RITY MODE FAILURE message, indicating the failure of the security mode control procedure as well as the fai

procedure is performed for the network to allocate a newUTRAN Radio Network Temporary Identifier (U-RNT

E or to inform the UE of mobility-related information such as timervalues and CN domain–related information

ILITY INFORMATION message to the UE.

d fields according to the values of the IEs carried in themessage.

ge to the SRNC.

ure is performed to request a UE to transmit its capability information related to any radio access network so t

capability

l lows:

ITY ENQUIRY message to the UE through the downlink DCCH using AM RLC.

INFORMATION message to the SRNC through the uplink DCCH using AM or UM RLC. The message contai

ty information and then sends a UE CAPABILITYINFORMA CONFIRM message to the UE through the downli

tra-RNC handover or GSM to WCDMA CS handover) isperformed to set up a radio link in an SRNC-controlle

l lows:

SETUP REQUEST message to the NodeB. Afterr eceiving the message, the NodeB reserves the necessary r

meters given in the message. ssage to the CRNC.

eB saves the value of the Configuration GenerationID IE contained in the RADIO LINK SETUP REQUEST me

e.

the NodeB sends a RADIO LINK SETUP FAILURE message. The message contains the failure cause.

ure (intra-RNC handover or GSM to WCDMA CS handover)is performed for a NodeB to notify the CRNC that t

or re-achieved

n with the UE, the NodeB sends a RADIO LINK RESTOREINDICATION message to the CRNC

ilure cause



the operations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILI

rations specified by the UTRAN MOBILITYINFORMATION message, the UE sends a UTRAN MOBILITY INF

se.





are

e GSM

tion from one or

igure is for

ndition of the

surement conditions are

rias are met, the UE reports

ransmission during which

on cause, source PLMN,

ge when the preparation isthe target network system.



specified by the message.

ssage indicates the failure

release of the signaling

r connection.

, CN domain indicator, target

resources and other

ical layer information,chosen

LOCATION



algorithm for a UE. The

rotection configurations for

E sends a SECURITYMODE

IEs has inconsistent

lure cause.

I) or Cell Radio Network

at the network can perform

s the information about UE

k DCCH using AM or

NodeB for a UE

esources and configures the

sage and sends a RADIO

he uplink synchronization of



Y INFORMATION

RMATIONFAILURE










RRC:Physical Channel Reconfiguration (DCCH)

RRC:Measurement Report (e2f)









RRC: Physical Channel Reconfiguration Complete (DCCH)





















RRC: Handover from UTRAN Command

Handover Completed





value=Inter-freq meas L3 filter coeff=3

value=Inter-freq meas bas ed on CPICH Ec/No

>>"Measurement Control and Measurement Report"

val ue=i n te rF requenc yMeasu remen t (RNC send mea ruement con tr o l o f In t er Fr e

parameter CoexistMeasTh dCho ice=" COEXIST_MEAS_THD_CHOICE_INTERFR



value=Event2D ( Start Compressed Mode)

value= InterFreqCSThd 2DEcN0=-14 dB

value= 0

value=2 dB ,Step: 0.5

value=320ms

value=Event2f ( Stop Com pressed Mode)

value= InterFreqCSThd 2FEcN0=-12 dB

value= 0

value=2 dB ,Step: 0.5

value=320ms



value=UE tr igger Event2D to star t Compressed Mode

value=UE tr igger Event2f to stop Comp ressed Mode



value=Compressed Mode Inforamt ion









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=interRATMeasurement (RNC send m earuement con trol of InterRAT af ter













value=UE measu re on GSM RSSI

value=InterRATFilterCoef=3

value=UE need to verify BSIC

value=InterRATPerio dRepo rtInterval= 1000ms

value=UE report 6 InterRATcel ls to RNC



value=RSSI= -110 + hex2dec(1E) = -80 dBm

value=BSIC=35 ( BCCH=112) refer to InterRAT CellID=7 in Measurem ent Contr o







uency because

Q" )















enter Compressed Mode)















(GSM900)




4.SRNS

13.Iu Re

8.SRNS Dat

1.RRC:Cell Change Order from UTRAN

4.SRNS

8.For

2.Routing Area Update Request

13. Iu R

UE BSS S-RNC

T( "RRC: Hand

UE Conn ected

UE Connected

UE Conn ected




UE BSC

22. BSS Packet Flow Context Procedure

S-RNC

19.Routing Area Update Accept

20.Routing Area Update Complete


1.When the PS data volume is low, the UE may be in CELL_PCH, URA_PCH, or Cell_FACH stat

information, the UE can initiate cell reselection to perform a handover to GSM. The cell reselectio

SGSN to SRNC.

When the UE in Idle ,URA_PCH.Cell_PCH or Cell_FACH states, the cell reselection procedure d

2.After cell reselection to a GSM cell, the NodeB sends a RADIO LINK FAILURE INDICATION m

cell.This message, however, is unnecessary to the procedure of inter-RAT PS handover from WC

3. After the UE accesses a GSM cell, the SGSN directly sends an IU RELEASE COMMAND mes

to be transferred.

4.The SRNS context transfer is unnecessary to the procedure of inter-RAT PS handover from W



1. Inter-RAT Handover

Decision

5.Security

2.Routing Area Update Request



20. RAB Assignement Request

20. RAB Assignement Response

19.Service Request

Setup Radio Resources

16.Routing Area Update Accept

17.Routing Area Update Complete



3.SGSN Context Request

5.SGSN Context Response

7.SGSN Context Acknowledge

9. Forward Packets

ontext Response

10. Update PDP Context Response

lease Command

12. Cancel Loc

6.Security Functions

C1

Forward Command

MSC-

2GGGSN

Context Request

L3 Messages - Inter-RAT Handover Procedure

ward Packets

10. Update PDP Context Request

Inter-RAT PS Handov er from WCDMA to GSM

lease Complete

12. Cancel Location A

11. Update GPRS Location

SGSN-

2G

SGSN-

3G

e procedure in this stage is simiilar to Inter-RAT CS Handover from WCDMA to GSMover from UTRAN Command " message is equivalent to "RRC:Cell Change Order from UTRA



Inter-RAT PS Handov er from GSM to WCDMA

SGSN-

2G GGSN

MSC-

3G

14. Insert Subscriber Data

14. Insert Subscriber Data Acknowledge

15. Update GPRS Location Acknowledge

SGSN-

3G

21. TMSI Reallocation Complete

16. Location Update Request

or when UE in Idle state. Based on the parameters in the system

n is initiated with an SRNS CONTEXT REQUEST message sent from the

es not include the sub-procedires which marked with "UE Connected)

ssage because the UE stops the transmission towards the WCDMA

DMA to GSM.

age to the SRNC, if the Packet Data Protocol (PDP) context does not need

DMA to GSM.

18 Location Update Accept

L3 Messages - Inter-RAT Handover Procedure



3.SGSN Context Request

4.SGSN Context Response

6.SGSN Context Acknowledge

7. Forward Packets

Functions

C2

10. Cancel Location A

11. Insert Subscriber Data

11. Insert Subscriber Data Acknowledge

12. Update GPRS Location Acknowledge

8. Update PDP Context Request

8 Update PDP Context Response

15 Location Update Accept

13. Location Update Request

9. Update GPRS Location

10. Cancel Loc

C1



C3

18. TMSI Reallocation Complete



ation

>>Inter-RA

MSC-

3GHLR

cknowledge

" )

SRNS Co nte

Iu release



MSC-

2GHLR

>>Inter-RA

17. Update Location



14a. Update Location

14b.Cancel Location

14c. Cancel Location Ack

14d. Insert Subscriber Data

14e. Insert Subscriber Data Ack

14f. Update Location Ack

cknowledge

ation





T HO Algorithm and related parameters

The Inter-RAT PS handover from WCDMA to GSM pro cedure is de

1.The UE in Cell_DCH state, the UTRAN decides to initiate an inter-RAT hand

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.

attach. The BSS adds the CGI including the RAC and LAC of the cell to the rec

3. The new 2G SGSN sends an "SGSN Context Request" message to the oldTMSI Signature is valid, the old 3G SGSN starts a timer. Otherwise, the old 3G

4. If the UE stay in connected mode before handover, the old 3G SGSN sends

PDUs to the UE, and send an "SRNS Context Response" message to the old 3

5. The old 3G SGSN sends an "SGSN Context Response" message to the 2G

6. The security functions can be excuted

7. The new 2G SGSN sends an 'SGSN Context Acknowledge" message to the

ready to receive PDUs belonging to the activated PDP contexts

8. The old 3G SGSN sends a "Data Forward Command" message to the SRN

the old 3G SGSN

9. The old 3G SGSN tunnels the GTP PDUs to the new 2G SGSN. In the PDU

10. the new 2G SGSN sends an "Update PDP Context Request" message to e

message after updating it's PDP Context fields

11. The new 2G SGSN sends an "Update GPRS Location" message ,requestin

12. The HLR sends a "Cancel Location" message to the old 3G SGSN. the old

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.

Release complete"

14. The HLR sends an "Insert Subscriber Data" message to the new 2G SGSN

returen an "Insert Subscriber Data Ack" message to the HLR

15.The HLR sends an "Update GPRS Location ACK" message to the new 2G

16. If the association has to be established, the new 2G SGSN sens a 'Locatio

number for creating or updating the association

17. If the subscriber data in VLR is marked as not confirmed by the HLR. the n

xt Transfer



T HO Algorithm and related parameters

- 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" me

- The old VLR acknowledge the message by responding with a "Cancel Locati

- The HLR sends an "Insert Subscriber Data" message to the new VLR

- The new VLR acknowledge the message by responding with an "Insert Subs

- 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 Update19. The new 2G SGSN checks the presence of the MS in the new RA. If all ch

established between the new 2G SGSN and the UE. The 2G SGSN responds

20. The UE acknowledge the new P-TMSI by returning a "Routing Area Update

21. The new 2G SGSN sends a "TMSI Reallocation Complete" message to the

22. The 2G SGSN and the BSS perform the "BSS Packet Flow Context" proce



The Inter-RAT PS handover from GSM to WCDMA pro cedure is de

1.The GSM decides to perform an inter-RAT handover in PS domanin and sto

2. The UE sends a "Routing Area Update Request" message to the 3G SGSN.

update with IMSI attach. The SRNC adds the the RAC and LAC of the cell to t

3. The new 3G SGSN obtain the address of the old 2G SGSN, and then sends

the UE. The old 2G SGSN validates the old P-TMSI signature. If the old P-TM

cause.

4. The old 2G SGSN response with an "SGSN Context Response" message to

5. The security functions can be excuted

6. The new 3G SGSN sends an 'SGSN Context Acknowledge" message to the

belonging to the activated PDP contexts

7. The old 2G SGSN copied and buffers N-PDUs, and then sends them to the

and sends them to the 3G SGSN. After the timer expires,the 2G SGSN does n

8.The new 3G SGSN sends an "Update PDP Context Request" message to 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 ti

Location Ack" message

11.The HLR sens an "Insert Subscriber Data" message to the 3G SGSN. The

12. The HLR sends "Update GPRS Location" by returning an "Update GPRS L

13. If the association has to be establilshed, that is . if the Update Type param

update, the 2G SGSN sends a "Location update request" message to the VLR

14. If the subscriber data in VLR is marked as not confirmed by the HLR. the n

- 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" me

- The old VLR acknowledge the message by responding with a "Cancel Locati

- The HLR sends an "Insert Subscriber Data" message to the new VLR

- The new VLR acknowledge the message by responding with an "Insert Subs

- The HLR responds with an "Update Location Ack" message to the new VLR

15. The new VLR allocates a new TMSI and responds with a "Location Update

16. The new 3G SGSN checks the presence of the MS in the new RA. If all ch

established between the new 3G SGSN and the UE. The 3G SGSN responds

17. The UE sends a "Routing Area Update Complete" message to confirm the

18. The new 3G SGSN sends a "TMSI Reallocation Complete" message to the

"



. ,

20. The 3G SGSN sends a "RAB Assignment Request" message to the SRNS.

Setup Complete" message. The SRNS sends a 'RAB assignment Response"



cribed as follows:

ver in the PS domain be sending "Cell Change Order from UTRAN' messge to UE to handover to a new

The update type in the message indicates RA update, combined RA/LA update, or combined RA/LA upd

eived message before forwarding the message to a new 2G SGSN

G SGSN to obtain the MM and PDP contexts. The old 3G SGSN validates the old P-TMSI signature. If thSGSN respons with an error cause.

an "SRNS Context Request" message. After receiving this message, the SRNS buffers the PDUs, stops

G SGSN

SGSN including the MM and PDP context

old 3G SGSN. This inform the old 3G SGSN that the new 2G SGSN is

. The SRNS starts a data-forwarding timer and sends the buffers PDUs to

, the sequence number in the GTP hearder remain unchange

ach related GGSN. Each GGSN sends an "Update PDP Context Response"

g the HLR to modify the SGSN number

3G SGSN responds with a "Cancel Location AcK" message. After the

After data-forwarding timer expires,the SRNS responds with an "Iu

. The 2G SGSN constructs an MM context and PDP context for the UE and

GSN

Update Request" message to the VLR. The VLR stores the SGSN

w VLR informs the HLP. The HLR cancel the old VLR and inserts



ssage to the old VLR

n ACK" message

criber Data ACK" message

Accept" message to the 2G SGSNcks area successful,the new 2G SGSN constructs the MM and PDP contexts for the MS. A logical link is

to the UE with a "Routing Area Update Accept" message

Complete" message, including all PDUs successfully sent to the UE before the routing area update proc

new VLR if the UE confirms the VLR TMSI

ure



cribed as follows:

s the data transmission between the UE and the network

The update type in the message indicates RA update, combined RA/LA update, or combined RA/LA

e received message before forwarding the message to a new 3G SGSN

an 'SGSN Context Request" message to the old 2G SGSN to construct the MM and PDP contects for

I Signature is valid, the old 2G SGSN starts a timer. Otherwise, the old 2G SGSN respons with an error

the 3G SGSN including the MM and PDP context

old 2G SGSN. This inform the old 2G SGSN that the new 3G SGSN is ready to receive PDUs

G SGSN. Before the timer expires ,if there are other N-PDUs from the GGSN,the 2G SGSN compies

ot send N-PDUs to the 3G SGSN anymore

ch related GGSN. Each GGSN sends an "Update PDP Context Response" message after updating it's

er expires,the 2G SGSN removes the MM and PDP contexts. The 2G SGSN response with a 'Cancel

G SGSN constructs an MM context and sends an "Insert Subscriber Data Ack" message to the HLR

ocation Ack" message to the 3G SGSN

ter indicates a combined RA/LA update with IMSI attach requested, or if the LA changed with the RA

. The VLR stores the SGSN number for creating or updating the association

w VLR informs the HLP. The HLR cancel the old VLR and inserts subscriber data in the new VLR

ssage to the old VLR

n ACK" message

criber Data ACK" message

Accept" message to the 3G SGSN

cks area successful,the new 3G SGSN constructs the MM and PDP contexts for the MS. A logical link is

to the UE with a "Routing Area Update Accept" message

allocated P-TMSI

new VLR if the UE confirms the VLR TMSI

"



.

. The SRNS sens a 'Radion Beare Setup Request" message to the UE. The UE responds with a 'Radio B

essage to the SGSN. The SRNS sends N-PCDS to the UE



SM cell

te with IMSI

e old P-

ending the



dure





arer




2.Suspend

3.Suspend

3. Suspend Ack

4. Resume

4. Resume NAck

5.Channel Release


2.Suspend

3.Suspend

1. Inter-RAT H

6. Routing Area Update Request

Inter-RAT CS&PS Hando ver from

L3 Messages - Inter-RAT

1. Inter-RAT H

2G

SGSN

UE BSS 2G/3G

SGSN

L3 Messages - Inter-RAT

UE BSS

Inter-RAT CS&PS Hando ver from



3. Suspend Ack

4. Resume

4. Resume NAck

5.Channel Release

6. Routing Area Update Request







3. SRNS Context Request

3. SRNS Context Response

>>Inter-RAT HO Algorithm a

>>Inter-RAT HO Algorithm a

ndover

For a UE in

from the U

message to

on the GS

if the inter-

inititates a

connection

The signalli

1. The UE i

2. The UE

3. The BSS

downlink Preturns a "

4. When th

changed. T

5. The BSS

6. The UE

use.

CDMA to GSM (Int ra-SGSN)

MSC

/VL

andover Procedure

ndover

MSC

/VLSRNS

SRNS

andover Procedure

For a UE in

from the U

message to

on the GS

if the inter-

inititates a

connection

The signalli

1. The UE i

2. The UE

CDMA to GSM (Int er-SGSN)

3G SGSN



3. The BSS

4. When th

changed. T

5. The BSS

6. The UE

use.







d related parameters

d related parameters

Cell_DCH state using both CS and PS domain services,the inter-RAT handover procedure is based on the m

RAN. The UE performs the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode

the GSM/BSS, the UE initiates a temporary block flow (TBF) towards the GPRS to suspend the GPRS servic

side, the inter-RAT handover in the PS domain resumes, which indicates that the handover is completed.

AT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the handover is regards

BF towards the GPRS or not. In case of inter-RAT handover failure, the UE may go back to the UTRA RRC C

in the original state.

ng procedures are described as follows,

n connection with both CS and PS domain perrforms the UMTS to GSM handover during which the CS service

ends a suspend message to the BSS

forwards the 'Suspend" message to the SGSN. The SGSN sends a "SRNS Context Request" message to the

Us. After receiving the message, the SRNS buffers downlink PDUs and respons to the SGSN with an 'SRNSuspend Ack" message to the BSS

CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. However,resume is im

herefore,the SGSN acknowledge the resume through a 'Resume NACK"

sens an RR message 'Channel Release" to the UE, indicating that the BSS fails to request the SGSN to resu

ends a 'Routing Area Update Request" message to the SGSN to resume the GPRS service. The update mod

Cell_DCH state using both CS and PS domain services,the inter-RAT handover procedure is based on the m

RAN. The UE performs the inter-RAT handover from UTRA RRC Connected Mode to GSM Connected Mode

the GSM/BSS, the UE initiates a temporary block flow (TBF) towards the GPRS to suspend the GPRS servic

side, the inter-RAT handover in the PS domain resumes, which indicates that the handover is completed.

AT handover from UTRA RCC Conencted Mode to GSM Connected Mode succeeds,the handover is regards

BF towards the GPRS or not. In case of inter-RAT handover failure, the UE may go back to the UTRA RRC C

in the original state.

ng procedures are described as follows,

n connection with both CS and PS domain perrforms the UMTS to GSM handover during which the CS service

ends a sus end messa e to the BSS



forwards the 'Suspend" message to the SGSN. The SGSN returns a "Suspend Ack" message to the BSS

CS connection is terminated , the BSS may send a 'Resume" message to the SGSN. However,resume is im

herefore,the SGSN acknowledge the resume through a 'Resume NACK"

sens an RR message 'Channel Release" to the UE, indicating that the BSS fails to request the SGSN to resu

ends a 'Routing Area Update Request" message to the SGSN to resume the GPRS service. The update mod







asurement reports from the UE but is initiated

first. After the UE sends a handover complete

s. After the CS domain services are released

as successful.no matter whether the UE

onnected Mode and re-establish the

is handed over to the GSM

SRNS, requesting the SRNS to stop sending

Context Response" messge. The SGSN

ossible since the radio access system has

e the GPRS service for the UE

depends on the network operation mode in

asurement reports from the UE but is initiated

first. After the UE sends a handover complete

s. After the CS domain services are released

as successful.no matter whether the UE

onnected Mode and re-establish the

is handed over to the GSM



ossible since the radio access system has

e the GPRS service for the UE

depends on the network operation mode in




5. RNSAP: Relocation Commit

UE SRNC DR

SRNS Static Relocation (UE not- involv ed

1.RANAP: Relo

L3 Messages - Intra-Frequency Hard Han

14. RANAP: Iu

4.RANAP: Relo

7. RRC:UTRAN Mobility Information

10. RRC:UE Capability Information (DCCH)

9. RRC:UE Capability Enquiry (DCCH)

11. RRC:UE Capability Information Confirm (DCCH)

8. RRC:UTRAN Mobility Information Confirm

13. RANAP: Iu R




2. RNSAP: Signalling Transfer

Indication


SRNC DR

SRNS Relo catio n w ith Cell /URA Up date (UE n ot-i

1. Cell Update/URA Update

UE



7. RNSAP: Relocation Commit

Note the fo l lowing in format ion about the p rocedure :

1.The DRNC acquires the SRNC ID of the UE from the URNTI IE in the CELL UPDATE

SIGNALLING TRANSFER INDICATION messageto the SRNC to indicate that the UE re

2.To initiate a cell update, the UE sends a CELL UPDATE message to the DRNC. To initi

UPDATE message to the DRNC.

3.After a successful cell update, the DRNC sends a CELL UPDATE CONFIRM message

the DRNC sends a URA UPDATE CONFIRM message to the UE.

4.After receiving the CELL UPDATE CONFIRM or URA UPDATE CONFIRM messagefro

PHYSICAL CHANNEL RECONFIGURATION COMPLETE message (for the cell update)

CONFIRM message (for the URA update) to the DRNC. This response from the UE is op


15. RANAP: Iu R

16. RANAP: Iu



9. RRC:Cell Update Confirm/URA Update Confirm

10. RRC:Physical Channel Reconfiguration Complete/UTRAN Mobility

Information Confirm

6.RANAP: Relo

3RANAP: Relo

Cell

Update/U

RA

Update








1.RANAP: Relo


5.RANAP: Forwa


13. RANAP: Iu R

14. RANAP: Iu

4.RANAP: Relo

9. RRC:Physical Channel Reconfiguration Complete

SRNS Relo catio n w ith Hard Han do ver(UE in v

UE SRNC DR

7.RRC:Physical ChannelReconfigurationPhysicalC

hannelReconfig



Note the fo l lowing in format ion about th e procedure :

1.During the relocation with hard handover, if an RAB supporting lossless SRNS r

SRNC sends the GTP-U and PDCP sequence numbers to the DRNC through the

sequence numbers are required for data forwarding.

2.After receiving a RADIO LINK RESTORE INDICATION message from the Node

message to the CN.

3.If the DRNC does not obtain the information about the UE capability, the DRNC i



2.RANAP Relocation Request

3.RANAP Relocation Request Ack

6. RANAP:Relocation Detect

12. Relocation Complete

>>SRNC Relocation Algorithm and related

The

->D

->D

Th

1.T

ca

2.T

3.T

RE

rele

to b

C CN

relocat ion)

cation Required

over Procedure

elease Complete

ation Command

The

Net

Th

1.T

2.T

The

Th

1.T

RE

2.T

3.T

The

->D->D

Th

1.T

indi

2.T

3.T

me

Ide

part

so

elease Command


Relocation Resourc e Al location

Relocat ion Comm it

Iu release

UE capabi l i ty enqu iry

UTRAN mobi l i ty in format ion




The

can

Th

1.T

2.T

info

3.T

AM

over Procedure

C CN

The

->T

->T

->T

->T

Th

1.T

sign

part

2.T

The->D

->D

Th

1.T

PL

2.T

3.T

RE

rele

volved relocat ion)

.

->If

INF

->If

INF



4.RANAP Relocation Request

5.RANAP Relocation Request Ack



The

upd

Th

1.T

U-R

2.T

ciph

essage and then sends an UPLINK

uests a cell update.

iate a URA update, the UE sends a URA

tothe UE. After a successful URA update,

m the DRNC, the UE can send a

or a UTRAN MOBILITY INFORMATION

tional.

elease Command

elease Complete

The

pro

The

failu

Th

1.T

RN

2.Tcha

3.A

me

->U

->P

->T

->R

->R

ation Command

The

->D

->D

Th

1.T

indi

2.T

3.T

me

incl

, an

so

RE cation Required



Relocat ion Comm it

Iu release




The

->T

->T

->T

->T

The

can

Th

1.T

2.T

info

3.T

AM

The

Net

Th

1.T

2.T

3.T

->If

INF

->If

INF

.

par

The

Th

1.T

RE

2.T

3.T




2.RANAP: Relocation Request

3.RANAP: Relocation Request Ack

6.RANAP: Forward SRNS Context



over ProcedureThe

->D

->D

Th

1.T

PL

2.T

3.T

RE

rele

RE

cation Required

rd SRNS Context

The

Th

1.

me

for

2.A

3.T

The

->D

->D

Th

1.T

CN

2.T

3.T

RE

incl

and

so

elease Command

elease Complete

1.T

sign

part

2.T

ation Command

lved relocat ion)

C CN



Relocat ion Comm it

Iu release




The

->T

->T

->T

->T

Th

1.T

sign

part

2.T

location is available on the Iu-PS interface, the

FORWARD SRNS CONTEXT message. The

B, theDRNC sends a RELOCATION DETECT

initiatesa UE capability enquiry procedure.

4.T

The

Th

1.T

2.T

3.T

->If

CH

->If

old

the

The

can

Th

1.T

2.T

info

3.T

AM



arameters

relocation preparation procedure can be triggered in either of the following conditions:

uring an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.

uring an inter-RAT CS handover from WCDMA to GSM, the SRNC sends aRELOCATION REQUIRED messa

procedure is descr ibed as fo l lows:

e SRNC sends a RELOCATION REQUIRED message to the CN. The message containscertain information s

se, source PLMN, source LAC,source SAC, target PLMN, and target LAC

e CN interacts with the target RNC or the target network system, such as the GSMsystem, to prepare relevan

e CN sends a response message to the SRNC.lIf the target RNC or the target network system prepares the r

OCATION COMMAND message when thepreparation is complete. The message contains the L3 information

vant resources allocated by the target RNC or the targetnetwork system.lIf the resources partially or totally fail

e allocated, the CN sends a RELOCATIONPREPARATION FAILURE message.

UTRAN m obi l i ty in format ion procedure is performed for the network to allocate a newUTRAN Radio Netwo

ork TemporaryIdentifier (C-RNTI) to a UE or to inform the UE of mobility-related information such as timer va


e SRNC sends a UTRAN MOBILITY INFORMATION message to the UE

e UE starts to update the related fields according to the values of the IEs carried in themessage.

re locat ion commit procedure is performed to execute the change of control from the SRNCof a UE to the


e SRNC sends a RELOCATION COMMIT message to the DRNC. If an RAB supportinglossless SRNS reloca

OCATION COMMITmessage carries the GTP-U and PDCP sequence numbers required for data forwarding.

e DRNC sends a RELOCATION DETECT message to the CN to notify the CN of thedetection of the relocatio

e original DRNC sends a RELOCATION COMPLETE message to the CN to notify thatthe relocation is succe

relocation resource al location procedure can be triggered in either of the following conditions:

uring an SRNS relocation, the CN applies for resources from the target RNCuring an inter-RAT CS handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC


e CN sends a RELOCATION REQUEST message to the target RNC. The messagecontains certain informati

cator, target cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RA

e target RNC allocates radio resources for the relocation.

e target RNC sends a response message to the CN.lIf the resources are allocated, the target RNC sends a R

sage. The message contains the radio resources and otherparameters allocated to the UE. The parameters i

tifier (U-RNTI), RAB, transport layer and physical layer information,chosen encryption algorithm, and chosen i

ially or totally fail to be allocated or the target RNC rejects the SRNSrelocation for

e reason, the target RNC sends a RELOCATION FAILURE message,indicating the failure cause.



UE capabi l i ty enqu iry procedure is performed to request a UE to transmit its capabilityinformation related to

perform dataconfiguration based on the UE capability.


e SRNC sends a UE CAPABILITY ENQUIRY message to the UE through the downlink DCCH using AM RLC

e UE sends a UE CAPABILITY INFORMATION message to the SRNC through theuplink DCCH using AM or

rmation about UE capabilities.

e SRNC reads the UE capability information and then sends a UE CAPABILITYINFORMA CONFIRM messa

or UMRLC.

Iu release procedure can be triggered in one of the following conditions:

he transaction between the UE and the CN is complete.

he UTRAN requests the CN to release the resources on the Iu interface by, for example,sending an IU RELEA

he Serving Radio Network Subsystem (SRNS) is relocated.

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


e CN sends an IU RELEASE COMMAND message to the SRNC to initiate the Iu releaseprocedure. The mes

aling connection.NOTE After sending the IU RELEASE COMMAND message, the CN will not send further RA

icular connection.

e SRNC releases the related UTRAN resources and then sends an IU RELEASE COMPLETE message to th

relocation preparation procedure can be triggered in either of the following conditions:uring an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.




N, source LAC,source SAC, target PLMN, and target LAC




vant resources allocated b the tar et RNC or the tar etnetwork s stem.lIf the resources artiall or totall fail

.

the UE succeeds in conducting the operations specified by the UTRAN MOBILITYI NFORMATION message,

ORMATIONCONFIRM message.

the UE fails to conduct the operations specified by the UTRAN MOBILITYINFORMATION message, the UE s

ORMATIONFAILURE message, indicating the failure cause.



URA update procedure is performed to update the URA-related location information on thenetwork side whe

ate procedure can be triggered in either of the following conditions:URA reselection or Periodical URA update


e UE sends a URA UPDATE message to the RNC to initiate the URA update. The message contains the cau

NTI.

e RNC sends a URA UPDATE CONFIRM message to the UE. The message containsthe new C-RNTI and U-

ering and integrityprotection modes.

cel l update procedure is performed to update the UE-related information on the UTRANside when the locati

edure takes the role ofmonitoring the RRC connection, switching the status of the RRC connection, reporting

cell update procedure can be triggered in one of the following conditions:Cell reselection,Re-entering the serv

re,Paging response,Uplink data transmission and RLC unrecoverable error

procedure is descr ibed as fo l lows :

e UE sends a CELL UPDATE message to the RNC. The message contains the information such as the Servi

I) andthe SRNC ID.

e RNC sends a CELL UPDATE CONFIRM message to the UE. The message containsthe information such annels, physicalchannels, and radio bearers.

cording to related IEs in the received message, the UE may respond with messages ornot. If the UE respond

sages:

TRAN MOBILITY INFORMATION CONFIRM

HYSICAL CHANNEL RECONFIGURATION COMPLETE

RANSPORT CHANNEL RECONFIGURATION COMPLETE

ADIO BEARER RECONFIGURATION COMPLETE

ADIO BEARER RELEASE COMPLETE


uring an SRNS relocation, the CN applies for resources from the target RNC

uring an inter-RAT CS handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC



cator, target cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cause, and RA



sage. The message contains the radio resources and otherparameters allocated to the UE. The parameters

lude the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer informa

d chosen integrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC


.

OCATIONPREPARATION FAILURE message.















or UMRLC.

UTRAN m obi l i ty in format ion procedure is performed for the network to allocate a newUTRAN Radio Netwo

ork TemporaryIdentifier (C-RNTI) to a UE or to inform the UE of mobility-related information such as timer va


e SRNC sends a UTRAN MOBILITY INFORMATION message to the UE

e UE starts to update the related fields according to the values of the IEs carried in themessage.

e UE sends a response message to the SRNC.

the UE succeeds in conducting the operations specified by the UTRAN MOBILITYI NFORMATION message,

ORMATIONCONFIRM message.

the UE fails to conduct the operations specified by the UTRAN MOBILITYINFORMATION message, the UE s

ORMATIONFAILURE message, indicating the failure cause.

. ,

meters intoeffect.

re locat ion commit procedure is performed to execute the change of control from the SRNCof a UE to the


e SRNC sends a RELOCATION COMMIT message to the DRNC. If an RAB supportinglossless SRNS reloca

OCATION COMMITmessage carries the GTP-U and PDCP sequence numbers required for data forwarding.

e DRNC sends a RELOCATION DETECT message to the CN to notify the CN of thedetection of the relocatio




relocation preparation procedure can be triggered in either of the following conditions:

uring an SRNS relocation, the SRNC sends a RELOCATION REQUIRED message.




N, source LAC,source SAC, target PLMN, and target LAC




vant resources allocated by the target RNC or the targetnetwork system.lIf the resources partially or totally fail

OCATIONPREPARATION FAILURE message.

r elocat ion comm it procedure is performed to execute the change of control from the SRNCof a UE to the D


hen an RAB supporting lossless SRNS relocation is available on the Iu-PS interface, theSRNC sends a FOR

sage to the SGSN to ask the SGSN totransfer the GTP-U and PDCP sequence numbers to the DRNC. The s

arding.

ter receiving the FORWARD SRNS CONTEXT message, the SGSN forwards themessage to the DRNC.

e UE is handed over from the SRNC to the DRNC through a physical channelreconfiguration procedure. After


uring an SRNS relocation, the CN applies for resources from the target RNC

uring an inter-RAT CS handover from GSM to WCDMA, the CN applies for resourcesfrom the target RNC



domain indicator, target cellidentifier, encryption, integrity protection, Iu signaling connection ID, handover cau



UESTACKNOWLEDGE message. The message contains the radio resources and otherparameters allocate

lude the UTRAN Radio NetworkTemporary Identifier (U-RNTI), RAB, transport layer and physical layer informa

chosen integrity protection algorithm.lIf the resources partially or totally fail to be allocated or the target RNC r




icular connection.












icular connection.


,


physica l ch annel reconf iguration procedure is performed to set up, reconfigure, or releasea physical chan


e SRNC sends a PHYSICAL CHANNEL RECONFIGURATION message to the UE to request reconfiguration

e UE saves the IEs of the UE, Radio Bearer (RB), transport channel, and physical channel.

e UE sends a response message to the SRNC.

successfully reconfiguring the physical channels specified by the PHYSICALCHANNEL RECONFIGURATION

NNELRE CONFIGURATION COMPLETE message on the uplink DCCH by using AM RLC.

failing to reconfigure the physical channels specified by the PHYSICAL CHANNELRECONFIGURATION mes

physicalchannel configuration and sends a PHYSICAL CHANNEL RECONFIGURATION FAILURE message

Failure causeIE contained in the PHYSICAL CHANNEL RECONFIGURATION FAILURE message is "physical








or UMRLC.



ge.

uch as relocation type, relocation

t resources.

levant resourcessuccessfully, the CN sends a

IE, which carries theinformation about the

rk Temporary Identifier (U-RNTI) or Cell Radio

lues and CN domain–related information.

RNC

tion is available on the Iu-PS interface, the

hen, the SRNC initiates data forwarding.

n commitment.

sful.

on, such as the IMSI of the UE, CN domain

parameters.

ELOCATION REQUESTACKNOWLEDGE

clude the UTRAN Radio NetworkTemporary

ntegrity protection algorithm.lIf the resources



any radio access network so that the network

he UE sends a UTRAN MOBILITY

nds a UTRAN MOBILITY

Date post:	07-Aug-2018
Category:	Documents
Upload:	nueng-phumpanyarut-nattawat
View:	215 times
Download:	0 times

45568132 W RNO Analysis Mate V1 0

Documents