11 WO_NA03_E1_0 UMTS Access Control-34

UMTS Access Control

iiii

Contents

1 System Broadcast ....................................................................................................................................... 1

1.1 System Information Broadcasting, Scheduling, and Transmission ................................................... 1

1.2 Information Sent by SIBs .................................................................................................................. 3

1.2.1 SIB1 ....................................................................................................................................... 3

1.2.2 SIB2 ....................................................................................................................................... 7

1.2.3 SIB3/SIB4 .............................................................................................................................. 8

1.2.4 SIB5/SIB6 .............................................................................................................................. 9

1.2.5 SIB7 ..................................................................................................................................... 10

1.2.6 SIB11/SIB12 ........................................................................................................................ 11

1.2.7 SIB15 ................................................................................................................................... 11

1.2.8 SIB18 ................................................................................................................................... 11

1.2.9 SIB11bis ............................................................................................................................... 12

2 RRC Connection Setup and Release ...................................................................................................... 13

2.1 RRC Connection Setup ................................................................................................................... 13

2.1.1 Establishing an RRC Connection over a Dedicated Transport channel ............................... 14

2.1.2 Establishing an RRC Connection over a Common Transport channel ................................. 14

2.2 Handling Abnormality in the RRC Connection Setup .................................................................... 15

2.2.1 Wireless Link Setup Failure ................................................................................................. 15

2.2.2 Failure to Receive RRC Connection Setup Response From UE .......................................... 16

2.3 Releasing the RRC Connection ....................................................................................................... 16

2.3.1 Releasing the RRC Connection Established over the Dedicated Channel ........................... 17

2.3.2 Releasing the RRC Connection Established over the Common Channel ............................ 18

iiiiiiii

2.3.3 Handling Abnormality in the RRC Connection Release ....................................................... 18

3 NAS Message Transfer ............................................................................................................................. 19

3.1 NAS Message Forwarding Flow...................................................................................................... 19

3.2 Setting up and Releasing the Iu Interface Connection ..................................................................... 20

3.2.1 Setting up the Iu Interface Connection ................................................................................. 20

3.2.2 Releasing the Iu Interface Connection .................................................................................. 21

4 Paging ........................................................................................................................................................ 27

4.1 Paging Flow ..................................................................................................................................... 27

4.2 PAGING TYPE 1 ............................................................................................................................. 28

4.3 PAGING TYPE 2 ............................................................................................................................. 30

1111

1 System Broadcast

The RNC is responsible for creating and broadcasting system information. The system

information include the Non-Access Stratum (NAS) message, cell common channel

configuration message, cell selection and reselection parameter, initial access message,

measurement control message, and locating message. The system information can

provide the UTRAN information necessary to Location Area Update (LAU), Route

Area Update (RAU), and RRC setup initiated by the cell.

The system information can be divided into three categories: master information block

(MIB), schedule block (SB), and system information block (SIB).

1.1 System Information Broadcasting, Scheduling, and Transmission

The MIB can store the scheduling information of the SB and SIB; the SB stores the

scheduling information of the SIB, including SB1 and SB2; the SIB stores the system

information. The ZTE UTRAN supports SB1, SB2, SIB3, SIB5, SIB6, SIB7, SIB11,

SIB11bis, SIB18.

After a cell is created or added, the system broadcasts messages within the cell. When

the system message is updated or the timer is time out, the system also broadcasts

system messages. See the following figure.

UMTS Access Control

2222

Figure 1 System broadcasting

� When a cell is created or the system information is updated, the system first

schedules the system information broadcasting and specifies the interval at

which the information blocks are to be sent. According to the significance of

the SIB, the system assigns two priorities to the SIB: The SIB with the highest

priority is scheduled by the MIB; the SIB with the second highest priority is

scheduled by SB1.The assignment of priority can improve the frequency at

which the system information is broadcasted. The SIBs with few contents can

be cascaded together and transmitted within the same TTI. The SIBs with

many contents can be divided into several segments, such as SIB5 and

SIB11.This following describes the division of the SIB specifically:

− The MIB schedules SB1, SIB1, SIB2, SIB3, SIB5, and SIB7.

− SB1 schedules SIB11, SIB18.

� Except MIB, the significance of all system information blocks is divided into

two levels. The significance level represents the priority of filling in system

information.

Table 1 Scheduling levels of the SIBS

Level 1 Information blocks scheduled by the MIB: SB1, SIB1, SIB2, SIB3, and SIB7

Chapter Error! Use the Home tab to apply 标题标题标题标题 1 to the text that you want to appear here. Error! Use th

e Home tab to apply 标题标题标题标题 1 to the text that you want to appear here.

3333

Level 2 Information blocks scheduled by SB1: SIB11, SIB18

Broadcast interval of the SIBs of various levels: broadcast interval of level 2 >=

broadcast interval of level 1

� After filling in the system information according to the scheduling principles,

the RNC sends the SYSTEM INFORMATION UPDATE REQUEST message

to the Node B. When the RNC receives the correct SYSTEM INFORMATION

UPDATE RESPONSE message, it considers system information updating

successful.

� After receiving the system information, the Node B broadcasts the system

information over the BCH channel to each information block at the specified

interval.

� When the system information is updated, the system notifies the UE in the

Idle, PCH, or FACH state through the following means:

− Notify the UE in the Idle or PCH state through paging: The RNC sends a

paging message of PAGING TYPE 1 to the UE. The cell BCCH modification

info in the message indicates that the system information has been updated.

− Notify the UE in the FACH state through the system information updating: The

system sends the SYSTEM INFORMATION CHANGE INDICATION to the

UE. The BCCH modification info in the message indicates that the system

information has been updated.

1.2 Information Sent by SIBs

1.2.1 SIB1

SIB1 mainly contains the CN information, UE behavior related timers and counters.

The following describes the cells configured in the OMCR:

T300 specifies the waiting time after the UE sends the RRC CONNECTION SETUP

REQUEST message. The timer is started after the UE sends the RRC CONNECTION

REQUEST message. If the cause of the RRC connection request is MBMS Reception,

the T300 timer is not started. Instead, the T318 timer is started, and the value of the

timer T318 is invariably configured to 1000ms. The T300 timer is stopped when the

message RRC CONNECTION SETUP is received; when the timer expires and the

retransmit event count is smaller than N300, the UE retransmits the RRC

CONNECTION SETUP REQUEST message.

UMTS Access Control

4444

N300 specifies the maximum retransmit event count of the RRC CONNECTION

SETUP REQUEST message. If the T300 timer expires and the retransmit event count is

equal to or larger than N300 but the RRC CONNECTION SETUP message has not

been received, the UE enters the Idle mode.

T312Idle specifies the time during which the UE in Idle mode has to wait for the

synchronization indication from layer 1 when it establishes the dedicated physical

channel. The timer is started when the UE starts to establish the dedicated channel.

When the UE finds the number of synchronization indications received from layer 1 is

equal to N312Idle, the T312 timer is stopped. If the timer expires, the physical channel

setup fails.

N312Idle is an Idle mode counter. It indicates the number of synchronization

indications received from layer 1 when the UE sets up the dedicated channel.

T302 specifies the waiting time after the UE sends the CELL UPDATE or URA

UPDATE message. The counter is started when the UE sends the CELL UPDATE or

URA UPDATE message; the counter is stopped when the UE receives the CELL

UPDATE CONFIRM or URA UPDATE CONFIRM message. If the counter T302

expires but the number of retransmitted messages is smaller than N302, the UE

retransmits the CELL UPDATE or URA UPDATE message.

N302 specifies the maximum retransmit event count of the CELL UPDATE or URA

UPDATE message. When the T302 counter expires and the number of the CELL

UPDATE or URA UPDATE messages sent by the UE is larger than or equal to N302,

the UE enters the Idle mode.

T304 specifies the waiting time after the UE sends the UE CAPABILITY

INFORMATION message. When the UE sends the UE CAPABILITY

INFORMATION message, the timer is started; when the UE receives the UE

CAPABILITY INFORMATION Confirmed message, the timer is stopped. When the

T304 timer expires and the number of the CAPABILITY INFORMATION messages

sent by the UE is smaller than N304, the UE retransmits the UE CAPABILITY

INFORMATION message.

N304 specifies the maximum retransmit event count of the UE CAPABILITY

INFORMATION message. When the T304 counter expires and the retransmit event

count is equal to or larger than N304, the UE starts the CELL UPDATE process.



5555

T305 specifies the interval at which the cell or URA is updated when the UE is in the

CELL_FACH, or CELL_PCH/URA_PCH state. The T305 timer is started when the UE

enters the CELL_FACH, or CELL_PCH/URA_PCH state. When the UE receives the

CELL UPDATE CONFIRM or URA UPDATE CONFIRM message, the T305 timer is

stopped. When the T305 timer expires and the UE detects its own serving cell, the UE

sends the CELL UPDATE message; when the T305 timer expires and the UE is not in

the serving cell, it starts the T307 timer.

T307 specifies the time during which the UE waits for cell reselection after leaving the

serving cell. After the timer expires, the UE returns to the Idle mode.

T308 specifies the waiting time after the UE in the CELL_DCH state sends the RRC

CONNECTION RELEASE COMPLETE message. The T308 timer is started after the

UE sends the RRC CONNECTION RELEASE COMPLETE message. When the T308

timer expires and the number of the RRC CONNECTION RELEASE COMPLETE

messages sent by the UE is smaller than N308, the UE retransmits the RRC

CONNECTION RELEASE COMPLETE message.

N308 specifies the maximum retransmit event count of the RRC CONNECTION

RELEASE COMPLETE message. When the T308 counter expires and the number of

the RRC CONNECTION RELEASE COMPLETE messages sent by the UE is larger

than or equal to N308, the UE enters the Idle mode.

T309 specifies the waiting time after the UE initiates the request of accessing other

system (such as GSM). When the UE receives the CELL CHANGE ORDER FROM

UTRAN message, the T309 timer is started; when the UE in the new cell successfully

receives the response to the connection setup request, the T309 timer is stopped. If the

T309 timer expires, the UE returns to the original UTRAN.

T312 Connected is a timer when the UE is in connected mode. The timer specifies the

time during which the UE in connected mode has to wait for the synchronization

indication from layer 1 after it initiates the setup of a dedicated physical channel. The

timer is started when the UE starts to establish the dedicated channel. When the UE

finds the number of synchronization indications received from layer 1 is equal to N312,

T312 is stopped. If the T312 timer expires, the physical channel setup fails.

N312Connected is the N312 counter in Connected mode. It indicates the number of

synchronization indications received from layer 1 before the UE in connected mode

UMTS Access Control

6666

sets up the dedicated channel successfully.

T313 specifies the waiting time after the DPCCH channel set up by the UE in the DCH

state loses synchronization. When the number of synchronization loss indications

received by the UE in the DCH state from layer 1 reaches the value of N313, the UE

starts T313. When the UE receives synchronization indications from layer 1 for N315

times, it stops the T313 timer. When the T313 timer expires, the radio links involved in

the lost synchronization fail.

N313 specifies the maximum number of synchronization loss indications received by

the UE from layer 1.

N315 specifies the maximum number of synchronization loss indications received by

the UE from layer 1 when T313 is in active status.

T314 is a UE timer. When the criteria for radio link failure are fulfilled, T314 is started

if radio bearer(s) that are associated with T314 exist or if only RRC connection exists

only to the CS domain. When the Cell Update procedure has been completed, T314 is

stopped.

T315 specifies the time during which the radio bearers related to T315 wait for the

completion of cell updating after the radio connection setup fails. When the RB is set

up, the system uses T314 or T315 for the RB. When the radio link fails and the current

RB uses T315, the system starts T315. When the cell updating process finishes, the

system stops T315.

When T314 expires, the UE judges whether T302 is still in running status. If yes, the

UE waits for the CELL UPDATE CONFIRM or URA UPDATE CONFIRM message

continuously. If T302 is not running, the UE judges whether T315 is in running status.

If yes, the UE releases RAB resources related to T314. If T315 is not running, the UE

releases all the RAB resources and enters the Idle mode.

If T315 expires, the UE behaves as if T314 expires. At the moment, the UE takes

actions according to the running status of T302 and T314.

T306 specifies the time during which the UE in the CELL_PCH/URA_PCH state waits

for cell selection or reselection after leaving the serving cell. When the UE in the PCH

state leaves the serving cell, the system starts the T316 timer; when the UE detects the

serving cell, the system stops the T316 timer. When the T316 timer expires, if the UE is

in the serving cell, it initiates the cell updating; if the T316 timer is not in the serving



7777

cell, it starts the T317 timer and switches to the FACH state. When the UE detects the

serving cell, it starts the cell updating.

T307 specifies the time during which the UE in the CELL_FACH state waits for cell

selection or reselection after leaving the serving cell. When the T316 timer expires, the

system starts the T317 timer; when the UE in the FACH leaves the serving cell, the

system starts the T317 timer. When the UE detects the serving cell, it stops the T317

timer.

MCC: mobile country code.

MNC: mobile network code

CnDomain refers to the CN domain supported by the system.

T3212Cs is a periodic location updating timer. Location updating involves two

occasions: The UE detects LAC variation and initiates location updating; the system

updates locations periodically. T3212Cs is a periodic location updating timer.

ATTIndCs is a digital variable and specifies whether the IMSI ATTACH flow or the

DETACH flow should be adopted.

NMOPs specifies a network operation mode. Network mode 1 indicates that Gs

interfaces exist between the MSCServer and the SGSN; network mode 2 indicates that

the Gs interfaces do not exist.

Kcs is the discontinuous reception cycle length coefficient of the CS domain. The

parameter allows a UE in the Idle or PCH state to calculate the paging occasion so that

it can monitor the PICH channel at the time specified by the parameter.

Kps specifies the discontinuous reception cycle length coefficient of the CS domain.

The parameter allows a UE in the Idle or PCH state to calculate the paging occasion so

that it can monitor the PICH channel at the time specified by the parameter.

MbmsModPrdCoeff specifies the Modification Period Coefficient for MBMS.

The above parameters can be configured in the OMCR.

1.2.2 SIB2

SIB2 specifies the URA ID of a cell. With SIB2, the UE in the URA_PCH state can

update the URA. The table below lists the parameters configured in the OMCR.

UMTS Access Control

8888

Table 2 SIB2 parameters that can be configured in the OMCR

Parameter Name Parameter Description

URANum Number of UTRAN registration areas

URA[4] ID of a UTRAN registration area

1.2.3 SIB3/SIB4

Parameters in SIB3 and SIB4 are related to the cell selection and cell reselection. SIB3

contains information required by the UE in Idle mode; SIB4 contains information

required by the UE in Connected mode (the FACH and DCH states are under the

control of the measurement policies). If SIB4 is not sent, the UE in Connected mode

can also receive SIB3. Whether broadcasting the parameters of cell selection and cell

reselection through SIB3 or SIB4 can be configured at OMCR (Sib3orSib4).SIB4 is not

broadcasted in this version, so the value of parameter Sib3orSib4 is fixed and zero

(SIB3 is sent). In the OMCR, you can configure the following parameters.

Table 3 SIB3/SIB4 parameters that can be configured in the OMCR


Cid Cell ID

QualMeas Measurement Quantity for Cell Selection and Reselection

SIntraSearchPre Sintrasearch Configuration Tag

SIntraSearch The threshold that triggers the intra-frequency measurement in the cell

reselection process

SInterSearchPre Sintersearch Configuration Tag

SInterSearch The threshold that triggers the inter-frequency measurement in the cell

reselection process

SSearchHCS Pre SsearchHCS Configuration Tag

SSearchHCS The threshold that triggers the measurement in the HCS cell reselection process

SSearchRat The threshold that triggers the inter-system measurement in the cell reselection

process

SHCSRatPre SHCS,RAT Configuration Tag

SHCSRat The threshold that triggers the inter-system measurement in the HCS cell

reselection process

SLimitRat The threshold that triggers the inter-system cell measurement in the cell

reselection process



9999


QQualMin The minimum cell quality requirement level

QRxLevMin The minimum cell receive electrical level threshold

DltaQRxLevMinPr DeltaQrxlevmin Configuration Tag

DltaQRxLevMin The minimum cell receive electrical level threshold increment

1.2.4 SIB5/SIB6

SIB5 and SIB6 are mainly used to configure the common transport channels and

common physical channels. SIB5 contains the parameters of the auxiliary common

control channels in IDEL mode; SIB6 contains the parameters of the common physical

channels or shared physical channels in connected mode. The UE in Idle mode uses

SIB5; the UE in connected mode uses SIB6. If SIB6 does not exist, the UE in the

connected mode also uses SIB5. Whether broadcasting the parameters of common

transport channels and common physical channels through SIB5 or SIB6 can be

configured at OMCR (Sib5orSib6). SIB6 is not broadcasted in this version, so the value

of parameter Sib5orSib6 is fixed and zero (SIB5 is sent)..

In the OMCR, you can configure the following parameters.

Table 4 SIB5/SIB6 parameters that can be configured in the OMCR


TfsIndex

Transmission format index. It is used to indicate the attributes of a transport

channel, including channel type, transport format number, number of transport

blocks, transport block size, transmission time interval, coding rate, rate

matching attribute.

ChType Channel Type

TfNum Transport Format Number

TrBlkNum Number of Transport Blocks

RlcSize Transport Block Size

TTI Transmission Time Interval

CodingRate Coding Rate

RateMatchAttr Rate Matching Attribute

CRCSize CRC Size

NiNumPerFrame Number of NI per Frame

CPCId MICH Common Physical Channel ID

MichPwr MICH Power(dB)

MichChCode MICH Channelisation Code No.

UMTS Access Control

10101010


SttdInd MICH STTD Indicator

SttdInd AICH STTD Indicator

ChCode AICH Channelisation Code No.

AichTranTime AICH Transmission Timing

AichPwr AICH Power

MplexPos Multiplexing Position

PCHInd Indicator for SCCPCH Carrying PCH

DlScraCode SCPICH Scrambling Code

ChCode SCPICH Channelisation Code No

ChCode PICH Channelisation Code No.

SttdInd PICH STTD Indicator

CPCId Pich Common Physical Channel ID

PichPwr PICH Power

SttdInd PCCPCH STTD Indicator

Signature Available Signature

AvailSubChanNum PRACH Available Subchannel Number

AvailableSF PRACH Available SF

PreamScraCode PRACH Preamble Scrambling Code

PcpichPwr P-CPICH Power(dBm)

PunctLimit Puncturing Limit

SignalFach FACH Usage

TfcsIndex Index of a transmission format combination set. It must be configured for

S-CCPCH or PRACH.

CtfcNum

Number of transmission format combination sets. It must be configured for

S-CCPCH or PRACH.

Ctfc

ID of a transmission format combination. It must be configured for S-CCPCH or

PRACH.

SCCPCHUsage SCCPCH Usage

SccpchOffset SCCPCH Frame Timing Offset

SttdInd SCCPCH STTD Indicator

DlScraCode S-CCPCH Scrambling Code

DlChCodeNo S-CCPCH Channelisation Code No.

SlotFmt S-CCPCH Slot Format

SttdInd P-CPICH STTD Indicator

1.2.5 SIB7

SIB7 is the system information block that is updated periodically. The timer of SIB7 is

calculated as follows:



11111111

Expiration timer = MAX(32,SIB_REP * ExpirationTimeFactor)

SIB_REP is the transmission interval of SIB7 and is obtained at the time of broadcast

scheduling; ExpirationTimeFactor is the timeout factor of SIB7 and is set to 2

invariably.

SIB7 is sent by the RNC or Node B. By configuring the parameter

SIB7Originator in the OMCR, you can specify the transmitting end for SIB7.By

Default, the Node B sends SIB7 for reducing the transmission time.

SIB7 contains the parameters needed in the calculation of the PRACH preamble power.

The table below lists the parameters that can be configured in the OMCR.



DynPstLevelInit Initial Dynamic Persistence Level

1.2.6 SIB11/SIB12

SIB11/SIB12 is used to configure cell measurement control information. SIB11

specifies the measurement control information required by the UE in Idle mode;

SIB12 specifies the measurement control information required by the UE in

FACH state. If SIB12 is not broadcasted, the UE in connected mode can also

use the configuration information specified by SIB11. Whether SIB11 or SIB12

is sent can be configured at OMCR (Sib11orSib12).SIB12 is not broadcasted in

this version, so the value of Sib11orSib12 is fixed and zero (SIB11 is sent).

1.2.7 SIB15

SIB15 contains DGPS, astronomical information, calendar information, and

UTC and ionization revision information, cell location information, and

encryption or not. SIB15 is not broadcasted in this version.

1.2.8 SIB18

SIB18 specifies the PLMN tag that must be considered by the UE in Idle or connected

mode. In the OMCR, you can configure the following parameters.


UMTS Access Control

12121212


NMCC Mobile Country Code of Neighbouring Cell

NMNC Mobile Network Code of Neighbouring Cell

1.2.9 SIB11bis

The content of SIB11bis is same with SIB11, it can alleviate the lack of SIB11 space

when there is too many adjacent cells. The parameter “SIB11orSIB11bis” can specify if

an adjacent cell information can be broadcast through SIB11bis. So the adjacent cell’s

information will broadcast by SIB11bis when the space of SIB11 is depleted.

Table 7 SIB11bis parameters that can be configured in the OMCR (intra, inter, inter-RAT adjacent cell information)


SIB11ORSIB11BIS Specify if an adjacent cell information can be broadcast through

SIB11bis

13131313

2 RRC Connection Setup and Release

2.1 RRC Connection Setup

The RRC connection can be established over:

� A dedicated channel

� A common channel

The following figure shows the RRC connection establishment flow.

Sour ceNode B

UE

RRCRRC CONNECTI ON REQUEST

[ CCCH]

Tar getNode B

Dr i f tRNC

SourceRNC

RRC

RRCRRC CONNECTI ON SETUP

[ CCCH]RRC

RRCRRC CONNECTI ON SETUP COMPLETE

[ DCCH]RRC

Condition setup RRC connection on DCH

RL Set up

RRCRRC CONNECTI ON SETUP

[ CCCH]RRC

RRCRRC CONNECTI ON SETUP COMPLETE

[ DCCH]RRC

Condition setup RRC connection on FACH

Tr anspor t channel sel ect i on

Condition RRC connection reject

RRCRRC CONNECTI ON REJET

[ CCCH]RRC

Condition RL setup successful

Condition RL setup failed

Condition% expiration of waiting RRC CONNECTION COMPLETE

RL Del et e

RRC CONNECTI ON REJET[ CCCH]

RRCRRC

Load balance of RRC

Figure 2 RRC connection establishment flow

UMTS Access Control

14141414

2.1.1 Establishing an RRC Connection over a Dedicated Transport channel

When receiving the RRC CONNECTION REQUEST message from a UE, the

RNC specifies the channel over which the RRC connection is to be established

according to the parameter InitRrcOnDch (Type of Transport Channel for Initial

RRC Connection Setup) in the OMCR.

If the parameter InitRrcOnDch is set to 0 (Forced to DCH and Using Normal Speed Signaling)

or 1 (Forced to DCH and Using 13.6Kbps signaling), or 5(Forced to DCH and using

27.2Kbps), the RNC establishes the RRC connection over the DCH channel.

If the parameter InitRrcOnDch is set to 3 (Not Forced, Using 3.4Kbps Signaling on Cell-DCH

State) or 4 (Not Forced, Using 13.6kbps Signaling on Cell-DCH State), or 6(Not Forced, Using

27.2Kbps Signaling on Cell-DCH State), the RNC selects to establish the RRC

connection over the DCH according to the Establishment_cause (for example, the UE

initiates a call) in the RRC CONNECTION REQUEST message.

The RNC obtains the cell where the radio link is to be set up using the inter-frequency

load balance algorithm.

The RNC establishes a radio link at the Iub interface. (for more details, refer to the

section “Establishing Iub Interface Radio Link”.)

After the radio link is established successfully, the RNC sends the RRC

CONNECTION SETUP message to the UE.

If the parameter InitRrcOnDch is set to a value that indicates using high speed

signaling, the RNC fills in 13.6k high speed SRB for the parameter Dynamic

Transport Format Information in the RRC CONNECTION SETUP message.

Otherwise, the RNC fills in 3.4k common SRB. If the 13.6K SRB has been

established, the RNC fills in 3.4K SRB when RAB assignment starts.

RNC will retransmit RRC CONNECTION SETUP message once again if RNC haven’t

received RRC CONNECTION SETUP COMPLETE message from UE after 0.7

seconds.

The RNC receives the RRC CONNECTION SETUP COMPLETE message from the

UE, indicating that the RRC connection is established successfully. The process ends.

2.1.2 Establishing an RRC Connection over a Common Transport channel

When receiving the RRC CONNECTION REQUEST message from a UE, the



15151515

RNC specifies the channel over which the RRC connection is to be established

according to the parameter InitRrcOnDch in the OMCR.

If the parameter InitRrcOnDch is set to 2 (Forced to FACH), the RNC establishes the

RRC connection over the FACH channel.

If the parameter InitRrcOnDch is set to 3 , 4, or 6, the RNC establishes the RRC

connection according to the Establishment_cause:if services are initiated

immediately after the setup of RRC connection(for example, the value of

Establishment cause is Originating Conversational Call), RNC will select DCH

channel; if there is only a signaling process, instead of setting up services, that

should be completed after RRC connection(for example, the value of

Establishment cause is registration ), RNC will select common channel to bear

signaling.

The RNC selects the SCCPCH channel according to the Initial UE Identify of the UE.

Index of selected SCCPCH = Initial UE Identity” mod K. K represents the number of

FACH SCCPCH channels of the cell. The RNC sends the RRC CONNECTION

SETUP message over the SCCPCH channel to the UE and sends the SRB

configuration.

RNC will retransmit RRC CONNECTION SETUP message once again if RNC haven’t

received RRC CONNECTION SETUP COMPLETE message from UE after 0.7

seconds.

The RNC receives the RRC CONNECTION SETUP COMPLETE message from the

UE, indicating that the RRC connection is established successfully. The process ends.

2.2 Handling Abnormality in the RRC Connection Setup

2.2.1 Wireless Link Setup Failure

If the radio link setup fails, the RNC sends the RRC CONNECTION REJECT

message to the UE and fills in Wait Time in the message. The parameter Wait

Time specifies the duration (from the reception of the RRC CONNECTION

REJECT message to the time of sending access request) during which the UE

has to wait. The parameter Twait can be configured in the OMCR.

UMTS Access Control

16161616

2.2.2 Failure to Receive RRC Connection Setup Response From UE

If RNC havn’t received RRC CONNECTION SETUP COMPLETE for waiting 5

seconds from the first transmitting of RRC CONNECTION SETUP, the RRC

connection setup fails. The RNC deletes the radio link at the Iub interface if the

wireless link has been set up( i.e. this RRC connection has been planed on the

dedicated transmission channel) (for details, refer to the section “Releasing the Iub

Interface Radio Link”). As a result, the RRC connection setup fails and the UE is still

in idle mode.

If radio links have been set up already on Iub interface, RNC will delete the radio links

on Iub ( please refer to the chapter of “Releasing the Iub Interface Radio Link”)

2.3 Releasing the RRC Connection

The causes triggering the RRC connection release include:

� The connection carrying services data or NAS signaling is released normally;

� The Node B detects radio link failure;

� The RNC monitors the RLC connection failure;

� The UE in the DCH or FACH state sends CELL UPDATE message. The value of

AM_RLC error indication (RB2, RB3 or RB4) is true.

� The UE in the FACH state sends the CELL UPDATE message to the RNC. The

cause is Radio link failure or RLC unrecoverable error.

The UE in the FACH or PCH state have not exchanged any message or data within the

period of T305 + 1 minute.

Any of the above occasions may trigger the RRC connection release flow. Figure 3

shows the RRC connection release flow.



17171717

Sour ce

Node BUE

RRCRRC CONNECTI ON RELEASE

[ DCCH% UM RLC RB1% ]

Tar get

Node B

Dr i f t

RNC

Sour ce

RNC

RRC

RRCRRC CONNECTI ON RELEASE COMPLETE

[ DCCH% UM RLC RB1% ]RRC

Condition RRC connection release on DCH

RL Del et e

RRCRRC CONNECTI ON RELEASE

[ CCCH% DCCH% AM RLC RB2% ]RRC

RRCRRC CONNECTI ON RELEASE COMPLETE

[ CCCH% DCCH% AM RLC RB2% ]RRC

Condition RRC connection release on FACH

Figure 3 RRC connection release flow

As shown in the above figure, the RNC sends RRC CONNECTION RELEASE

message to the UE using SRB1 to request for the release of the RRC

connection. The RNC fills in information in the RRC CONNECTION RELEASE

message. The information includes the frequency information of the GSM

network and UMTS FDD network under the PLMN of the current cell and

BCCH frequency range of the surrounding GSM cells and surrounding UMTS

cells so that the UE in Idle mode can quickly search the desired cell. The fill-in

frequency information related to the GSM network and FDD network includes

GsmBARangeNum (number of GSM frequency bands), GsmURange[32] (upper

limit of the GSM frequency range), GsmLRange[32] (lower limit of the GSM

frequency range), FDDFreqRngNum (number of FDD frequency bands), Luarfcn[8]

(lower limit of the FDD UMTS frequency range), and Uuarfcn[8] (upper limit of

the FDD UMTS frequency range).

2.3.1 Releasing the RRC Connection Established over the Dedicated Channel

The UE in the DCH state receives the RRC release request from the RNC and

sends the RRC CONNECTION RELEASE COMPLETE message in the UM

mode to the RNC and starts the T308 timer. When the T308 timer expires, the

UMTS Access Control

18181818

UE retransmits the RRC CONNECTION RELEASE COMPLETE message. The

retransmit event count is decided by N308. The wait time (T308) and the

maximum retransmit event count (N308) can be configured in the OMCR.

The UE in the FACH state receives the RRC release request from the RNC. The UE

only sends the RRC CONNECTION RELEASE COMPLETE message for once.

The RNC releases the radio link from the Iub interface.

2.3.2 Releasing the RRC Connection Established over the Common Channel

The RNC sends the RRC CONNECTION RELEASE message over the CCCH channel

to the UE or sends the RRC CONNECTION RELEASE message through SRB2 to the

UE, requesting the UE to release the RRC connection.

The UE in the FACH state receives the RRC release request from the RNC. The UE

only sends the RRC CONNECTION RELEASE COMPLETE message through the

CCCH for only one time.

The RNC receives the RRC CONNECTION RELEASE COMPLETE message from

the UE and releases the local resources. The RRC connection is released successfully.

2.3.3 Handling Abnormality in the RRC Connection Release

If the RNC has not received the RRC CONNECTION RELEASE COMPLETE

message from the UE after sending the RRC CONNECTION RELEASE message to

the UE, the RNC retransmits the RRC CONNECTION RELEASE message. The

parameter NreTran specifies the maximum retransmit event count of the RRC

CONNECTION RELEASE message and can be configured in the OMCR.

If the RNC has sent the RRC CONNECTION RELEASE message for NreTran times

and after 500ms not received the RRC CONNECTION RELEASE COMPLETE

message, the RNC considers the RRC connection release complete and

releases the local resources. �

19191919

3 NAS Message Transfer

3.1 NAS Message Forwarding Flow

Figure 4 NAS message forwarding flow

The NAS message forwarding involves three occasions: initial direct transfer, uplink

direct transfer, and downlink direct transfer.

Initial direct transfer: When the RNC receives the INITIAL DIRECT TRANSFER

message from the UE, it establishes the Iu interface connection.

Uplink direct transfer: The RNC receives the UPLINK DIRECT TRANSFER message

from the UE, forwards the information in the message to the CN, and then sends the

DIRECT TRASFER message to the CN.

Downlink direct transfer: The RNC receives the DIRECT TRASFER message from the

CN, forwards the information in the DIRECT TRASFER message to the UE, and

UMTS Access Control

20202020

transmits the DOWNLINK DIRECT TRANSFER message to the UE.

3.2 Setting up and Releasing the Iu Interface Connection

3.2.1 Setting up the Iu Interface Connection

After the RRC connection is set up successfully, the UE sends a message to the RNC.

After receiving the message, the RNC initiates the setup of the Iu interface connection

between the RNC and the CN and sends the initial NAS-PDU to the CN. See the

following.

UE

INITIAL DIRECT TRANSFER% EP %

RNC

RRC

SCCP connection setup

% RANAP% INITIAL UE MESSAGE%

RANAP DIRECT TRANSFER% EP %

CN

%

RRC

%

RANAP

NNSF

Without Iu connection

Iu connection has already Setup

Figure 5 Setting up the Iu interface connection

After the RRC connection setup, the UE sends the initial message to the RNC. The

RNC receives the direct transfer message from the UE.

The RNC judges whether the Iu interface connection between itself and the CN. If yes,

the RNC sends direct transfer message to the CN. If not, it does as follows:

� If the RNC supports the Iu Flex function, it selects the CN node through

the non-access layer node selection function (NNSF). If the RNC does not

support the function, it selects the default CN node.

� The RNC initiates the setup of the connection to the selected CN and sends the

initial direct transfer message to the CN.

If the RNC serving as the DRNC receives the RELOCATION REQUEST message

from the CN, the DRNC sets up the RAB resources. After completion of the setup, it

sends the RELOCATION REQUEST ACKNOWLEDGE message to the CN, and then

sets up the Iu interface connection.



21212121

3.2.2 Releasing the Iu Interface Connection

The service release, signaling release, or the Iu release request from the RNC may

trigger the Iu interface connection release. The Iu interface release may be initiated by

the CN or RNC. The Iu interface connection release initiated by the CN involves two

occasions: Iu interface connection release caused by service release; Iu interface

connection release caused by signaling release. The following describes the Iu interface

connection release process:

� Iu interface connection initiated by the CN

− When the UE is in the DCH state, it initiates a single service and then releases the

service, or the UE initiates simultaneous multiple services and then releases all

simultaneous multiple services.

Figure 6 UE in DCH state releases the Iu interface connection

The CN sends the IU RELEASE REQUEST message to the RNC. The RNC releases

the RAB resources and returns the IU RELEASE COMPLETE message to the CN.

The RNC releases the RRC connections, RB resources, and Iub Interface Radio Links.

If the UE is in the macro diversity status, it needs to notify the DRNC to release the

radio link.

− When the UE is in the DCH state, it initiates the CS + PS service and releases a

service.

UMTS Access Control

22222222

Figure 7 CS+PS domain services are provided concurrently. Release the service of one domain



The RNC reconfigures the radio link and modify the radio link configuration. The RNC

then releases the RB carrying the service.

The RNC sends the SIGNALING CONNECTION RELEASE message to the UE,

notifying the UE to release the signaling connection of the corresponding domain.

− When the UE is in the FACH state, it initiates a single service and then releases

the service, or the UE initiates simultaneous multiple services and then releases

all simultaneous multiple services.

Figure 8 The UE in FACH state releases the Iu interface connection



23232323



The RNC releases the RRC connection and the RB resources.

− When the UE is in the PCH state, it initiates a single service and then releases the

service, or the UE initiates simultaneous multiple services and then releases all

simultaneous multiple services.

Figure 9 The UE in PCH state releases the Iu interface connection

The CN sends the IU RELEASE REQUEST message to the RNC. The RNC initiates

the paging by sending the paging message of PAGING TYPE 1 to the UE. After

receiving the paging message, the UE sends the CELL UPDATE message with the

cause value of Paging Response to the RNC. After receiving the CELL UPDATE

message, the RNC sends the IU RELEASE COMPLETE message to the CN.

The RNC releases the RRC connection.

− When the UE is in connected mode, it does not initiate any service. The CN

requires the release of the Iu interface connection (signaling release).

UMTS Access Control

24242424

Figure 10 Iu interface connection release caused by signaling release

The CN sends the IU RELEASE REQUEST message to the RNC. The RNC returns

the IU RELEASE COMPLETE message to the CN.

The RNC releases the RRC connection. The UE in the DCH state needs to release the

radio link.

� The RNC initiates the Iu interface connection.

UE CNRNC

Iu Release Command

Iu Release Complete

Iu Release Request

Signaling Connection

Release Indication

Node B

Iu signaling bearer release

Signaling Connection Release

Condition% Signaling connection release originated by UE

Figure 11 The RNC initiates the Iu interface connection release

The RNC initiates the Iu interface connection release because the UE initiates signaling

connection release or the RNC detects the radio connection abnormality. This chapter

mainly describes the Iu interface connection release caused by the UE signaling



25252525

connection release. For example, the UE performs location updating in the CS domain

and route updating in the PS domain. When the location updating or route updating is

finished, the UE immediately notifies the RNC of signaling connection release. For

details on the Iu interface connection release caused by the radio connection

abnormality detected by the RNC, refer to the section “Radio Connection Monitor”.

If the UE notifies the RNC of the release of a signaling connection, the UE sends the

SIGNALLING CONNECTION RELEASE INDICATION message to the RNC. When

the RNC receives the SIGNALLING CONNECTION RELEASE INDICATION

message, if the domain where the signaling connection is released is the only CN

domain of the UE, the RNC releases the RRC connection. Otherwise, the RNC sends

the IU RELEAST REQUEST message, requesting for the release of the Iu interface.

When the CN receives the IU RELEAST REQUEST message, if the CN decides to

release the Iu interface connection, it sends the IU RELEASE COMMAND message to

the RNC. The RNC returns the IU RELEASE COMPLETE message and releases the

Iu interface signaling bearer.

27272727

4 Paging

4.1 Paging Flow

According to the paging initiators, the paging involves the following occasions:

SRNC CNUE

Condition% PAGING originated by CN

NodeB DRNC

Condition% PAGING originated by RNC

Condition% PAGING originated by RNC , on Iur interface

PAGING

PAGING TYPE 1

PAGING TYPE 2

Condition% UE in IDLE% PCH

Condition% UE in DCH% FACH

PAGING REQ

PAGING TYPE 1

PAGING TYPE 2

Condition% UE in IDLE% PCH

Condition% UE in DCH% FACH

Figure 12 Paging flow

� Receive the paging message from the CN and broadcast message through the

Node B under the RNC.

The RNC sends paging messages of PAGING TYPE1 to the UE in Idle or PCH state

and sends the paging message of PAGING TYPE2 to the UE in the CELL_FACH or

CELL_DCH state.

� Receive a paging message from another RNC or a paging message from the local

RNC without spanning any Iur interface.

The RNC sends paging messages of PAGING TYPE1 to the UE in Idle or PCH state

and sends the paging message of PAGING TYPE2 to the UE in the CELL_FACH or

CELL_DCH state

� The local RNC initiates paging that must span an Iur interface.

UMTS Access Control

28282828

The RNC sends a Paging Request message through RNSAP to the DRNC, requesting

the DRNC to page the UE.

4.2 PAGING TYPE 1

When the UE is in the Idle, or URA_PCH state, the RNC receives the paging

message from the CN and then sends the paging message of PAGING TYPE 1

over the PCH channel to the UE.To improve the chance of receiving the paging

message by the UE, the RNC repeatedly sends the paging message of

PAGING TYPE 1 to the UE. The maximum retransmit event count

(PagingSendTimes) can be configured in the OMCR.

The PCH channel has a corresponding PICH physical channel. The page indicator (PI)

is transmitted over the PICH channel, with each PI corresponding to a group of UEs.

The following lists the formula for calculating the PI:

PI = DRX Index mod Np

Where:

DRX Index = IMSI div 8192

Np = the number of PIs included in a PICH frame. It can be configured in the OMCR.

The UE judges whether the network is paging itself by monitoring its own PI. Each

PICH frame can contain the PI of multiple UEs. The parameter Np, namely the

number of PIs included in a PICH frame, can be configured in each PICH

frame. The more the parameter Np, the larger the transmit power of the PICH

(PichPwr) will be. The table shows the relations between the parameter Np and

the transmit power.

Number of PIs in each frame Number of repeated bits in the

PICH

Transmit power of the PICH in

comparison with that of the CPICH

18 16 -7

36 8 -7

72 4 -5

144 2 -2

For saving power, the UE in the Idle or PCH state monitors the PICH channel in the

Discontinuous Reception (DRX) mode. In the DRX mode, the UE monitors the PI once

every DRX period. That is, each UE has its own paging occasion (PO). The UE



29292929

monitors each PICH frame in the corresponding SFN and finds its own PI in the frame

according to the calculated PI.Therefore; the RNC fills in the PI in the message

transmitted over the PICH channel according to the paging occasion of the UE. In the

FDD system, a DRX period = 2k frames

In the OMCR, you can configure three DRX cycle length coefficients: CS Domain

DRX Cycle Length Coefficient (Kcs), PS Domain DRX Cycle Length Coefficient

(Kps), and UTRAN DRX Cycle Length Coefficient (KUtran).

The RNC calculates the PO as follows:

� When the UE is in the Idle mode, the RNC calculates K in the DRX period

according to Kcs, Kps, and DRX Cycle Length Coefficient in the paging message

from the CN.

For paging messages from the CS domain, K = Min(Kcs,Kps)

For paging messages from the PS domain, if the CN adds DRX Cycle Length

Coefficient to the paging message, K = Min (Kcs,Kps,DRX Cycle Length

Coefficient).If the CN does not add DRX Cycle Length Coefficient to the paging

message, K = Min(Kcs,Kps).

When the UE is in the PCH state, the RNC calculates K in the DRX period according

to Kcs, Kps, KUtran, and DRX Cycle Length Coefficient in the paging message from

the CN.

For paging messages from the CS domain, K = Min(Kcs, KUtran)

For paging messages from the PS domain, if the CN adds DRX Cycle Length

Coefficient to the paging message, K = Min (Kps,KUtran,DRX Cycle Length

Coefficient).If the CN does not add DRX Cycle Length Coefficient to the paging

message, K = Min(Kps,KUtran).

The following lists the formula for calculating the PO:

Paging Occasion = {(IMSI div N) mod (DRX cycle length div PBP)} * PBP + n *

DRX cycle length + Frame Offset

Where:

N = number of SCCPCH channels carried over the PCH in a cell

DRX cycle length = 2k frame, K is calculated according to the above-mentioned

UMTS Access Control

30303030

method.

PBP = 1

n = SFN

When the system broadcast messages are updated, the RNC sends the

paging message of PAGING TYPE 1 to the UE in Idle or PCH state. At the

moment, the system sends PI over the PICH channel during the DRX period. K

= MAX(Kcs,Kps, KUtran).

4.3 PAGING TYPE 2

When the UE is in the DCH or FACH state, the UTRAN initiates the paging process

and sends a paging message of PAGING TYPE 2 over the DCCH channel. The

UTRAN configures paging cause in the message.

After the UE in the DCH or FACH state receives the message of PAGING TYPE 2, it

starts the paging reception process and reports paging cause and paging record type

identifier to the upper layer.

11 WO_NA03_E1_0 UMTS Access Control-34

Documents

Transcript of 11 WO_NA03_E1_0 UMTS Access Control-34