148504581 ZTE UMTS Connection Management Feature Guide V6!1!201204

Connection Management

Feature Guide

WCDMA RAN

Connection Management Feature Guide

ZTE Confidential Proprietary 1


Version Date Author Reviewer Notes

V6.0 2011-5-30 FengChao Lu Li

Eliminate Asian Character

2.1.10 RRC Connection Redirect: modify

2.1.1 System Information Broadcasting: add SIB19

3.1.2.10 SIB19: add

3.4.1 Redirection for Load Reduction: RCP CPU

Load check method is modified

4.9.2.2 PriRedirectRat:modify

4.9.1 Parameter List:add RrcRdtSwch

4.9.2.3 RrcRdtSwch:add

2.1.16 Iu Interface Interruption Protection: add

3.2.1.1 Enable the DSAR:modify

3.2.1.4 Disable the DSAR:modify

4.3.2.1 CsDsarSwh:modify

4.3.2.2 PsDsarSwh:modify

4.3.2.14 Number of Cells Updating SIB3:add

4.3.2.15 Time Interval Updating SIB3 among

Cells:add

2.1.10 RRC Connection Redirect: add E-UTRA

TDD.

3.4.1 Redirection for Load Reduction: add E-UTRA

frequency info and E-UTRA TDD.

4.9 RRC Connection Redirection Parameters: add

EutranCellType

4.9.2.4 EutranCellType

Figure 20 Call re-establishment triggered by

Network:

delete the cellupdate msg line.

3.10.2 Call Re-establishment Triggered By

Network

1.1/1.2: add "If cell update is received before

Timer1 Expiry, the Call will be released"

3.4.1 Redirection for Load Reduction:



delete the same coverage condition

3.1.2.1 SIB1 add the description of T317 value

4.1.1 SIB1 Parameter List:delete T317

4.1.2 SIB1 Parameter Configuration: delete T317

4.12 Direct Tunnel: Add

V6.1 2012-02-22 Huangmeiqing

fengchao

3.10.2:add note for CELL UDPATE message.

3.10.1 Processing of Call Re-establishment

(i) delete the decription of fach

3.10.2 Call Re-establishment Triggered By Network

(i) delete the decription of global switch

(ii) delete RB Reconfigure messgae

(iii)add timer TWaitRlRestore/TWaitActSetUpCmp/

WaitRbCompTimer

4.13: add

Modify:

2.1.3 Paging: add description of Virtual LAC paging

3.10.1 Processing of Call Re-establishment:

add description of switch

3.10.2 Call Re-establishment Triggered By

Network: add description of switch

Add:

3.6.4 Virtual Location Area Paging

4.4.2.7 - 4.4.2.9

4.13.2.4 - 4.13.2.15

© 2012 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used

without the prior written permission of ZTE.

Due to update and improvement of ZTE products and technologies, information in this document is subjected to

change without notice.



TABLE OF CONTENTS

1 Functional Attribute............................................................................................... 8

2 Overview ................................................................................................................. 8

2.1 Function Introduction................................................................................................ 8

2.1.1 System Information Broadcasting ............................................................................ 8

2.1.2 Connection Setup and Release ............................................................................... 9

2.1.3 Paging .................................................................................................................... 10

2.1.4 NAS Message Transfer .......................................................................................... 11

2.1.5 Ciphering Algorithm UEA0 and UEA1 ................................................................... 12

2.1.6 Integrity Protection Algorithm UIA1........................................................................ 13

2.1.7 Radio Connection Monitor ..................................................................................... 14

2.1.8 Radio Connection Re-establishment ..................................................................... 14

2.1.9 27.2Kbps High Speed Signaling RB ...................................................................... 15

2.1.10 RRC Connection Redirect...................................................................................... 15

2.1.11 Domain Specific Access Restriction (DSAR)......................................................... 16

2.1.12 Ciphering Algorithm UEA2 ..................................................................................... 16

2.1.13 Integrity Protection Algorithm UIA2........................................................................ 17

2.1.14 Deferred SIB11/12 ................................................................................................. 17

2.1.15 Direct Tunnel .......................................................................................................... 18

2.1.16 Iu Interface Interruption Protection ........................................................................ 18

3 Technical Description.......................................................................................... 19

3.1 System Broadcast .................................................................................................. 19

3.1.1 System Information Broadcasting, Scheduling, and Transmission....................... 20

3.1.2 Information Sent by SIBs ....................................................................................... 22

3.2 DSAR and Cell Bar Access.................................................................................... 32

3.2.1 Overview of DSAR ................................................................................................. 32

3.2.2 Cell Bar Access (CBA) ........................................................................................... 37

3.3 RRC Connection Setup and Release .................................................................... 39

3.3.1 RRC Connection Setup.......................................................................................... 39

3.3.2 Handling Abnormality in the RRC Connection Setup ............................................ 41

3.3.3 Releasing the RRC Connection ............................................................................. 42

3.4 RRC Connection Redirection ................................................................................. 44

3.4.1 Redirection for Load Reduction ............................................................................. 44

3.4.2 Redirection for Emergency Call ............................................................................. 48

3.5 NAS Message Transfer .......................................................................................... 50

3.5.1 NAS Message Forwarding Flow ............................................................................ 50

3.5.2 Setting up and Releasing the Iu Interface Connection .......................................... 51

3.6 Paging .................................................................................................................... 57



3.6.1 Paging Flow............................................................................................................ 57

3.6.2 PAGING TYPE 1 .................................................................................................... 58

3.6.3 PAGING TYPE 2 .................................................................................................... 60

3.6.4 Virtual Location Area Paging ................................................................................. 60

3.7 Security Mode Control............................................................................................ 61

3.7.1 Security Mode Control Flow ................................................................................... 61

3.7.2 Encryption Algorithm and Parameters ................................................................... 66

3.7.3 Integrity Protection Algorithm and Parameters...................................................... 68

3.8 RAB Force Queue .................................................................................................. 69

3.9 Radio Connection Monitor ..................................................................................... 70

3.10 Call Re-establishment ............................................................................................ 71

3.10.1 Processing of Call Re-establishment..................................................................... 72

3.10.2 Call Re-establishment Triggered By Network ....................................................... 74

3.11 Managing the Iub Interface Radio Link .................................................................. 77

3.11.1 Establishing the Iub Interface Radio Link .............................................................. 77

3.11.2 Reconfiguring the Iub Interface Radio Link ........................................................... 78

3.11.3 Releasing the Iub Interface Radio Link.................................................................. 79

3.12 Managing the Iur Interface Radio Link................................................................... 79

3.12.1 Reconfiguring the Iur Interface Radio Link ............................................................ 79

3.12.2 Releasing the Iur Interface Radio Link .................................................................. 80

3.13 RB reconfiguration .............................................................................................. 80

3.14 Iu Overload Control ................................................................................................ 81

3.15 Deferred SIB11/12 ................................................................................................. 83

4 Configuration and Parameters ........................................................................... 84

4.1 System Information Broadcasting Parameters ...................................................... 84

4.1.1 SIB1 Parameter List ............................................................................................... 84

4.1.2 SIB1 Parameter Configuration ............................................................................... 86

4.1.3 SIB2 Parameter List ............................................................................................... 97

4.1.4 SIB2 Parameter Configuration ............................................................................... 97

4.1.5 SIB3/SIB4 Parameter List ...................................................................................... 98

4.1.6 SIB3/SIB4 Parameter Configuration ...................................................................... 99

4.1.7 SIB5/SIB6 Parameter List .................................................................................... 106

4.1.8 SIB5/SIB6 Parameter Configuration .................................................................... 108

4.1.9 SIB7 Parameter List ............................................................................................. 119

4.1.10 SIB7 Parameter Configuration ............................................................................. 119

4.1.11 SIB11/SIB12 Parameter List ................................................................................ 120

4.1.12 SIB11bis Parameter Configuration ...................................................................... 120

4.2 Parameters related to Connection Setup and Release ....................................... 121

4.2.1 Parameter List ...................................................................................................... 121

4.2.2 Parameter Configuration ...................................................................................... 121

4.3 DSAR Parameters................................................................................................ 125



4.3.1 Parameter List ...................................................................................................... 125


4.4 Paging Parameters .............................................................................................. 132

4.4.1 Parameter List ...................................................................................................... 132


4.5 Ciphering Parameters ....................................................................................... 136

4.5.1 EncryAlg ............................................................................................................... 136

4.6 Integrity Protection Parameters ........................................................................... 136

4.6.1 IntegrityAlg............................................................................................................ 136

4.7 AMR Service Forced Queue Parameters ............................................................ 136

4.7.1 Parameter List ...................................................................................................... 136


4.8 Radio Connection Monitor Parameters ............................................................... 137

4.9 RRC Connection Redirection Parameters ........................................................... 138

4.9.1 Parameter List ...................................................................................................... 138


4.10 Iu Overload Control .............................................................................................. 140

4.10.1 TigOR ................................................................................................................... 140

4.10.2 TinTR .................................................................................................................... 140

4.11 Deferred SIB11/12 ............................................................................................... 140

4.11.1 Parameter List ...................................................................................................... 140


4.12 Direct Tunnel ........................................................................................................ 141

4.12.1 Parameter List ...................................................................................................... 141


4.13 Call Re-establishment .......................................................................................... 142

4.13.1 Parameter List ...................................................................................................... 142


5 Counter and Alarm ............................................................................................ 150

5.1 Counter List .......................................................................................................... 150

5.2 Alarm List.............................................................................................................. 170

6 Glossary.............................................................................................................. 170

7 Reference............................................................................................................ 171



FIGURES

Figure 3-1 System broadcasting ........................................................................................... 20

Figure 3-2 Example of DSAR polling mode........................................................................ 35

Figure 3-3 RRC connection establishment flow .................................................................... 39

Figure 3-4 RRC connection release flow .............................................................................. 43

Figure 3-5 NAS message forwarding flow............................................................................. 50

Figure 3-6 Setting up the Iu interface connection ................................................................. 51

Figure 3-7 UE in DCH state releases the Iu interface connection ........................................ 52

Figure 3-8 Release the service of one domain ..................................................................... 53

Figure 3-9 The UE in FACH state releases the Iu interface connection............................... 54

Figure 3-10 The UE in PCH state releases the Iu interface connection............................... 54

Figure 3-11 Iu interface connection release caused by signaling release ........................... 55

Figure 3-12 The RNC initiates the Iu interface connection release ...................................... 56

Figure 3-13 Paging flow......................................................................................................... 57

Figure 3-14 Security mode control flow................................................................................. 62

Figure 3-15 Querying the UE capability ................................................................................ 65

Figure 3-16 Encryption and decryption process ................................................................... 67

Figure 3-17 Using the f9 algorithm for integrity protection.................................................... 68

Figure 3-18 Radio link failure................................................................................................. 70

Figure 3-19 Call re-establishment ......................................................................................... 73

Figure 3-20 Call re-establishment triggered by Network ...................................................... 75

Figure 3-21 RB reconfiguration ............................................................................................. 81

Figure 3-22 Iu overload control.............................................................................................. 83

TABLES

Table 3-1 Scheduling levels of the SIBS ............................................................................... 21



Table 3-2 SIB2 parameters that can be configured in the OMCR ........................................ 26

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

Table 3-4 SIB5/SIB6 parameters that can be configured in the OMCR ............................... 28

Table 3-5 SIB7 parameters that can be configured in the OMCR ........................................ 30

Table 3-6 SIB18 parameters that can be configured in the OMCR ...................................... 31

Table 3-7 SIB11bis parameters that can be configured in the OMCR (intra, inter, inter-RAT

adjacent cell information) ......................................................................................................... 31

Table 3-8 Absolute Priority Reselection Criteria Switch ....................................................... 31

Table 5-1 Connection Management Counter ...................................................................... 150



1 Functional Attribute

System version: [RNC V3.11.10/V4.11.10, Node B V4.11.10, OMMR V3.11.10/V4.11.10,

OMMB V4.11.10]

Attribute: necessary function

NEs involved:

UE Node B RNC MSCS MGW SGSN GGSN HLR

√ √ √ √ √

Note:

*-: Not involved

*√: Involved:

Dependency: none

Mutual exclusive functions: none

Remarks: The radio link management function of the Iur interface requires that the Iur

interface must be configured between two RNCs.

2 Overview

2.1 Function Introduction

2.1.1 System Information Broadcasting

The function allows an entity to broadcast system information periodically with the cell as

the basic unit and update the system information. The system information broadcasted

over the BCH channel mainly includes the following contents:

Public Land Mobile Network (PLMN) ID, location area (LA), route area (RA)

Information on the timers and counters related to the Radio Resource Control (RRC)

connections



Configuration information of the UTRAN registration area (URA)

Cell selection and reselection parameters

Parameters for configuring the common channels, such as FACH, PCH, and RACH

Information on the uplink interference related to the auxiliary power control

UE measurement control message over the idle or common channel

Parameters of the adjacent cell

AGPS location information

The system information is included in the system information block (SIBs). The SIB

supported by the ZTE RAN includes SIB1, SIB2, SIB3, SIB5, SIB7, SIB11, SIB18, SIB19.

Except SIB7 (including the uplink interference information) that can be measured and

sent by the Node B, all SIBs are controlled and encoded by the RNC.

Currently, a SIB can be cut into a maximum of 16 partitions, each partition’s size is up to

222bit, so the maximum size of a SIB is 3552bit, however, the maximum number of

adjacent cell information that can contained in a single SIB is 96, it may exceed the

3552bit. To solve this problem and keep the current system information process stratege,

the SIB11bis is introduced, it’s structure is similar to SIB11 but optimized. For adaption

SIB11bis, the SIB18 is also add the PLMN indicator for the cells which inside the

SIB11bis.

ZTE RAN li fted the limits of the maximum number of adjacent cells in prior version. Now

it allow 31 intra-frequence adjacent cells, plus 32 inter-frequence adjacent cells and 32

inter-RAT adjacent cells. and it also introduce a new parament which indicate the current

adjacent cell information should included in SIB11 or SIB11bis. The system will construct

the SIB11 and SIB11bis according to the adjacent cell configuration, and modify the

SIB18 content according to the 3GPP protocol.

2.1.2 Connection Setup and Release

This function is used to manage the setup and release of the RRC connections between

the UTRAN and the UE so that the signaling bearer can be established between the UE



and the UMTS Terrestrial radio access network (UTRAN).

When a UE needs to establish a connection with the network, it involves several

scenarios, such as LA or RA updating, service request, and paging response. When the

UE initiates the RRC connection setup requests according to the system broadcast

parameters, the UTRAN allocates resources to set up the Signaling Radio Bearer (SRB)

for the UE and finishes the RRC connection setup process.

After the completion of RRC connection setup, the UE establishes the Lu connection with

the core network (CN) to update the LA/RA. The SRB also provides the signaling

channel between the UE and the CN. For more details on the Iu connection setup, refer

to ZWF21-01-004 NAS Message Forwarding.

After the completion of RRC connection setup, the UTRAN monitors the Iu connection

and radio connection of the UE. If all Iu connections are released or the radio connection

to the UE is interrupted (refer to the section “ZWF21 -01-007Radio Connection Monitor”),

the UTRAN releases the RRC connection and all resources allocated to the UE.

2.1.3 Paging

When there are service demands in the CN, the system triggers the UE to set up the

connection between the UE and the CN through its paging function. For example, the UE

needs to receive the Short Message Service (SMS) or Multimedia Message Service

(MMS) message, or other users page the UE. The CN sends paging message through

the Iu interface to the RNC. The RNC selects an area according to the RRC connected

state of the UE and sends paging message to the UE.

The UE is in Idle mode

The RNC cannot obtain information on the specific location of the UE. Therefore,

the RNC sends paging message within the LA or RA according to the LA/RA

information carried in the paging message of the CN.

The UE is in PCH mode

The RAN of ZTE supports the URA PCH state. The RNC knows the location

information of the UE in the URA and sends paging messages within the whole

URA.



The UE is in FACH or DCH state

The RNC knows the location information of the UE in the cell and sends paging

messages to the cell.

The ZTE RAN allows the RNC to initiate the paging on the following special occasions:

When there are data packets in the downlink buffer, the RNC sends paging

message to trigger the UE state change from URA_PCH to CELL_FACH and

set up the service bearer for the downlink data transmission.

After the system information changes, the RNC sends the paging message to

notify all the UEs in Idle or PCH state of a cell.

When it is necessary to suspend the RRC connection of a UE in the PCH state,

the RNC sends a paging message to release the RRC connect ion of the UE.

The ZTE RAN supports two paging modes: PAGING TYPE 1 and PAGING TYPE 2:

For the UE in the Idle, URA_PCH state, send paging message of PAGING

TYPE 1.

For the UE in the CELL_FACH, or CELL_DCH state, send paging message of

PAGING TYPE 2.

To improve the success paging rate at boundary of Location area, RNC introduce Virtual

Location Area Paging. When a cell is at boundary of Location area, the paging in this cell

also will be sent to the cell of adjacent Location area.

2.1.4 NAS Message Transfer

Signaling in the Non-Access Stratum (NAS) layer between the UE and the CN must pass

the UTRAN. The signaling in the NAS layer is used to control the UE location updating,

authentication, call setup, call release, and SMS data transfer. The UTRAN device does

not have to resolve and process the NAS signaling and SMS data exchanged between

the UE and the CN. The UTRAN transparently transmits the NAS signaling and SMS

data as the parameters in the DIRECT TRANSFER messages defined by the RANAP

and RRC protocols between the CN and the UE.

The ZTE RAN supports three types of direct forward messages:



INITIAL DIRECT TRANSFER message

Once the UTRAN receives the INITIAL DIRECT TRANSFER message from the UE,

the RNC immediately sets up the SCCP connection with the Iu inter face of the MSC

or SGSN according to the CN (PS or CS) domain label in the message, adds the

NAS message to the INITIAL UE MESSAGE, and sends it to the MSC or the SGSN.

Meanwhile, the RNC records the binding relation between the SCCP connection

and the UE RRC connection, and sets up a channel for NAS messages between

the UE and the CN.

UPLINK DIRECT TRANSFER message

When receiving the UPLINK DIRECT TRANSFER message from the UE, the

UTRAN adds the NAS message to the DIRECT TRANSFER message according to

the label of the CN domain in the message, and forwards the message to the MSC

or SGSN.

DOWNLINK DIRECT TRANSFER message

When receiving the DIRECT TRANSFER message from the CN, the UTRAN adds

the NAS message to the DOWNLINK DIRECT TRANSFER message according to

the relation between the SCCP connection and the RRC connection and forwards

the message to the destination UE.

When the RNC receives a message for releasing the Iu connection from the CN, it

releases the Iu connection of the CN and dismisses the binding relation between the

SCCP and the RRC.

2.1.5 Ciphering Algorithm UEA0 and UEA1

When the Uu interface broadcasts data, the function can be used to encrypt the service

data and signaling data of the user and protect the security of the communication

between the RNC and the UE. The ZTE RAN supports the encryption algorithms UEA0

and UEA1: UEA0 means that the data from the Uu interface are not encrypted; UEA1 is

based on the encryption algorithm f8 of the KASUMI algorithm and supports encryption

and decryption.



Whether the encryption protection function should be enabled and which encryption

algorithm is to be applied can be configured in the CN. Through the security mode

command process of the RAN Application Part (RANAP), a message with key of the

encryption algorithm is sent to the RNC, requesting the RNC to enable the encryption.

The RNC selects an encryption algorithm according to its encryption capability, the

encryption capability of the UE, and priority of encryption algorithms available to the UE,

and then starts the encryption process through the security mode command process of

the RRC.

When the encryption function is enabled, the RNC or the UE encrypts the data to be

transmitted in compliance with the f8 algorithm, with the encryption key and variables

varying with the data volume. The receiver decrypts the data using the same algorithm.

Encryption is implemented in the RLC layer (AM or UM mode) or MAC layer (TM mode).

2.1.6 Integrity Protection Algorithm UIA1

To prevent malicious attack against the Uu interface signalings from the air interface, the

function provides a signaling check mechanism. The ZTE RAN supports the unique

integrity protection algorithm UIA1 defined by the 3GPP. The integrity protection

algorithm f9 is based on KASUMI algorithm and implements the integrity protection.

Whether the integrity protection should be enabled is configured in the CN. The notice of

starting the integrity protection is sent to the RNC through the security mode command

process of the RANAP. The message carries the key of the integrity protection algorithm.

The RNC starts the integrity protection mode through the RRC security mode command

process.

If the integrity protection is enabled, when the RNC or the UE sends the RRC message,

it first calculates the integrity protection authentication code (MAC-I) through the f9

algorithm, and then adds MAC-I to the message to be sent. The receiving end must

adopt an algorithm and a key that are the same as those of the transmitting end,

calculate the XMAC-I (the integrity protection authentication code of the received

message), and compare XMAC-I with the received MAC-I. If they are the same, it

considers the received message correct. Otherwise, it discards the received message.

Not all Uu interface signalings can be protected. The RRC message from the ZTE RAN



for integrity protection complies with the 3GPP TS25.331 protocol.

2.1.7 Radio Connection Monitor

The function monitors the radio connection status of the UE with established RRC. If the

RNC judges that the connection between the UE and the network has been interrupted

because of poor radio quality or other causes, the RNC immediately releases the

resources allocated to the UE (including RB resources with services) and releases the

RRC connection.

The ZTE RAN monitors the radio connections in the following modes:

Node B monitors the RL connection status;

The RNC monitors the RLC connection status;

The RNC monitors the cell update message of the UE;

The RNC monitors the UE keep_alive timer.

When the RNC detects an interrupted line of a UE, the RNC releases the radio resources

and sends an Iu release request message through the Iu interface to the CN to release

the related RAB resources.

2.1.8 Radio Connection Re-establishment

A UE in the DCH state may suffer from temporary radio connection interruption and

cannot continue the services due to burst interference or abrupt changes to the radio

environment. Before the UTRAN detects the radio connection interruption, the UE

recovers the services. At the moment, the UE sends the cell update message with t he

cause as Radio link failure or RLC unrecoverable error (for the service RB) and attempts

to establish network connections.

In this scenario, the ZTE RAN supports re-establishing radio connection between the UE

and the UTRAN and recovers the communication without releasing the original RRC

connection and Iu connection. The user can feel the transient service interruption

brought about by the radio connection re-establishment but this does not cause call drop.



2.1.9 27.2Kbps High Speed Signaling RB

The feature is benefit for reducing the time delay for CS/PS service setting up, and

accelerating SMS services reception. It improves user’s experience.

The feature enables the system to use the 27.2 kbps Signaling Radio Bearer (SRB)

when it establishes the RRC connection, and recovers the 3.4Kbps SRB during RAB

establishment. If 27.2k SRB is set to apply on OMC, ZTE RAN will setup SRB at

27.2kbps to speed up transferring the NAS signaling messages (including location

update message, authentication message, and call setup message) between the UE and

the CN. In different scenarios and in contrast to 13.6kbps SRB, the 27.2 kbps SRB can

reduce the call setup time delay by several hundred ms and facilitate the SMS service

reception.

2.1.10 RRC Connection Redirect

The feature is used to indicate UE to setup RRC connection in other UTRAN frequency

or GSM carrier when system load is high. So it facilitates load balancing between

different UTRAN networks or between UTRAN and GSM network or between UTRAN

and E-UTRAN network and so increases success rate of users’ service access.

During RRC connection procedure, when UTRAN receiving RRC Connection Request

message from UE, admission control is performed. If processor of RNC is in high load

state or all carrier of the sector where UE stays are congested, or emergency call where

UE originated has a same GSM cell coverage, UE will not be able to get service from the

UTRAN network. And if there is other UTRAN cell or GSM cell or E-UTRAN cell

collocated with the cell which the UE t ries to access, RNC transmits RRC Connection

Reject message with “Redirect info” IE to inform UE about frequency information of

collocated adjacent UTRAN or GSM or E-UTRAN cells.

With such information UE will perform a cell-reselection procedure to access to

inter-frequency/inter-system adjacent cell.

If RNC knows by RANAP message that CN is in overload stat, this feature is also be

used to redirect user to other UTRAN frequency or GSM or E-UTRAN carrier.

The RNC support the E-UTRAN FDD cells and the E-UTRAN TDD cells.



2.1.11 Domain Specific Access Restriction (DSAR)

For some critical conditions, e.g. in the sports match, or the large party, large amount of

user access will make the CN overloaded. DSAR function is be used to resolve the

problem, by which the UTRAN inform some users that PS domain or CS domain is

forbidden to access in SIB3. DSAR can limit the network traffic and improve network

stability.

DSAR is based on the AC(Access Class) of UE, and confines part of UEs access in

CS/PS domain. Different restriction strategy can be configured for PS/CS domain.

UTRAN selects part of UEs for access restriction by periodic polling method or

parameter configuration on OMC. When CN overload is resolved, DSAR is stopped for

relative domain.

Further more, ZTE UTRAN support manual DSAR triggering on OMC. In this way, the

operators can control network access more flexibly. For example, the network supports

more CS traffic by DSAR in PS domain.

2.1.12 Ciphering Algorithm UEA2

This feature realizes UEA2, which is known as f8 and is specified in 3GPP R7. The

algorithm f8 is used to protect the confidentiality of the data and signalling sent between

the UE and the RNC.

The followings are the diffirences between UEA2 and UEA1:

1. UEA1 is KASUMI based algorithm and UEA2 is SNOW 3G based algorithm.

2. KASUMI is a Blockcipher with 64-bit block, 128-bit key. SNOW 3G is a 32-bit

word-oriented stream cipher generator with 128-bit key and 128-bit IV.

When a UE makes a connection with the UTRAN, the UE indicates the confidentiality

and integrity algorithms supported by the UE in MS/USIM Classmark. RNC compares

the information with the confidentiality and integrity capability when a user subscribes for

the service, then a proper algorithm is selected. Thus more and more flexible encryption

algorithms are provided.

This feature complies with the security mechanism and SNOW 3G algorithms specified



in 3GPP TS 33.102 TS 35.215~218 TS 35.919.

2.1.13 Integrity Protection Algorithm UIA2

This feature realizes UIA2, which is known as f9 and is specified in 3GPP R7. The

algorithm f9 is used to protect the integrity of the signalling sent between the UE and the

RNC.

The followings are the diffirences between UIA2 and UIA1:

1. UIA1 is KASUMI based algorithm and UIA2 is SNOW 3G based algorithm.

2. KASUMI is a Blockcipher with 64-bit block, 128-bit key. SNOW 3G is a 32-bit

word-oriented stream cipher generator with 128-bit key and 128-bit IV.

When a UE makes a connection with the UTRAN, the UE indicates the confidentiality

and integraty algorithms supported by the UE in MS/USIM Classmark. RNC compares

the information with the integrity capability when a user subscribes for the service and

the RNC capability, then a proper algorithm is selected. Thus more and more flexible

integrity algorithms are provided.

This feature complies with the security mechanism and SNOW 3G algorithms specified

in 3GPP TS 33.102 TS 35.215~218 TS 35.919.

2.1.14 Deferred SIB11/12

Due to SIB11, SIB11bis or SIB12 should be read and stored by the UE before sending

message or acting on received message on FACH after the process of cell reselection or

channel type switching, in case that a lot of neighbouring cells are configured (over 20

neighboring cells for example), this will cause the obvious interruption of services. To

solve this problem, in 3GPP R7 specification, UE is allowed to send messages through

RACH or receive messages through FACH before reading and storing SIB11/12

information.

UTRAN broadcasts through SIB3 to notice if the network supports this feature. If the

feature is applied, UE’s switching to CELL-DCH status must notify the UTRAN that

SIB11/11bis/12 are not read and stored. After switching to a non CELL -DCH status, UE



needs to complete SIB11/11bis/12 reading and storing.

This feature complies with TS 25.331 CR2557R2

2.1.15 Direct Tunnel

After HSPA/HSPA+ is introduced to WCDMA network, data throughput is greatly

increased and the requirements for bandwidth and latency are much higher.

Direct tunnel is officially defined in 3GPP R7 standard. It supports direct connection of

user plane between RNC and GGSN. Direct Tunnel feature is transparent to RNC.

SGSN decides when to use Direct Tunnel. RNC is not involved during direct tunnel

establishment and release. ZTE RAN system supports the following functions, which

interoperates with SGSN to implement Direct Tunnel feature.

Iu PS interface protocol RAB process supports modification on address of peer user

plane.

RNC triggers RAB release request, with reason GTP Resources Unavailable, if

GTP user plane error is indicated.

RNC supports IP on Iu PS interface so that it may connect to Gn interface. ATM on

Iu PS is able to connect to Gn interface as well, but it’s a must to add ATM gateway

router.

2.1.16 Iu Interface Interruption Protection

When both Iu-CS connection and Iu-PS connection are broken down, it is impossible to

provide services to users. when this happened, the UMTS cells are barred by system

information SIB3. It triggers the UE to re-select cells. So operator will not receive user’s

complaints for service incapability. To avoid simultaneous registration of all terminals

moving to other networks, cell barring will be made in sequence. The number of cells to

be barred one time is configurable by operator.

If only one of core domain losses its connection with RAN, RAN initates domain specific

access restriction via “Domain Specific Access Restriction Parameters” in SIB3. It means

the domain is not allowed to be used for access classes 0~9 and UE with these access



classes is not going to request the service for the domain, It avoids too many UE

connection request signaling for rejection from network. So the signaling load to RAN is

reduced.

Iu Interface Interruption Protection is implemented by DSAR, the parameters should be

configured as the following.

“DSAR polling/non-polling” switch is set as disabled.

DSAR function switch is set to “RNC Controls Dynamically CS Domain

DSAR”/“RNC Controls Dynamically PS Domain DSAR”,

PagingLocaBarSwh is set to “UE-initiated paging response and location registration

barred”,

CsACBarredOmcr/PsACBarredOmcr is set to barred for all access class.

For more details, please refer the chapter “3.2 DSAR and Cell Bar Access” in this

document.

3 Technical Description

3.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 informati on block (SIB).



3.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 (for more details, refer to the

section “3.1.2.5 SIB7”), the system also broadcasts system messages. See the following

figure.

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

SRNC

System information broadcast

UE NodeB

system information broadcast

scheduler

DRNC

Paging（PAGING TYPE1）

SYSTEM INFORMATION CHANGE INDICATIONRRC RRC

Condition：informing UE of CELL_FACH that

system information changed

Condition：informing UE of idle, CELL_PCH、URA_PCH

that system information changed

SYSTEM INFORMATION UPDATE REQUEST

SYSTEM INFORMATION UPDATE RESPONSE



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:

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 3-1 Scheduling levels of the SIBS

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

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.

(for more details on the paging process, refer to the section “3.4 Paging”)

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.

3.1.2 Information Sent by SIBs

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

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 ret ransmit event

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

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 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 i f 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 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. T317 is fixed as infinity, which is the only value according to 25.331.

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.

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

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

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


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


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

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



3.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 c ommon

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

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



3.1.2.5 SIB7

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

calculated as follows:

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

3.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). For more details about the parameters broadcasted in

SIB11, refer to the FD “ZTE UMTS Idle Mode and Common channel behavior”.

3.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. For more details, refer to ZTE UMTS Location Service

Feature Description.



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



NMCC Mobile Country Code of Neighbouring Cell

NMNC Mobile Network Code of Neighbouring Cell

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

3.1.2.10 SIB19

The SIB19 contains Inter-RAT frequency and priority information to be used in

the cell. The frequency and priority information is related to UTRAN or GSM or

E-UTRAN. If the parameter “Absolute Priority Reselection Criteria Switch” is set as “1”,

SIB19 can be broadcast to UE; if If the parameter “Absolute Priority Reselection Criteria

Switch” is set as “0”, RNC will not broadcast SIB19.

Table 3-8 Absolute Priority Reselection Criteria Switch




AbsPriReselSwch Absolute Priority Reselection Criteria Switch

3.2 DSAR and Cell Bar Access

3.2.1 Overview of DSAR

RNC can exercise control over the access of UEs in case of emergencies (for example,

large-scale natural disasters or high-density gatherings. The CN (CS/PS domain)

resources may be used up before the RNC congestion) to avoid further consumption of

the CN resources.

Each UE will be assigned with an Access Class (AC) which is written into the USIM by

the carrier. An AC ranges between 0 and 15. 0–9: for common users; 11–15: for

emergency service units (for example, fire alarm and first aid); 10: for emergency calls.

The DSAR function bars the CS/PS access of UEs of some ACs for a specific PLMN in

the cell and broadcasts specific access restriction information through SIB3.

3.2.1.1 Enable the DSAR

The DSAR function in CS/PS domain on each PLMN is enabled and disabled by setting

the DSAR function switch (CsDsarSw or PsDsarSwh) in relation to the PLMN in a cell. If

this cell supports several PLMNs, the DSAR function switch of these PLMNs needs to be

separately set.

RNC take different act according to configuration of The DSAR function switch

(CsDsarSw or PsDsarSwh),

If the DSAR function switch is set to “RNC Controls Dynamically CS Domain DSAR

(According to Load of Iu or Accessibility of Iu) ”/“RNC Controls Dynamically PS

Domain DSAR (According to Load of Iu or Accessibility of Iu)” (CsDsarSw or

PsDsarSwh =3):

Upon receiving the Overload message from CN indicating CS/PS overload or

discovering that CN is unreachable (for example, RNC receives a Reset

message from CN, or the office direction or subsystem of CN is unavailable),



RNC enables the DSAR function in the domain in relation to the PLMN.

Note: When Iu-Flex mode is adopted, the DSAR function of related domain is

enabled only when the CS or PS domain of all lu interfaces is overloaded or

unreachable.

Upon receiving the Overload message from CN indicating that the CS/PS

domain of lu interface is not loaded or CN is reachable, RNC disables the

DSAR function of the domain.

If the DSAR function switch is set to “RNC Controls Dynamically CS Domain DSAR

(According to Accessibility of Iu))” /” RNC Controls Dynamically PS Domain DSAR

(According to Accessibility of Iu)”(CsDsarSw or PsDsarSwh =2):

RNC detect the office direction or subsystem of CN is unavailable, RNC

enables the DSAR function in the domain in relation to the PLMN.


enabled only when the CS or PS domain of all lu interfaces unreachable.

RNC detect CN is reachable, RNC disables the DSAR function of the domain.

If the DSAR function switch is set to “Switch On CS Domain DSAR by OMCR”

/“Switch On PS Domain DSAR by OMCR ”(CsDsarSw or PsDsarSwh =1), RNC

enables the DSAR function directly.

3.2.1.2 Determine the Barred AC

After the DSAR function is enabled, RNC determines the barred AC in the following two

ways:

Polling mode: When the “DSAR polling/non-polling” switch is enabled

(CSDsarPollingSwh or PSDsarPollingSwh=1), RNC periodically bars the access of

some ACs in polling mode. RNC sets the number of ACs barred from access to

CS/PS domain in each period based on the parameters CSBarAcNum and

PSBarAcNum. RNC selects the AC barred list by adopting the following method:

i When the DSAR function is enabled, RNC starts the counter CSDsarCounter or



PSDsarCounter and sets its initial value to 0; if the counter

CSDsarCouter/PSDsarCounter is already started (in the case of changeover

between the two modes "OMCR enables DSAR" and “RNC dynamically

enables DSAR”), RNC continues the counting based on its current value.

ii At the end of each polling period (set through the parameter BarInterval), the

counter value increments: CSDsarCounter=CSDsarCounte r + CsBarAcNum

(CsBarAcNum: refers to the number of ACs barred from access to the CS domain in

each period. This parameter can be set through the background)

PSDsarCounterPS=PSDsarCounterPS + PsBarAcNum

(PsBarAcNum: refers to the number of ACs barred from access to the PS domain in

each period. This parameter can be set through the background)

iii The start number of the AC barred from access to the CS domain:

CSDsarCounter mod 10; the end number of the AC barred from access to the

CS domain: (CSDsarCounter + CsBarAcNum - 1) mod 10.

The start number of the AC barred from access to the PS domain: PSDsarCounter

mod 10; the end number of the AC barred from access to the PS domain:

(PSDsarCounter + PsBarAcNum - 1) mod 10.

For example, if CSBarAcNum is 2, PSBarAcNum is 3 and BarInterval (Polling period) is

60, then the percentage of UEs barred from access to the CS domain in each period is

20%, and that barred from access to the PS domain is 30%, as shown in the following

figure:



Figure 3-2 Example of DSAR polling mode

x ooxoAC9

x ooxoAC8

ox oxoAC7

x ooxoAC6

oxoxoAC5

oxoxoAC4

oxox oAC3

oxoxoAC2

oxox oAC1

oxox oAC0

10987654321

x ooxoAC9

x ooxoAC8

ox oxoAC7

x ooxoAC6

oxoxoAC5

oxoxoAC4

oxox oAC3

oxoxoAC2

oxox oAC1

oxox oAC0

10987654321

Timer (minute)Timer (minute)

x CS Domain

O PS Domain

Non-polling mode: When the “DSAR polling/non-polling” switch is disabled

(CSDsarPollingSwh or PSDsarPollingSwh=0), the non-polling mode is adopted and

the ACs barred from access to the PS/CS domain are determined directly based on

the background configuration. RNC bars partial ACs from accessing the CS or PS

domain based on the parameters CsACBarredOmcr and PsACBarredOmc on

related PLMN.

3.2.1.3 Fill Broadcast Messages

RNC fills related cells in SIB3 based on the domain requiring access restriction and the

ACs.

When enabling the DSAR function only for a specified PLMN, RNC fills: Domain

Specific Access Restriction Parameters For PLMN Of MIB/CS Domain Specific

Access Restriction/ PS Domain Specific Access Restriction/Domain Specific

Access Class Barred List.

When enabling the DSAR function for several PLMNs, RNC respectively fill the

following based on the barred PLMN number: Domain Specific Access Restriction

Parameters For OperatorN(N=1~5)/CS Domain Specific Access Restriction/ PS

Domain Specific Access Restriction/ Domain Specific Access Class Barred List.

If the background parameter “Bar switch of paging response and location



registration (PagingLocaBarSwh)” is set to “UE-initiated paging response and

location registration barred”, that is, the paging of CS/PS domain needs to be

barred, then RNC fills the following based on the determined domain and AC (for

details, see 1.1.1.2 Determine the Barred AC): Paging Permission with Access

Control Parameters For PLMN Of MIB or Paging Permission with Access Control

Parameters For OperatorN(N=1~5)/Paging Response Restriction Indication. And

RNC fills Paging Permission with Access Control Parameters For PLMN of MIB or

Paging Permission with Access Control Parameters For OperatorN (N=1–5)

/Location/Registration Restriction Indicator and Location/Registration.

When filling Location/Registration specific information: If either CS or PS

domain needs to be barred, then RNC fills the information based on the AC of

the specific domain; if both CS and PS domains need to be barred, then RNC

fills the information based on the AC of the PS and CS domains.

3.2.1.4 Disable the DSAR

RNC disables the DSAR in any of the following cases:

When CSDsarSwh/PSDsarSwh is set to “Switch Off CS Domain DSAR by OMCR”

/”Switch Off PS Domain DSAR by OMCR” (CsDsarSw or PsDsarSwh =0), RNC

disables the DSAR function of the CS/PS domain on the PLMN and stops and

clears the started counter.

When CSDsarSwh/PSDsarSwh is set to “RNC dynamically enables and disables

DSAR”(e.g. RNC Controls Dynamically CS Domain DSAR (According to

Accessibility of Iu)/ RNC Controls Dynamically PS Domain DSAR (According to

Accessibility of Iu)/ RNC Controls Dynamically CS Domain DSAR (According to

Load of Iu or Accessibility of Iu)/ RNC Controls Dynamically PS Domain DSAR

(According to Load of Iu or Accessibility of Iu) ) and lu interface recovers from

overload, RNC disables the DSAR function of the CS/PS domain on the PLMN,

clears related cells in the SIB3 message and stops and clears the started counter.


disabled only when the CS or PS domain of all lu interfaces recovers from

overload or lu interface is restored.



When the value of CSDsarSwh/PSDsarSwh changes from “OMCR enables DSAR”

into “RNC dynamically enables and disables DSAR”, current CN is not overloaded

and lu interface is reachable, RNC disables the DSAR function of the CS/PS

domain on the PLMN, clears related cells in the SIB3 message and stops and

clears the started counter.


disabled only when the CS or PS domain of all lu interfaces recovers from

overload or lu interface is restored.

3.2.2 Cell Bar Access (CBA)

With the Cell Bar Access (CBA) function, RNC can bar the UE access of some ACs so as

to ease the cell load. The implementation procedure of the CBA function is quite similar

to that of the DSAR function.

RNC enables and disables the CBA function by setting the cell parameter CellBarAcSwh.

3.2.2.1 Enable the CBA

When CellBarAcSwh is set to “OMCR enables CBA” (CellBarAcSwh=1), RNC

enables the CBA function.

When CellBarAcSwh is set to “RNC dynamically enables and disables CBA”

(CellBarAcSwh=2), RNC judges the uplink load based on the TCP from NodeB as

well as the background parameter “Uplink Overload Threshold” (UlOverLd,for the

detail of this parameter’s configuration, please refer to “ZTE UMTS Overload

Control Feature Description U9.2”)and enables the CBA if the uplink is overloaded.

3.2.2.2 Determine the Barred AC

If CellBarPollingSwh is set to “Polling Mode” (CellBarPollingSwh =1), RNC sets the

number of ACs barred from cell access in each period based on the background

parameter CellBarAcNum. RNC selects the AC barred list by adopting the following

method:

RNC starts the counter CellBarCounter and sets its initial value to 0; if the



counter CellBarCounter is already started (in the case of changeover between

the two modes "OMCR enables CBA" and “RNC dynamically enables CBA”),

RNC continues the counting based on its current value.

At the end of each polling period (set through the parameter BarInterval),

CellBarCounter = CellBarCounter + CellBarAcNum

The start number of the AC barred from cell access: CellBarCounter mod 10;

the end number of the AC barred from cell access: (CellBarCounter +

CellBarAcNum - 1) mod 10.

If the background parameter CellBarPollingSwh is set to “Non-Polling Mode”

(CellBarPollingSwh =0), RNC selects the ACs barred from cell access based on the

value of the background parameter ACBarredOmcr. The UEs in the barred AC list

are also barred from response to the paging of CS or PS domain.

RNC fills the Cell Access Restriction/Access Class Barred list in the SIB3 message

based on the specified barred ACs.

3.2.2.3 Disable the CBA

RNC disables the CBA function in any of the following cases:

When CellBarAcSwh is set to “OMCR disables CBA” (CellBarAcSwh=0), RNC

disables the CBA function and stops and clears the started counter.

When CellBarAcSwh is set to “RNC dynamically enables and disables CBA”

(CellBarAcSwh=2), and the uplink load of current cell changes from “Overloaded”

into “Light Load”, RNC disables the CBA, clears contents in the Cell Access

Restriction/Access Class Barred list of the SIB3 message and stops and clears the

started counter.

When the value of CellBarAcSwh changes from “OMCR enables CBA” into “RNC

dynamically enables and disables CBA” and the uplink of current cell is not

overloaded, RNC disables the CBA function, clears contents in the Cell Access

Restriction/Access Class Barred list of the SIB3 message and stops and clears the

started counter.



3.3 RRC Connection Setup and Release

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

Figure 3-3 RRC connection establishment flow

SourceNode B

UE

RRCRRC CONNECTION REQUEST

[CCCH]

TargetNode B

DriftRNC

SourceRNC

RRC

RRCRRC CONNECTION SETUP

[CCCH]RRC

RRCRRC CONNECTION SETUP COMPLETE

[DCCH]RRC

Condition：setup RRC connection on DCH

RL Set up

RRCRRC CONNECTION SETUP

[CCCH]RRC

RRCRRC CONNECTION SETUP COMPLETE

[DCCH]RRC

Condition：setup RRC connection on FACH

Transport channel selection

Condition：RRC connection reject

RRCRRC CONNECTION REJET

[CCCH]RRC

Condition：RL setup successful

Condition：RL setup failed

Condition：expiration of waiting RRC CONNECTION COMPLETE

RL Delete

RRC CONNECTION REJET[CCCH]

RRCRRC

Load balance of RRC



3.3.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. For details on the inter-frequency load balance algorithm, refer to

ZTE UMTS Load Balance Feature Description.

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.



3.3.1.2 Establishing an RRC Connection over a Common 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 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.

3.3.2 Handling Abnormality in the RRC Connection Setup

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



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

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

shows the RRC connection release flow.



Figure 3-4 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).

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

SourceNode B

UE

RRCRRC CONNECTION RELEASE[DCCH（UM RLC RB1）]

TargetNode B

DriftRNC

SourceRNC

RRC

RRCRRC CONNECTION RELEASE COMPLETE

[DCCH（UM RLC RB1）]RRC

Condition：RRC connection release on DCH

RL Delete

RRCRRC CONNECTION RELEASE

[CCCH或DCCH（AM RLC RB2）]RRC

RRCRRC CONNECTION RELEASE COMPLETE

[CCCH或DCCH（AM RLC RB2）]RRC

Condition：RRC connection release on FACH



sends the RRC CONNECTION RELEASE COMPLETE message for once.

The RNC releases the radio link from the Iub interface (for more details, refer to the

section “Releasing the Iub Interface Radio Link”).

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

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

3.4 RRC Connection Redirection

3.4.1 Redirection for Load Reduction

This function support that RNC can reject a RRC connection setup request because of

overload or congestion .



When receiving a RRC CONNECTION REQUEST which the establishments cause is not

Emergency call, RNC check whether system is overloaded or congestion.

RCP Overload

The system queries the RCP CPU utilization rate every 2s, the CPU utilization

rate for load control is the average value of the continuous eight times. When

the CPU utilization rate exceeds 80%, the RCP state is identified as congested.

The system then sets the service admission proportion (R) to 0.1 and then

starts restricting service admission according to the proportion R.

If the CPU utilization rate is still higher than 80% in the next continuous ten

seconds from the beginning of congestion, the system sets R to 0.01. If the

CPU utilization rate is still higher than 80% in the next continuous twenty

seconds from the beginning of congestion, the system sets R to zero.

If the system detects that the CPU utilization rate is lowered to 75% in a cycle,

the system sets R to 1 and then cancels the restriction on service admission.

The RCP is returned from congested to normal.

When receiving a RRC Connection request, if R is less than 1, RNC generate

a random number by random function. RNC will reject this RRC connection

request if the random number is greater than the proportion R.

CN overload

RNC received overload message from CN

Without Iu Flex or Network sharing(i.e. the RNC connect with only one MSC

and one SGSN)

The RNC permit to reduce system load by rejecting RRC connection when CN

overload happens

If these three terms are all fulfilled, RNC will generate a random number by

random function. RNC will reject this RRC connection request if the random is

less than or equals the 30%.

Radio Resource Congestion



RRC Connection failed to establish because of Radio Resource Congestion

If “Switch of RRC Redirection Triggered by Radio Resource Congestion” is set

as “on”, RNC reject this RRC Connection Request.

When CN overload or RNC overload or Congestion happens, RNC will send message

“RRC CONNECTION REJECT” to UE , reject this RRC connection to reduce load on Uu

interface. In the message “RC CONNECTION REJECT”, RNC will fill the information of

inter-frequency cells or Inter-RAT in the IE “Redirection Information” to help UE to access

other carriers or GSM system.

The RNC will fill IE “Redirection Information” according the parameter “PriRedirectRat”

configured on OMC:

If the value of “PriRedirectRat” is 0 which inform system don’t provide related

information, RNC won’t fill IE “Redirection Information”;

If the value of “PriRedirectRat” is 1 which inform system Prior to Inter-Frequency,

secondly to Inter-RAT (Prior to GSM Cell, RNC will fill IE” Redirection Information”

with the information of a cell which satisfy the following conditions:

The cell coverage the area which is same with or including serving cell’s, and

the cell doesn’t belong to the RNC’s inter -frequency adjacent cell.( remark 1)

The frequency of the cell is different with all the inter -frequency adjacent cells

of the current cell

If there’re more than one cells satisfied the above conditions, RNC will prefer to select a

cell which has the same PLMN ID with the UE among these cells.

If there’s not any cell satisfied the above conditions, RNC will check if there’s any

inter-RAT adjacent cell satisfied the related conditions.

If the value of “PriRedirectRat” is 2 which inform system will Prior to Inter-Frequency,

Secondly to Inter-RAT (PS prior to E-UTRA, CS Prior to GSM), RNC will obtain the

cells satisfied the following conditions:

The cell coverage the area which is same with or including serving cell’s, and

the cell doesn’t belong to the RNC’s inter -frequency adjacent cell.( remark 1)



The frequency of the cell is different with all the inter -frequency adjacent cells

of the current cell

The GSM cells coverage the area which is same with or including serving cell’s

in case of CS service.

If there’re GSM cells satisfied the above condit ions, RNC will fill the BCCH ARFCN,

frequency information of the GSM cells in IE” Redirection Information”, and the number

of the GSM cells won’t over 32.

If there’re E-TRA cells satisfied the redirection conditions, RNC will fill the Redirection

Information IE with E-UTRAN frequency info, which include: DL Carrier frequency,

Blacklisted cells per freq list, Physical Cell identity.

If the value of “PriRedirectRat ” is 3 which inform system will Prior to Inter-RAT (Prior

to GSM), Secondly to Inter-Frequency, RNC will obtain the cells satisfied the

following conditions:

The GSM cells coverage the area which is same with or including serving

cell’s.

the cell doesn’t belong to the RNC’s inter -frequency adjacent cell.

The frequency of the cell is different with all the inter-frequency adjacent cells of the

current cell

If the value of “PriRedirectRat ” is 4 which inform system will Prior to Inter-RAT (PS

prior to E-UTRA, CS Prior to GSM), Secondly to Inter-Frequency, RNC will obtain

the cells satisfied the following conditions:

The GSM cells coverage the area which is same with or including serving cell’s

in case of CS service.

The E-UTRA cells coverage the area which is same with or including serving

cell’s in case of PS service.

the cell doesn’t belong to the RNC’s inter-frequency adjacent cell.

RNC support both E-UTRA FDD cells and E-UTRA TDD cells.



The parameter EutranCellType is the type of the E -UTRA cell. The value 0 means

EUTRAN FDD; the value of 1 menas EUTRAN TDD.

If the Pre-redirection info IE is included in the RRC CONNETION REQUEST, if value of

the Support of E-UTRA FDD is TRUE, which means the UE support E-UTRA FDD

frequency; if value of the Support of E-UTRA TDD is TRUE, which means the UE support

E-UTRA TDD frequency.

If there’re E-TRA cells satisfied the redirection conditions, and there are E-UTRA FDD

adjacent cells, and the UE support only the E-UTRA FDD frequency, then RNC can

redirect the UE to the E-UTRA FDD cells.

If there’re E-TRA cells satisfied the redirection conditions, and there are E-UTRA TDD

adjacent cells, and the UE support only the E-UTRA TDD frequency, then RNC can

redirect the UE to the E-UTRA TDD cells.

If there’re E-TRA cells satisfied the redirection conditions, and there are bothe E-UTRA

FDD adjacent cells and E-UTRA TDD adjacent cells, and the UE support both the

E-UTRA FDD frequency and E-UTRA TDD frequency, then RNC can redirect the UE to

the E-UTRA FDD cells and E-UTRA TDD cells randomly.

The frequency of the cell is different with all the inter -frequency adjacent cells of the

current cellIf there’s not any cell satisfied the above conditions, RNC will check if there’s

any inter-frequency adjacent cell satisfied the related conditions.

If there’s neither inter-frequency cell nor inter-RAT cell satisfied the related conditions,

RNC won’t fill IE” Redirection Information”.

Remark 1: the purpose of RRC connection redirection is reduce the RNC’s load, hence

the frequency information filled in IE” Redirection Information” doesn’t belong to the

current RNC.

Remark 2: When RRC CONNECTION REJECT message is sent to UE for load reduction,

the IE “Wait Time” in the message is set as 15 second.

3.4.2 Redirection for Emergency Call

At the earlier stage of 3G network deployment, if the operator has a mature GSM system



which can provide the location service with higher precision than the UMTS system, RNC

can redirect the Emergency call to the GSM system by this function. The system can

permit the Emergency call to be redirected to GSM or not by the parameter

EmgCallRdtSwitch (0: close the function, 1: open the function).

When UE generate RRC connection request, RNC will check the following conditions:

Value of IE “Establishment cause” in message RRC Connection Request is

“Emergency Call”

Value of parameter EmgCallRdtSwitch is 1

There are GSM cells coverageing the area which is same with or including serving

cell’s.

If the above conditions are satisfied, RNC will reject the RRC connection request, and fill

the related IEs in message “RRC Connection Reject”:

(1) Rejection cause=unspecified

(2) Wait time=2s

(3) Redirection Information: the value of sub-IE Inter-RAT info is GSM. RNC won’t fill

the detailed information of GSM adjacent cells, so that UE can select a certain GSM cell.

By this way, the success ratio of accessing to GSM system will improve, and the call

delay will reduce.



3.5 NAS Message Transfer

3.5.1 NAS Message Forwarding Flow

Figure 3-5 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 (for more details, refer to the

section "Establishing 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

SourceNode B

UE

RRCINITIAL DIRECT TRANSFER[DCCH（AM RLC RB3）]

TargetNode B

DriftRNC

SourceRNC

RRC

SCCP Link set up

RANAP DIRECT TRANSFER RANAP

CN

Precondition：RRC set up success

Initial direct transper

message

Uplink direct transper

Downlink direct

transper

Condition：without Iu signaling connection

Condition：with Iu signaling connection

RRCUPLINK DIRECT TRANSFER[DCCH（AM RLC RB3/RB4）]

RRC


RRCDOWNLINK DIRECT TRANSFER[DCCH（AM RLC RB3/RB4）]

RRC




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

transmits the DOWNLINK DIRECT TRANSFER message to the UE.

3.5.2 Setting up and Releasing the Iu Interface Connection

3.5.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 Figure 3-6.

Figure 3-6 Setting up the Iu interface connection

After the RRC connection setup, the UE sends the initial message to the RNC (for details,

refer to the section “NAS Message Transfer”). 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. For more details, refer to ZTE UMTS IU

Flex Feature Description.

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

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



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.

3.5.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 3-7 UE in DCH state releases the Iu interface connection

UE CNRNC

Iu Release Command

Iu CS service bearer release

Iu PS service bearer release

Node B

Iu Release Complete

Iu signaling bearer release

RRC connection release

RL release



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 (refer to the section “Releasing the Iu Interface Radio Links”).

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

service.

CS+PS domain services are provided concurrently.

Figure 3-8 Release the service of one domain



The RNC reconfigures the radio link (for more details, refer to the section “Reconfiguring

the Iub Interface 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.

UE CNRNC

Iu Release Command

Iu CS or PS service bearer release

Node B

Signaling connection release

Iu Release Complete

RL reconfigure

RB release




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 3-9 The UE in FACH state releases the Iu interface connection



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

UE CNRNC

Iu Release Command



Node B

Iu Release Complete



UE CNRNC

Iu Release Command



Node B

Iu Release Complete



Paging type 1

Cell update



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

Figure 3-11 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

Node B

Iu Release Complete



RL release

Condition： UE in DCH



Figure 3-12 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

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.

UE CNRNC

Iu Release Command

Iu Release Complete

Iu Release Request

Signaling Connection

Release Indication

Node B


Signaling Connection Release

Condition：Signaling connection release originated by UE



3.6 Paging

3.6.1 Paging Flow

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

Figure 3-13 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.

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



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

the DRNC to page the UE.

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

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

3.6.4 Virtual Location Area Paging

When UE is at the boundary of Location Area, sometimes the Location Update

Procedure is not finished in time, UE is already in the NEW LAC but CN Know the UE

OLD LAC, if a paging to the UE is needed, CN will send PAGING to the OLD LAC, then

the paging will fail.

ZTE RNC Int roduce Virtual Location Area Paging. RNC will send PAGING to the cells

which belong to another LAC neighbor to Current LAC, and then improve the paging

success rate.

A cell can be configured maximum two virtual LACs. If a paging is sent from CN to a LAC,

RNC will also match the virtual LACs, if the LAC of PAGING match virtual LACs of some

cell, these cells will send the paging to UE even though the LAC of CELL is not the LAC

of PAING. If the boundary of TWO LACs is at the boundary of Two RNCs, IUR PAING is

sent if the adjacent RNC support Virtual LAC paging.

In order to decrease paging load, RNC adopt Virtual LAC paging only for repeated CS

Voice Paging.



3.7 Security Mode Control

In the 3G system, the safety mechanism is applied in multiple layers:

Network access security: Provide safe access to the 3G network and prevent

attacks in the radio link.

Network domain security: Provide security protection for the signaling data

exchanged between nodes in the domain providing services and prevent attacks

against the radio network.

User domain security: Provide secure access measures for UEs.

Application domain security: Provide safe information exchange for the users and

the service applications between the domains providing services.

Visibility and configurability of security: Enable the user to know whether the

security measure has been implemented. Whether the user uses and provides the

services depend on the security attributes.

The encryption and integrity protection belong to the security mechanism of the network

access security.

3.7.1 Security Mode Control Flow

The security mode control flow specifies the algorithms and parameters of the encryption

and integrity protection between the UE and the RNC. The CN sends the security mode

control message to the RNC to specify the algorithms and parameters of integrity check

and encryption. If the RNC finishes the process at the radio interface, the RNC sends the

SECURITY MODE COMPLETE message to the CN. Figure 3-14 shows the process of

RAN resource allocation.



Figure 3-14 Security mode control flow

As shown in the above figure, the RNC receives the SECURITY MODE COMMAND

message from the CN. The message contains the Integrity Protection Information and

Encryption Information, or the Integrity Protection Information only. The Integrity

Protection Information contains two parts: integrity protection algorithm and integrity

protection key commended by CN. The integrity protection currently supports two

algorithms: UIA1 and UIA2. The Encryption Information also contains two parts:

encryption algorithm and encryption key commended by CN. There are three types o f

encryption algorithm: no encryption, UEA1 and UEA2.

Thereinto, UEA1 and UIA1 is the security algorithm in 3GPP phase 1, and UEA2, UIA2

are introduced in 3GPP R7. Compared with the security algorithms of phase 1, UEA2

and UIA2 support higher rate and efficiency, better security performance. ZTE UTRAN

supports all of these security algorithms..

The control procedure of security mode is as following:

When RNC receive SECURITY MODE COMMAND message from CN, RNC

selects security algorithms according to:

Encryption algorithm selection:

UE CNSource

RNC

RANAPSecurity Mode Command【EP】RANAP

RANAPSecurity Mode Reject【EP】RANAP

Security Mode Command【EP】RRC RRC

Condition ：arithmetic is not supported

Security Mode Complete【EP】RRC RRC

Security Mode Failure【EP】RRC RRC

RANAPSecurity Mode Complete【EP】RANAP

RANAPSecurity Mode Reject【EP】RANAP

Condition ：arithmetic is supported



i The RNC judges whether it supports the encryption algorithm configured in the

CN. If not, the RNC returns the SECURITY MODE REJECT message to CN.

The encryption algorithm (EncryAlg) and integrity protection algorithm

(IntegrityAlg) supported by the RNC can be configured in the OMCR.

ii If there’s intersection between the encryption algorithms supported by CN and

RNC, RNC selects the algorithms supported by RNC and CN, and holds the

priority queue of the algorithms commended by CN.

iii RNC judges whether the UE supports the algorithm. If the RNC lacks the

capability of the UE, it queries the capability of the UE. For details, refer to the

section “Querying the UE Capability”.

iv RNC judges if this is the first encryption algorithm selection of the UE in this

RNC:

If it is the first time, RNC selects the first algorithm that UE supports from

the encryption algorithm intersection supported by CN and RNC. If the

selection result is UEA0 or there’s no intersection in CN, RNC and UE,

RNC select “on encryption”.

If it isn’t the first time, RNC selects the encryption algorithm used for the

UE.

Integrity protection algorithm selection:

1 The RNC judges whether it supports the integrity protection algorithm configured in

the CN. If not, the RNC returns the SECURITY MODE REJECT message to CN.

The encryption algorithm (EncryAlg) and integrity protection algorithm (IntegrityAlg)

supported by the RNC can be configured in the OMCR.

2 If there’s intersection between the algorithms supported by CN and RNC, RNC

selects the algorithms supported by RNC and CN, and holds the priority queue of

the algorithms commended by CN.

3 RNC judges whether the UE supports the algorithm. If the RNC lacks the capability

of the UE, it queries the capability of the UE. For details, refer to the section

“Querying the UE Capability”.



4 RNC judges whether the UE set up connection in other domain:

If the UE has connection in other domain, RNC selects the integrity

algorithm that is used for the UE in that dom ain;

If the UE has no connection in other domain, RNC selects the first

algorithm that UE supports from the encryption algorithm intersection

supported by CN and RNC.

If the RNC and the UE support the encryption algorithm and integrity protection

algorithm configured in the CN, the RNC suspends the SRB entities except RB0

and RB2.After the RNC sends a SECURITY MODE COMMAND message to the UE

through SRB2, it then provides integrity protection for the downlink data carried

through SRB2.

After the UE receives an encryption command, if processing fails, it returns the

SECURITY COMMAND FAILURE message to the RNC. After the RNC receives the

failure message, it recovers the suspended SRBs and sends the SECURITY

COMMAND REJECT message to the CN.

After the UE receives the encryption command, if processing succeeds, it returns

the SECURITY COMMAND COMPLETE message to the RNC. After the RNC

receives the SECURITY COMMAND COMPLETE message, it recovers the

suspended SRBs and implements integrity protection and encryption for all uplink

and downlink signaling of all SRBs. The RNC returns the SECURITY COMMAND

COMPLETE message to the CN.

After the security mode is terminated, the encryption and integrity protection for the SRB

are also terminated accordingly. The RNC implements encryption and integrity protection

for the signaling data carried in the SRBs.

The UE stores the encryption parameter and encryption algorithm obtained during the

safety mode process. After the data radio bearer (DRB) is set up, the UE encrypts the

DRBs using the encryption parameters of the CS domain or PS domain.



3.7.1.1 Querying the UE Capability

The RNC sends the UE CAPABILITY ENQUIRY message to the UE to query the UE

capability information. After receiving the message, the UE sends the UE CAPABILITY

INFORMATION message with the UE capability. The RNC finally sends the UE

CAPABILITY INFORMATION CONFIRM message as confirmation.

Figure 3-15 Querying the UE capability

As shown in the above figure, the RNC queries the UE capability on the following three

occasions:

When the RNC needs to know the UE capability, it creates the UE CAPABILITY

ENQUIRY message and sends the message to the UE.

If the UE is in the connected mode and its capability information changes, the UE

sends the UE CAPABILITY INFORMATION message to the UE.

The RNC receives the CAPABILITY INFORMATION message from the UE. The

information in the message includes UE protocol version (R99/R4/R5), HS-PDSCH

supported or not, supporting SCCPCH, DPCH, and HS-PDSCH or not, downlink

capability when the HS-DSCH is configured concurrently, physical layer of the SH-DSCH,

and whether it is allowed to estimate the capability of the HS-PDSCH and HS-SCCH

according to the pilot frequency.

After the RNC stores the UE capability information, it creates the UE CAPABILITY

INFORMATION CONFIRM message and sends the message to the UE.

If the RNC has not received the CAPABILITY INFORMATION message from the UE for 5

seconds, it considers UE capability information query failed.

UESourceRNC

RRC UE Capability Information RRC

RRC UE Capability Enquiry RRC

RRC UE Capability Information Confirm RRC



3.7.2 Encryption Algorithm and Parameters

3.7.2.1 Authentication and Key Generation

The authentication is intended to verify the key used in the encryption and integrity

protection. Through various algorithms and random numbers, the keys that are

consistent between the UE (or MS) and the UTRAN are generated, including encryption

keys (CK) and integrity protection key (IK).

The VLR/SGSN initiates the authentication request to the HE/HLR. The HE/HLR

generates multiple authentication vectors. Through the authentication responses, the

HE/HLR brings these authentication vectors to the VLR/SGSN. The VLR/SGSN saves

the authentication vectors, selects a vector, and initiates an authentication request to the

UE (or MS). The UE (or MS) calculates the CK, IK, and return value RES according to

the parameters RAND and AUTN in the authentication request. The network compares

the return value RES from the UE(or MS) with the expected XRES and checks whether

they are the same. If yes, the authentication succeeds. The network also selects the CK

and IK that are the same as the UE (or MS).

3.7.2.2 Encryption Algorithm and Parameters

The encryption is done in the RLC layer (AM or IM mode) or the MAC layer (TM mode).

Currently, the encryption algorithms of the Uu interfaces of the 3G system have three

types: UEA0, UEA1 and UEA2. UEA0 means that the data of the Uu interface is not

encrypted. UEA1 means that the KASUMI algorithm based encryption algorithm f8

should be adopted, and UEA2 means that the SNOW 3G algorithm based encryption

algorithm f8.

The parameters of encryption algorithm f8 include:

Encryption key CK

COUNT-C (it varies with time)

BEARER (bearer tag)

DIRECTION (direction indication)



LENGTH (block length required by the key stream)

Original code stream

According to these parameters, the encryption algorithm generates a key block of

specified length. The plain text can be encrypted into cipher text by adding encryption

key; the cipher text can decrypted into plain text by adding the same encryption key. The

following describes the encryption and decryption process.

Figure 3-16 Encryption and decryption process

The encryption related parameters can be obtained and configured as follows:

COUNT-C:

RB in AM mode: COUNT-C = HFN (20 bits)+ SN(12 bits);

RB in UM mode: COUNT-C = HFN (25 bits)+ SN(7 bits);

RB in TM mode: COUNT-C = HFN (24 bits) + CFN (8 bits);

At the time of COUNT-C initialization, HFN is the RLC hyper frame number (AM

mode or UM mode) or the MAC hyper frame number (TM mode), the value of HFN

increases once every SN period or every connection frame number (CFN) period.

The initial value of the HFN uses the first 20 bits of START to form the first 20 bits of

the initial COUNT-C, and the left bits are all 0s. The START value is sent by the UE

to the RNC through the uplink message (such as CELL UPDATE message) of the

PLAINTEXT

BLOCK

f8

COUNT-C DIRECTION

BEARER LENGTH

CK

KEYSTREAM

BLOCK

CIPHERTEXT

BLOCK

f8

COUNT-C DIRECTION

BEARER LENGTH

CK

KEYSTREAM

BLOCK

PLAINTEXT

BLOCK

发送端

UE 或 RNC

接收端

RNC 或 UE Sender：UE/RNC Receiver：RNC/UE



Uu interface. The RNC always stores the latest START provided by the UE. When a

frame is transmitted in the data transmission process, the value of the HFN

increases with the SN (or CFN). The value of COUNT-C generated in every

transmission event varies.

DIRECTION: It indicates the direction of the current encryption event. 0 represents

uplink; 1 represents downlink.

CK: encryption key. It is generated in the authentication process.

BEARER: bearer tagThe tag corresponds to each RB. BEARER = RB ID - 1

LENGTH: It indicates the length of the key stream block.

DATA: It specifies the data to be encrypted or decrypted.

3.7.3 Integrity Protection Algorithm and Parameters

The integrity protection is implemented in the RRC layer. The integrity protection function

supports the UIA1 and UIA2 algorithms, thereinto UIA1 means that the KASUMI based

encryption algorithm f9, and UIA2 means that the SNOW 3G based encryption

algorithm f9. F9 algotithm is as shown in the figure blow.

Figure 3-17 Using the f9 algorithm for integrity protection

The input parameters of the algorithm include IK (integrity protection key), COUNT-I

(integrity SN), FRESH (random number generated in the network), DIRECTOR (direction

bit), and MESSAGE (signaling message). Based on these input parameters, the transmit

ting end calculates the authentication code MAC-I using f9 algorithm. MAC-I is added to

f 9

COUNT-I DIRECTION

MESSAGE FRESH

IK

MAC -I

f 9

COUNT-I DIRECTION

MESSAGE FRESH

IK

XMAC -I

发送端 UE 或 RNC

接受端 RNC 或 UE

Sender：UE/RNC Receiver：RNC/UE



the message and is sent to the receiving end. After receiving the message, the receiving

end calculates XMAC-I in a similar way and compares it with the received MAC-I to

perform integrity check.

The following describes the parameters of the algorithm:

Integrity SN: COUNT-I = HFN(28 bits) + SN (4 bits)

Similar to the COUNT-C in the encryption algorithm, the initial value of HFN consists of

the first 20 bits of the parameter START and all 0s in the left bits. The HFN increases

once every RRC SN period.

The SN is a 4-bit RRC-SN. The RRC-SN can be obtained from each RRC PDU.

IK: integrity key. It is obtained in the authentication process.

FRESH: The FRESH parameter prevents the users from using the signaling message

repeatedly. FRESH is a random number generated by the RNC. The FRESH varies with

each UE. In the security mode, the FRESH is sent to the UE.

DIRECTOR: direction bit. 0 represents the uplink; 1 represents the downlink.

3.8 RAB Force Queue

This function enables RNC to force AMR and CS64K to queue even if RNC does not

receive any queue information from CN or queuing is not allowed based on the

assignment information.

If the RAB assignment message (only including the setup and modification of a single

RAB) of AMR or 64kbps CS service and the RAB setup message of incoming relocation

from CN do not contain queuing information (that is, the “RAB ASSIGNMENT REQUEST”

message does not contain Allocation/Retention priority) or specify that the RAB does not

have the queuing capability (that is, “Queuing Allowed” carried in the “RAB

ASSIGNMENT REQUEST” message is 0 (queuing not allowed)), RNC will judge whether

the RAB has the queuing capability according to whether the ForcQueSwi is enabled or

not.



If ForcQueSwiAMR is enabled, the AMR service has the queuing capability and its

maximum queue time can be set with the parameter “TTrueQForced”. If

ForcQueSwiAMR is disabled, the AMR service cannot queue.

If ForcQueSwiCS64 is enabled, the CS64k service has the queuing capability and

its maximum queue time can be set with the parameter “TTrueQForced”. If

ForcQueSwiCS64 is disabled, the CS64k service cannot queue.

3.9 Radio Connection Monitor

If the RNC judges that the radio connection between a UE and a network is actually

interrupted due to poor quality of the UE radio connections with the RRC or other causes,

the RNC immediately releases all resources allocated to the UE, including RB resources

where services are distributed, RRC resources, and Iu interface connection.

The ZTE RAN supports monitoring the radio connections in the following modes:

The Node B monitors the RL status.

This mode is suitable to the UE in the DCH state. The Node B monitors the radio link

of the UE. Node B shall start timer T_RLFAILURE after receiving

NUMOUTSYNCIND consecutive out-of-sync indications. Node B shall stop and

reset timer T_RLFAILURE upon receiving successive NumInSyncInd in-sync

indications. If T_RLFAILURE expires, Node B shall trigger the RL Failure procedure

and indicate which radio link set is out-of-sync. ( For the detailed of the parameters’

configuration including NUMOUTSYNCIND, T_RLFAILURE, NumInSyncInd,

please refer to <ZTE UMTS Node B Management Feature Description U9.2>. )

Figure 3-18 Radio link failure

CRNC Node B

RADIO LINK FAILURE INDICATION



If the cause value in the RADIO LINK FAILURE INDICATION message indicates

that the radio link is unrecoverable or the radio link is recoverable but the RNC has

not received the message RADIO LINK RESTORE INDICATION within 10 seconds,

the RNC considers that the radio link of the UE is interrupted.

The RNC monitors the RLC connection status.

After the RRC connection is set up, if the RNC sends messages over the RLC layer

but has not received responses from the UE, the RNC retransmits the message. If

the retransmit event count reaches 15, the RLC layer reset. If the reset time reaches

6, the RNC considers that errors occur in the user plane.

The RNC monitors the RLC connections in the AM mode. The ZTE RNC adopts the

AM mode for the SRB. Through the function, the RNC can monitor all UEs in

connected mode.

The RNC monitors the CELL UPDATE message of the UE.

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

The value of the parameter AM_RLC error indication (RB2, RB3 or RB4) is true.

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

cause value in the message is radio link failure or RLC unrecoverable error,

when the RNC receives the cell update message indicating the mentioned errors

from the UE, the RNC considers that the radio connection is interrupted.

The RNC monitors the keeping alive duration of the UE.

If the RNC has not exchanged any message or data with the UE in the FACH or

PCH state within the period of T305 + 1 minute, it considers that the radio

connection of the UE is interrupted.

When the RNC detects the interruption in the radio connection of a UE through above

monitoring methods, it releases the RRC connection and radio resources and sends Iu

connection release request through the Iu interface to the CN, notifying the CN to release

the RAB resources.

3.10 Call Re-establishment

Call re-establishment is a procedure of re-establishing the radio link of a UE. When a link



is interrupted due to poor radio quality, if the UE in DCH state detects an RlC

Unrecoverable Error or RL FAILURE and the durations of all service re -establishment

timers (T314 and T315) are neither 0 nor in timeout state, the UE will switch to FACH

state and reports the Cell Update to UTRAN through a CCCH, expecting the UTRAN to

re-establish this link and reduce the call drop rate.

When detecting an out-of-sync condition on radio uplink or an RLC Unrecoverable Error,

the UTRAN can deactivate all the radio links of UE, thus driving the UE to trigger call

re-establishment to reduce the call drop rate.

Call re-establishment is a hard handoff, and its channel and cell selection principle is

similar to that of hard handoff. Call re-establishment may select the cell that reports

CELL UPDATE or other cells for the sake of load balance. The channel type adopted for

re-establishment may vary with cell type.

3.10.1 Processing of Call Re-establishment

When the radio link is interrupted due to poor link quality, the UE in the DCH state sends

a “Cell Update” message with a cause value to the RNC. The RNC then sets up a radio

connection to the UE. See the following figure.



Figure 3-19 Call re-establishment

As shown in the above figure, the UE in the DCH state sends the CELL UPDATE

message to the RNC. If the cause value is Radio link failure (for example, T313 timer

expires) or RLC unrecoverable error (for example, the uplink RB in the RLC layer is reset

due to repeated data retransmission) and the value of the parameter AM_RLC error

indication (RB2, RB3 or RB4) is FALSE, if the switch of Call Re-Establishment is opened,

the RNC initiates the setup of a radio connection to the UE.

Delete the RL connection of the UE: If the RL connection belongs to the local RNC,

delete the Iub Interface Radio Link. If the RL belongs to another RNC, it notifies the

DRNC to delete the radio link.(for more details, refer to the section “Releasing the Iub

Interface Radio Link” and the section “Releasing the Iur Interface Radio Link”.)

The RNC reconfigures the UE, reselects the channel, and re-configures the parameters

of the signaling and services according to the selected channel. The RNC re-sets up the

RL in Node B.

The RNC sends the CELL UPDATE CONFIRM message to the UE, providing information

NODEB RNCUE

Cell update

Reconfigure SRB on FACH

RL deletion request

RL deletion response

Reconfigure SRB and DRB

RL setup request

RL setup response

Cell update confirm （PhyCH info ，RB info）

Physical channel reconfiguration complete

RB reconfiguration complete

Condition: UE reconfigured Physical channel



on the physical channel and RB reconfiguration. To ensure that the UE correctly receives

the message, the RNC sends the message for three consecutive times, the RRC SN in

the three messages remains unchanged.

According to the information on the physical channel and RB parameters carried in the

CELL UPDATE CONFIRM message sent by the RNC, the UE reconfigures the physical

channel or RB parameters, and returns a message indicating the completion of physical

channel reconfiguration or RB reconfiguration.

3.10.2 Call Re-establishment Triggered By Network

RNC will initiates the cell update call re-establishment procedure to improve the call

completion rate and reduce the call drop rate, when RNC detected the Uu response

timeout or RL fail or RLC unrecover Error



Figure 3-20 Call re-establishment triggered by Network

Node BUE RNC

Set the timer 1 for response on Uu

Set the timer 1 for response on Uu

Timer 1 expiry

Set timer 2 for CELL UPDATE

Call re-establishment process

Exception handling

RL DEACTIVE

RB SETUP

CELL UPDATE

Condition: handover procedure

Condition: RNC receive cell update before timer 1 expiry

Condition: RNC doesn't receive any message on Uu befor timer 1 expiry

Condition: RNC doesn’t receive CELL UPDATE before timer 2 expiry

Condition: call re-establishment process is initialed

RL FAILCondition: RNC receive Radio link failure from NodeB

Set the timer 1 for RL restore from NodeB

DL RLC unrecover error detected

Condition: RNC detected “DL RLC unrecover error”

ACTIVE SET UPDATE/TRCH RECONFIGURATION/PHYCH

RECONFIGURATION

Condition: rb setup procedure

CELL UPDATE

1 RNC will start call re-establishment according to different case:

i. In the rb setup procedure, RNC sends a “Radio Bearer Setup” message to UE

and starts Timer1 to wait for response from UE, Timer1 value can be

configured by WaitRbCompTimer, default is 5s. Upon receiving the “Response”

message from UE, RNC will stop Timer1. If Timer1 expires, and the switch of

Call Re-Establishment is opened, the call re-establishment is triggered.

ii. In handover procedure, RNC send a “Active Set Update” (e.g. soft handover)

or “transport channel Reconfiguration” or “physical channel Reconfiguration”

message(e.g. hard handover with RB unchanged) to UE and starts Timer1 to



wait for response from Uu, Timer1 value for soft handover can be configured

by TWaitActSetUpCmp, default is 10s, Timer1 value for hard handover is set

5s. Upon receiving the “Response” message from UE, RNC will stop Timer1. If

Timer1 expires, and the switch of Call Re-Establishment is opened, the call

re-establishment is triggered.

iii. When RNC receive “Radio Link Failure Indication” message of all Radio Links

belong to a UE from NodeB, starts Timer1 to wait for Radio link Restore from

NodeB, Timer1 value can be configured by TWaitRlRestore, default is 3s.

Upon receiving the “Restore” message from NodeB, RNC will stop Timer1. If

Timer1 expires, and the switch of Call Re-Establishment is opened, the call

re-establishment is triggered.

iv. When “DL RLC unrecover error ” is detected by RNC, and the switch of Call

Re-Establishment is opened, the call re-establishment is triggered

immediately.

Note: (i)For rb setup procedure and soft-handover procedure, If the RNC

receive the CELL UPDATE before the Timer1 expires, the RNC trigger the call

re-establishment procedure and doesn’t sent RADIO LINK ACTIVATION

COMMAND message to the NODEB. For hard procedure, the call will be

released. (ii)If RNC is handling another RRC procedure, the call

re-establishment will not be triggered. (iii)when RNC receive CELL UPDATE, if

the condition of call re-establishment is not fulfilled, the UE will be dropped by

RNC.

2 if the call re-establishment is triggered:

If UE has CS service and T314 is set 0, or UE has PS service and T315 is set

0, RNC will directly release UE instead of call re-establishment. Otherwise, the

following procedure is ongoing.

RNC will send a “RADIO LINK ACTIVATION COMMAND” message to the

Node B, to which all radio links of the UE active set belong. Here “CHOICE

Delayed Activation Update” of the cell related to every radio link is set to

“Deactivate” in order to deactivate the radio link.



Upon receiving the “RADIO LINK ACTIVATION COMMAND” message, Node

B closes the downlink transmission on related link to drive UE to initiate the

Cell Update procedure as soon as possible.

After deactivating the radio links of UE, RNC sets Timer2 to wait for Cell

Update. Timer2 is set 10s.

After receiving the “CELL UPDATE” message from UE, RNC will stop Timer2 and

initiate the call re-establishment procedure. (For details, see Call Re-Establishment

Procedure.)

If Timer2 expires, ,RNC perform exception handling according to the triggered

cause(eg, RNC perform handover fail process or release call or rb setup fail

process)

3.11 Managing the Iub Interface Radio Link

3.11.1 Establishing the Iub Interface Radio Link

Creating a radio link

On the following two occasions, the system needs to set up radio links:

Establishing the RRC connection over the DCH

Establishing the RRC connection over the FACH; establishing the RAB over

the DCH, HS-DSCH, or E-DCH.

The RNC intending to establish a radio link first implements the radio link admission

control and code resources allocation;

The RNC sends the RADIO LINK SETUP REQUEST message carrying dedicated

channel configuration parameters to the control port of the Node B;

The RNC receives the RADIO LINK SETUP RESPONSE message from the control port

of the Node B;

The RNC establishes the user plane bearer over the dedicated transport channel and



shared transport channel (i f the bearer is used to carry the HSPA service) with the Node

B.The RNC establishes a transmission bearer with the Node B and synchronizes the

nodes and transport channels.

3.11.2 Reconfiguring the Iub Interface Radio Link

On the following occasions, the system needs to reconfigure radio links:

Establishing the RRC connection over the DCH; establishing the RAB over the

DCH, E-DCH, or HS-DSCH;

Establishing the RAB over the DCH, E-DCH, or HS-DSCH; reconfiguring the

RAB over the DCH, E-DCH, or HS-DSCH;

Provisioning the CS+PS service concurrently and releasing the service for the

first time

1 Prepare for the reconfiguration of the RL synchronization

After the RNC finishes the radio link admission control, code resource allocation,

and application for the dedicated channels, it sends the RADIO LINK

RECONFIGURATION PREPARE message to each Node B;

When the RNC applies for the channels for the services, if the admission control or

code resource allocation in a wires link fails, the radio link synchronization

reconfiguration preparation flow is terminated abnormally. If the channelization

codes are allocated, the RNC releases the downlink channelization codes of the

applied downlink channelization codes.

The RNC receives the RADIO LINK RECONFIGURATION READY messages from

each Node B.

If the RNC receives the RADIO LINK RECONFIGURATION FAILURE message

from a Node B, it means that the preparation for the reconfiguration of the Node B

radio link fails. The RNC sends the RADIO LINK RECONFIGURATION CANCEL

message to the Node Bs with successful radio link reconfiguration preparation.

If it is time out when the RNC waits for the radio link reconfiguration response from

the Node Bs, the radio link reconfiguration preparation fails. The RNC sends the

RADIO LINK RECONFIGURATION CANCEL message to the Node Bs with

successful reconfiguration or reconfiguration timeout.



If the setup of any transmission link fails, the radio link reconfiguration fails. The

RNC sends the RADIO LINK RECONFIGURATION CANCEL message to each

Node B. The RNC releases the newly-established user plane resources, links in the

transmission link, and downlink channelization code resources newly -applied for all

radio links.

2 Reconfigure RL synchronization

The RNC sends the RADIO LINK RECONFIGURATION CANCEL COMMIT

message to the related Node Bs. The RNC and Node Bs adopt the new

configuration data simultaneously.

3 Cancel RL synchronization reconfiguration

If the RNC judges that the radio link synchronization must be reconfigured, it sends

the RADIO LINK RECONFIGURATION CANCEL message to the related Node Bs.

The RNC cancels the new configuration and recovers the original configuration.

3.11.3 Releasing the Iub Interface Radio Link

The RNC sends the Radio Link Deletion Request message to the Node B, notifying the

Node B to delete the radio link. The RNC receive the radio link deletion response from

the Node B and releases the resources of the deleted radio link.

3.12 Managing the Iur Interface Radio Link

3.12.1 Reconfiguring the Iur Interface Radio Link

The SRNC sends the Radio Link Reconfiguration Prepare message to the DRNC. The

DRNC prepares for the reconfiguration of the user plane and the Iub interface, and

returns the RADIO LINK RECONFIGURATION READY message to the SRNC.

After receiving the RADIO LINK RECONFIGURATION READY message, the SRNC

reconfigures the FP for the user plane.

After completion of reconfiguration preparation, the SRNC sends the RADIO LINK

RECONFIGURATION COMMIT message to the DRNC. After receiving the message, the

DRNC configures the user plane according to the contents in the message, and then



sends the RADIO LINK RECONFIGURATION COMMIT message to the Node B.

The SRNC and the DRNC simultaneously activates the new configuration data of the

radio links and releases the original configuration data.

If the SRNC judges that it is necessary to cancel the Iur Interface Radio Link

reconfiguration, it first cancels the user plane FP configuration, deletes the transmission

bearer, and sends the RADIO LINK RECONFIGURATION CANCEL message to the

DRNC. The DRNC receives the RADIO LINK RECONFIGURATION CANCEL

MESSAGE from the SRNC, cancels the reconfiguration task, deletes the transmission

bearer, and then sends the RADIO LINK RECONFIGURATION CANCEL message to the

Node B.

3.12.2 Releasing the Iur Interface Radio Link

When receiving the radio link deletion message, the DRNC sends a radio link deletion

message to the Node B. The DRNC receives the radio link deletion success message

from the Node B, releases transmission bearer, and deletes the FP. The DRNC then

sends the radio link deletion success message to the SRNC. The flow ends.

3.13 RB reconfiguration

During the RAB reconfiguration, the RNC modifies the existing RB. See the following

figure.



Figure 3-21 RB reconfiguration

As shown in the above figure, the RNC sends the RADIO BEAER RECONFIGURATION

message to the UE. The message includes information on the RB to be reconfigured,

transport channel, and physical channel. After receiving the message, the UE returns the

RADIO BEARER RECONFIGURATION COMPLETE message as a response. The RNC

fills the information of the RB, the transport channel and the physical channel in the

RADIO BEAER RECONFIGURATION message according to the existing channels of the

UE and the channels to be set up for the UE.

The RNC sends the RADIO BEARER RECONFIGURATION message over the RRC

connection to the UE. The RNC receives the RADIO BEARER RECONFIGURATION

COMPLETE message from the UE.

If the RNC receives the RADIO BEARER RECONFIGURATION FAILURE message over

the RRC connection or has not received the response from the UE within 5 seconds, it

restores the configuration for the user plane and returns to the status before the RB

reconfiguration.

3.14 Iu Overload Control

When the traffic of Iu is overload, RNC should take measures of overload control to

UESource

RNC

Radio Bearer ReconfigurationRRC RRC

Radio Bearer Reconfiguration CompleteRRC RRC

Radio Bearer Reconfiguration FailureRRC RRC

Condition：RB reconfiguration success

Condition：RB reconfiguration

failed

Condition：RNC didn’t receive response message from UE after 5

second

Return the status

before RB

reconfiguration



insure the stability of the system.

When the overloading is detected, CN will send the overload message to RNC(fig.

20).and overload message should include the Global CN-ID IE if NNSF is started. RNC

should perform the actions as describled below when receive the overload message:

If the timer TigOR is not set, set the timer TigOR and TigTR.

RNC should ignore the follow-up overload message send by CN unless TigOR is

timeout.

If TinTR is timeout, consider the CN is not overload anymore.

If RNC receive the RRC connection setup request of UE exclude the reason of

emergency call, RNC should check if the CN is overload first. If CN is overload and

current network have neither Iu Flex nor networkshare(MSC number is 1,SGSN number

is 1) and RNC is set using RRC Reject to reduce the system load, RNC should generate

a random integer between 1-100 by a random function, if the integer is less then the

RRC reject proportion which set in the system before, then RNC send RRC Reject, or

else, setup the RRC connection. Furthermore, when RNC take the process of NNSF, it

should take the load balance in the CN which is reachable and not overload, if there is no

CN satisfy the condition, then take the load balance in the CN which is reachable and

overload.



Figure 3-22 Iu overload control

3.15 Deferred SIB11/12

In order to avoid the obvious interruption of services due to reading SIB11, SIB11bis or

SIB12, especially a lot of neighbouring cells are configured (over 20 neighboring cells for

example). UE is allowed to send messages through RACH or receive messages through

FACH before reading and storing SIB11/12 information, which named deferred SIB11/12.

RNC will include the IE “Deferred measurement control UTRAN support” in SIB3

message if the UTRAN support this feather. If UE receive this IE in SIB3, then it can

add the IE ” Deferred measurement control reading” into Radio Bear Reconfig Complete

or RRC Connection Setup Complete or UTRAN Mobility informaion Confirm message,

which notify UTRAN the incomplete reading SIB11/11bis/12. After switching to a non

CELL-DCH status, UE needs to complete SIB11/11bis/12 reading and storing,

RNC will judge the ability of deferred SIB11/12 according to whether the

DefSibSuptSwch is enabled or not.

If DefSibSuptSwch is 1, RNC will include the IE “Deferred measurement control

UTRAN support ” In SIB3 Message.

If DefSibSuptSwch is 0, RNC will not include the IE “Deferred measurement control

UTRAN support ” In SIB3 Message.

RNC MSC Server

OVERLOAD

RNC SGSN

OVERLOAD



4 Configuration and Parameters

4.1 System Information Broadcasting Parameters

4.1.1 SIB1 Parameter List

Id Abbreviate Parameter name

1 T300 Waiting Time After UE Sending RRC CONNECTION

SETUP REQUEST Message(T300)

2 N300 Maximum Number of Retransmissions of the RRC

CONNECTION REQUEST Message (N300)

3 T312Idle (RL

synchronization)

T312 in Idle Mode)(Waiting Time for Receiving "In Sync"

from L1 in Idle Mode (T312 in Idle Mode)

4 N312Idle Maximum Number of " In Sync" Received from L1 in Idle

Mode (N312 in Idle Mode)

5 T302 Waiting Time After UE Sending CELL/URA UPDATE

Message(T302)

6 N302 Maximum Number of Retransmissions of the CELL/URA

UPDATE Message (N302)

7 T304 Waiting Time After UE Sending UE CAPABILITY

INFORMATION Message(T304)

8 N304 Maximum Number of Retransmissions of the UE

CAPABILITY INFORMATION Message (N304)

9 T305 Period of Cell/URA Update When UE is in

CELL_FACH/CELL_PCH/ URA_PCH State(T305)(min)

10 T307 Waiting Time for Cell Reselection After UE is out of

Service(T307)

11 N308 maximum number of retransmissions of the RRC

CONNECTION RELEASE COMPLETE

12 T308 Waiting Time After Sending RRC CONNECTION RELEASE

COMPLETE Message in CELL_DCH State(T308)

13 T309 Waiting Time After Requesting Connection Establishment in

Other System(eg. GSM) (T309)

14 T312Connected T312 in Connected Mode,Waiting Time for Receiving "In

Sync" from L1 in Connected Mode (T312 in Connected




Mode)

15 N312Connected

N312 in Connected Mode,Maximum Number of "In Sync"

Received from L1 in Connected Mode (N312 in Connected

Mode)

16 T313 Waiting Time After DPCCH Established in CELL_DCH State

Losing Sychronization (T313)

17 N313 Maximum Number of Successive "Out of Sync" Received

from L1(N313)

18 T314 Waiting Time for Completion of Cell Upate When Radio Link

Fails and Radio Bearer(s) Associated with T314 Exist (T314)

19 T315 Waiting Time for Completion of Cell Upate When Radio Link

Fails and Radio Bearer(s) Associated with T315 Exist (T315)

20 N315 Maximum Number of Successive "In Sync" Received from

L1 During T313 is Activated ( N315)

21 T316 mobility Waiting Time for Cell Selection/Reselection After UE is out

of Service in CELL_PCH/URA_PCH State(T316)(s)

22 MCC Mobile Country Code

23 MNC Mobile Network Code

24 CnDomain CN Domain Supported

25 T3212Cs T3212 (hour)

26 ATTIndCs IMSI Attach and Detach Indicator

27 NMOPs Network Mode of Operation

28 Kcs CS Domain DRX Cycle Length Coefficient

29 Kps PS Domain DRX Cycle Length Coefficient

30 MbmsModPrdC

oeff Modification Period Coefficient for MBMS

31 T323Swch Switch of T323 Broadcasting

32 T323 UE’s Waiting Time of Sending Message “Signaling

Connection Release Indication”(with cause)



4.1.2 SIB1 Parameter Configuration

4.1.2.1 T300

OMC Path

Path:View->Configuration Management->RNC NE->RNC Radio Resource

Management->Advanced Parameter Manage ->INFORMATION ON THE CONSTANTS

OF THE UE COUNTER AND TIMER ->Waiting Time After UE Sending RRC

CONNECTION SETUP REQUEST Message(T300)

Parameter Configuration

Configuration Description: If the UE has not received the response message after the

period specified by the parameter, it considers the occurrence of time out and resends

the RRC connection request. By reducing the waiting time, you can reduce the time

taken in RRC connection setup, provided that the quality at the air interface is desirable.

4.1.2.2 N300

OMC Path



OF THE UE COUNTER AND TIMER ->Maximum Number of Retransmissions of the

RRC CONNECTION REQUEST Message (N300)


Configuration Description: If the Maximum Number of Retransmissions of the RRC

CONNECTION REQUEST Message exceeds the value, the system considers the

occurrence of call drop. If the value of the parameter increases, the call drop possibility

also drops accordingly, but the load at the air interface also increases accordingly.

4.1.2.3 T312Idle

OMC Path





OF THE UE COUNTER AND TIMER ->Waiting Time for Receiving "In Sync" from L1 in

Idle Mode (T312 in Idle Mode)


Configuration Description:By reducing the waiting time, you can speed up the exchange

with layer 1, but the flow fails easily if the quality of the air interface is undesirable.

4.1.2.4 N312Idle

OMC Path



OF THE UE COUNTER AND TIMER ->Maximum Number of "In Sync" Received from L1

in Idle Mode (N312 in Idle Mode)


Configuration Description: The smaller the parameter, it is easier to judge whether the

synchronization finishes, but the chance of fake synchronization also increases; the

larger the parameter, the higher the reliability, but it is more time consuming.

4.1.2.5 T302

OMC Path



OF THE UE COUNTER AND TIMER ->Waiting Time After UE Sending CELL/URA

UPDATE Message(T302)


Configuration Description:If the system has not received the message after the waiting

time, it considers the occurrence of timeout. The larger the parameter, it is more difficult



to judge the occurrence of timeout, and the lower the flow processing efficiency.

4.1.2.6 N302

OMC Path



OF THE UE COUNTER AND TIMER ->Maximum Number of Retransmissions of the

CELL/URA UPDATE Message (N302)


Configuration Description: If the number of retransmission events exceeds the value of

the parameter, the system considers the flow failed. The smaller the value, it is more

easy to judge that the flow fails.

4.1.2.7 T304

OMC Path



OF THE UE COUNTER AND TIMER ->Waiting Time After UE Sending UE CAPABILITY

INFORMATION Message(T304)


Configuration Description:If the system has not received any message after the waiting

time, it considers the occurrence of timeout. The larger the parameter, it is more difficult

to judge the occurrence of timeout.

4.1.2.8 N304

OMC Path





OF THE UE COUNTER AND TIMER ->Maximum Number of Retransmissions of the UE

CAPABILITY INFORMATION Message (N304)


Configuration Description: If the number of retransmission events exceeds the value of

the parameter, the system considers the flow failed. The smaller the value, it is easier to

judge that the flow fails.

4.1.2.9 T305

OMC Path



OF THE UE COUNTER AND TIMER -> Period of Cell/URA Update When UE is in

CELL_FACH/CELL_PCH/ URA_PCH State(T305)(min)


Configuration Description: The smaller the parameter, the system updates cells and URA

more frequently.

4.1.2.10 T307

OMC Path



OF THE UE COUNTER AND TIMER ->Waiting Time for Cell Reselection After UE is out

of Service(T307)


Configuration Description: The parameter specifies the waiting time between the time

when the UE leaves the serving cell and the time when the UE reselects the cell. The

smaller the parameter, more quickly the UE can reenter the network, but this may



increase the load of the UE and the system.

4.1.2.11 N308

OMC Path


Management->Advanced Parameter Manage ->RNC Radio Resource Management

->N308


Configuration Description: The smaller the parameter, the higher the chance of judging

flow failure.

4.1.2.12 T308

OMC Path



OF THE UE COUNTER AND TIMER ->Waiting Time After Sending RRC CONNECTION

RELEASE COMPLETE Message in CELL_DCH State(T308)

4.1.2.13 T309

OMC Path



OF THE UE COUNTER AND TIMER ->Waiting Time After Requesting Connection

Establishment in Other System(eg. GSM) (T309)



time, it considers the occurrence of timeout.



4.1.2.14 T312Connected

OMC Path



OF THE UE COUNTER AND TIMER ->Waiting Time After Sending RRC CONNECTION

RELEASE COMPLETE Message in CELL_DCH State(T308)


Configuration Description: If the system has not received the message after the waiting


4.1.2.15 N312Connected

OMC Path



OF THE UE COUNTER AND TIMER ->Maximum Number of "In Sync" Received from L1

in Connected Mode (N312 in Connected Mode)





4.1.2.16 T313

OMC Path



OF THE UE COUNTER AND TIMER ->Waiting Time After DPCCH Established in

CELL_DCH State Losing Sychronization (T313)






4.1.2.17 N313

OMC Path



OF THE UE COUNTER AND TIMER ->Maximum Number of Successive "Out of Sync"

Received from L1(N313)





4.1.2.18 T314

OMC Path



OF THE UE COUNTER AND TIMER ->Waiting Time for Completion of Cell Upate When

Radio Link Fails and Radio Bearer(s) Associated with T314 Exist (T314)




4.1.2.19 T315

OMC Path





OF THE UE COUNTER AND TIMER ->Waiting Time for Completion of Cell Upate When

Radio Link Fails and Radio Bearer(s) Associated with T315 Exist (T315)




4.1.2.20 N315

OMC Path



OF THE UE COUNTER AND TIMER ->Maximum Number of Successive "In Sync"

Received from L1 During T313 is Activated ( N315)





4.1.2.21 T316

OMC Path



OF THE UE COUNTER AND TIMER -> Waiting Time for Cell Selection/Reselection After

UE is out of Service in CELL_PCH/URA_PCH State(T316)(s)






4.1.2.22 MCC

OMC Path


Management->CN NAS Configuration Information ->Mobile Country Code


Configuration Description: The parameter specifies the mobile country code.

4.1.2.23 MNC

OMC Path


Management->CN NAS Configuration Information ->Mobile Network Code


Configuration Description: The parameter specifies the mobile network code.

4.1.2.24 CnDomain

OMC Path


Management->CN NAS Configuration Information ->CN Domain Supported


Configuration Description: The parameter specifies the supported CN domains.

4.1.2.25 T3212Cs

OMC Path


Management->Advanced Parameter Manage ->CN NAS Information->Timer for



updating location periodically


Configuration Description: The parameter specifies the interval at which the location

information is reported. The smaller the parameter, it is easier to judge the real location.

4.1.2.26 ATTIndCs

OMC Path


Management->CN NAS Configuration Information ->IMSI Attach and Detach Indicator

4.1.2.27 NMOPs

OMC Path


Management->CN NAS Configuration Information ->Network Mode of Operation


Configuration Description:0: Network operation mode I indicates that the Gs interface

appears; 1: The network operation mode 2 indicates that the Gs interface does not

appear.

4.1.2.28 Kcs

OMC Path


Management->Advanced Parameter Manage ->CN NAS Information ->CS Domain DRX

Cycle Length Coefficient


Configuration Description: The parameter specifies the CS Domain DRX Cycle Length



Coefficient.

4.1.2.29 Kps

OMC Path


Management->Advanced Parameter Manage ->CN NAS Information ->PS Domain DRX



Configuration Description: The parameter specifies the PS Domain DRX Cycle Length

Coefficient.

4.1.2.30 MbmsModPrdCoeff

OMC Path


Management->Advanced Parameter Manage ->CN NAS Information->Modification

Period Coefficient for MBMS


Configuration Description: This parameter specifies the interval at which the MBMS is

modified.

4.1.2.31 T323Swch

OMC Path

Path:View->Configuration Management->RNC NE->RNC Radio Resource Management->

Advanced Parameter Manage->UE Timers and Constants Information -> Switch of T323

broadcasting




Configuration Description:

0:RNC will not include T323 Timer in SIB1 and UTRAN Mobility Information message

1: RNC will include T323 Timer in SIB1 and UTRAN Mobility Information message

4.1.2.32 T323

OMC Path


Advanced Parameter Manage->UE Timers and Constants Information -> UE's Waiting

Time of Sending Message "Signaling Connection Release Indication"(with

cause)(T323)(s)


Configuration Description: This parameter specifies indicates the interval of reporting

signaling connection release indication(with cause).



1 URANum URA Number

2 URA[4] URA Identity


4.1.4.1 URANum

OMC Path


Management->UtranCell->UtranCell global Info ->URA Number


Configuration Description: The parameter specifies the number of URAs for the current

cell. The system supports up to 4 URAs.



4.1.4.2 URA[4]

OMC Path


Management->UtranCell->UtranCell global Info ->URA Identity


Configuration Description: The parameter specifies the No. of the URA to which the

current area belongs.

4.1.5 SIB3/SIB4 Parameter List


1 Cid Cell Identity

2 Sib3orSib4 Broadcast in either SIB3 or SIB4

3 QualMeas Measurement Quantity for Cell Selection and

Reselection

4 SIntraSearchPre Sintrasearch Configuration Tag

5 SIntraSearch Sintrasearch

6 SInterSearchPre Sintersearch Configuration Tag

7 SInterSearch Sintersearch

8 SSearchHCS Pre SsearchHCS Configuration Tag

9 SSearchHCS SsearchHCS

10 SSearchRat Ssearch,RAT

11 SHCSRatPre SHCS,RAT Configuration Tag

12 SHCSRat SHCS,RAT)

13 SLimitRat Slimit,SearchRAT

14 QQualMin Qqualmin

15 QRxLevMin Qrxlevmin

16 DltaQRxLevMinPr DeltaQrxlevmin Configuration Tag)

17 CellBarredInd Cell Barred Indicator

18 InFreqReselInd Intra-Frequency Cell Re-Selection Indicator

19 TBarred Tbarred




20 OperatorUseInd Cell Reserved for Operator Use

21 CellRsvExt Cell Reservation Extension

22 ACBarredOmcr Access Class N Barred Indicator (N=0…9)

23 DltaQRxLevMin DeltaQrxlevmin

4.1.6 SIB3/SIB4 Parameter Configuration

4.1.6.1 CId

OMC Path


Management->UtranCell->UtranCell global Info ->Cell Identity


Configuration Description: The parameter specifies the ID of a cell and is used to

distinguish different cells.

4.1.6.2 Sib3orSib4

OMC Path


Management->UtranCell->Cell Selection and Reselection->Broadcast in either SIB3 or

SIB4

4.1.6.3 QualMeas

OMC Path


Management->UtranCell->Cell Selection and Reselection->Advanced Parameter

Manage ->Cell Selection and Reselection ->Measurement Quantity for Cell Selection

and Reselection




Configuration Description: If the parameter is set to 1, select CPICH Ec/No for

measurement; if the parameter is set to 2, select CPICH RSCP for measurem ent.

4.1.6.4 SIntraSearchPre

OMC Path



Manage ->Cell Selection and Reselection ->Sintrasearch Configuration Tag


Configuration Description: Configure this parameter so that the UE conducts

intra-frequency measurement when the quality of the current cell is lower than the

threshold.

4.1.6.5 SIntraSearch

OMC Path



Manage ->Cell Selection and Reselection ->Sintrasearch


Configuration Description: The parameter specifies the intra-frequency measurement

threshold of cell reselection. The lower the threshold, it is easier for the UE to conduct

intra-frequency measurement.

4.1.6.6 SInterSearchPre

OMC Path





Manage ->Cell Selection and Reselection ->Sintersearch Configuration Tag



inter-frequency measurement when the quality of the current cell is lower than the

threshold.

4.1.6.7 SInterSearch

OMC Path



Manage ->Cell Selection and Reselection ->Sintersearch


Configuration Description: The parameter specifies the inter-frequency measurement


inter-frequency measurement.

4.1.6.8 SSearchHCS Pre

OMC Path



Manage ->Cell Selection and Reselection ->SsearchHCS Configuration Tag


Configuration Description: 0: Do not configure the parameter SsearchHCS; 1:configure

the parameter SsearchHCS.Configure this parameter so that the UE conducts HCS

adjacent cell measurement when the quality of the current cell is lower than the

threshold.



4.1.6.9 SSearchHCS

OMC Path



Manage ->Cell Selection and Reselection ->SsearchHCS


Configuration Description: The parameter specifies the HCS adjacent cell measurement


HCS adjacent cell measurement.

4.1.6.10 SSearchRat

OMC Path



Manage ->Cell Selection and Reselection ->Ssearch,RAT


Configuration Description: The parameter specifies the inter-system adjacent cell

measurement threshold of cell reselection. The lower the threshold, it is easier for the UE

to conduct inter-system adjacent cell measurement.

4.1.6.11 SHCSRatPre

OMC Path



Manage ->Cell Selection and Reselection->SHCS,RAT Configuration Tag





inter-system adjacent cell measurement when the quality of the current cell is lower than

the threshold.

4.1.6.12 SHCSRat

OMC Path



Manage ->Cell Selection and Reselection ->SHCS,RAT


Configuration Description: The parameter specifies the inter-system HCS adjacent cell

measurement threshold of cell reselection. The lower the threshold, it is easier for the UE

to conduct inter-system HCS adjacent cell measurement.

4.1.6.13 SLimitRat

OMC Path



Manage ->Cell Selection and Reselection ->Slimit,SearchRAT


Configuration Description: The parameter specifies the inter-system high HSC priority

cell measurement threshold of cell reselection. The lower the threshold, it is easier for

the UE to conduct inter-system high HSC priority cell measurement.

4.1.6.14 QqualMinSib11

OMC Path





Manage ->Cell Selection and Reselection ->Qqualmin


Configuration Description: The parameter specifies the minimum cell quality requirement

level. The lower the level, it is easier to conduct cell reselection.

4.1.6.15 QRxLevMin

OMC Path



Manage ->Cell Selection and Reselection ->Qrxlevmin


Configuration Description: The parameter specifies the minimum receive electrical level

threshold of a cell. The lower the threshold, cell reselection takes place more easily.

4.1.6.16 DltaQRxLevMinPr

OMC Path



Manage ->Cell Selection and Reselection ->DeltaQrxlevmin Configuration Tag

4.1.6.17 CellBarredInd

OMC Path



Manage ->Cell Selection and Reselection ->Cell Barred Indicator



4.1.6.18 InFreqReselInd

OMC Path



Manage ->Cell Selection and Reselection ->Intra-Frequency Cell Re-Selection Indicator.

4.1.6.19 TBarred

OMC Path



Manage ->Cell Selection and Reselection ->Tbarred

4.1.6.20 OperatorUseInd

OMC Path



Manage ->Cell Selection and Reselection ->Cell Reserved for Operator Use

4.1.6.21 CellRsvExt

OMC Path



Manage ->Cell Selection and Reselection ->Cell Reservation Extension

4.1.6.22 ACBarredOmcr

OMC Path





Manage ->Cell Selection and Reselection ->Access Class N Barred Indicator (N=0…9)


Configuration Description: The parameter specifies the barred access level and is

configurable in the OMCR.

4.1.6.23 DltaQRxLevMin

OMC Path



Manage ->Cell Selection and Reselection -> Increment to the Minimum Required

Received Level in the Cell (DeltaQrxlevmin)


Configuration Description: This parameter indicates the extension of Qrxlevmin, which

means Qrxlevmin = Qrxlevmin + DeltaQrxlevmin.


Id Abbreviated name Parameter name

1 SIB5orSIB6 Broadcast in either SIB5 or SIB6

2 TfsIndex TFS Index

3 ChType Channel Type

4 TfNum Transport Format Number

5 TrBlkNum Number of Transport Blocks

6 RlcSize Transport Block Size

7 TTI Transmission Time Interval

8 CodingRate Coding Rate

9 RateMatchAttr Rate Matching Attribute

10 CRCSize CRC Size

11 CPCId MICH Common Physical Channel ID




12 MichChCode MICH Channelisation Code No.

13 NiNumPerFrame Number of NI per Frame

14 MichPwr MICH Power(dB)

15 SttdInd MICH STTD Indicator

16 SttdInd AICH STTD Indicator

17 AichTranTime AICH Transmission Timing

18 AichPwr AICH Power

19 ChCode AICH Channelisation Code No.

20 SCCPCHUsage SCCPCH Usage

21 SccpchOffset S-CCPCH Frame Time Offset(chip)

22 MplexPos Multiplexing Position

23 PCHInd Indicator for S-CCPCH Carrying PCH

24 ChCode PICH Channelisation Code No.

25 CPCId Pich Common Physical Channel ID

26 PichPwr PICH Power

27 SttdInd PICH STTD Indicator

28 DlScraCode S-CPICH Scrambling Code

29 ChCode S-CPICH Channelisation Code No

30 SttdInd S-CCPCH STTD Indicator

31 Signature Available Signature

32 AvailSubChanNum PRACH Available Subchannel Number

33 AvailableSF PRACH Available SF

34 PreamScraCode PRACH Preamble Scrambling Code

35 PcpichPwr P-CPICH Power(dBm)

36 PunctLimit Puncturing Limit

37 DlScraCode S-CCPCH Scrambling Code

38 DlChCodeNo S-CCPCH Channelisation Code No.

39 SlotFmt S-CCPCH Slot Format

40 SttdInd S-CCPCH STTD Indicator

41 SignalFach FACH Usage

42 TfcsIndex Tfcs Index




43 CtfcNum CTFC Number

44 Ctfc CTFC Id

45 TfcsIndex Tfcs Index

46 CtfcNum CTFC Number

47 Ctfc CTFC Id

48 SttdInd P-CPICH STTD Indicator

49 SttdInd PCCPCH STTD Indicator

50 SIB6IND SIB6 Indicator

51 PccpchInfSib5Pre PCCPCH Information in SIB5 Configuration Tag

52 PccpchInfSib6Pre PCCPCH Information in SIB6 Configuration Tag

4.1.8 SIB5/SIB6 Parameter Configuration

4.1.8.1 SIB5orSIB6

OMC Path

Path:View->Configuration Management-> RNC Radio Resource Management->Utran

cell->Utran cell xx-> Modify Advanced Parameter-> SCCPCH-> Broadcast in either SIB5

or SIB6

4.1.8.2 TFS Index

Configure the parameter for the RACH, FACH, PCH, and FACH carrying the MCCH.

OMC Path

Path of the parameter Tfs Index of the FACH: View->Configuration Management-> RNC

Radio Resource Management->Utran cell->Utran cell xx-> Modify Advanced Parameter ->

FACH-> TFS Index

Path of the parameter Tfs Index of the RACH: View->Configuration Management->RNC

NE->RNC Radio Resource Management-> UTRAN Cell-> UTRAN Cell XXX-> Modify

Advanced Parameter ->RACH-> TFS Index



Path of the parameter TfsIndex of the PCH:View->Configuration Management-> RNC

Radio Resource Management->Utran cell->Utran cell xx-> Modify Advanced Parameter ->

PCH-> TFS Index

Path of the parameter Tfs Index of the FACH carrying the MCCH: View->Configuration

Management->RNC NE->RNC Radio Resource Management-> UtranCell ->Utrancell

XXX->Advanced Parameter Manage ->MBMS Configuration Information in a Cell ->

TfsIndex

4.1.8.3 ChType

OMC Path

Path:View->Configuration Management -> RNC Radio Resource Management-> Modify

Advanced Parameter->Transmission Format Composition Set

4.1.8.4 TfNum

OMC Path



4.1.8.5 TrBlkNum[MAX_TF]

OMC Path



4.1.8.6 RlcSize[MAX_TF]

OMC Path





4.1.8.7 TTI

OMC Path



4.1.8.8 Coding Rate

OMC Path


Advanced Parameter->Transmission Format Composition Set ->Coding Rate

4.1.8.9 RateMatchAttr

OMC Path


Advanced Parameter->Transmission Format Composition Set-> Rate Matching Attribute

4.1.8.10 CRC Size

OMC Path


Advanced Parameter->Transmission Format Composition Set-> CRC Size

4.1.8.11 MICH Common Physical Channel ID

OMC Path


cell->Utran cell xx->Modify Advanced Parameter-> MICH



4.1.8.12 MichChCode

OMC Path

Path: View->Configuration Management-> RNC Radio Resource Management->Utran

cell->Utran cell xx->Modify Advanced Parameter-> MICH Channelisation Code No.

4.1.8.13 NiNumPerFrame

OMC Path


cell->Utran cell xx->Modify Advanced Parameter-> MICH

4.1.8.14 MichPwr

OMC Path


cell->Utran cell xx->Modify Advanced Parameter-> MICH -> MICH Power(dB)

4.1.8.15 MICH STTD Indicator

OMC Path


cell->Utran cell xx->Modify Advanced Parameter-> MICH-> MICH STTD Indicator

4.1.8.16 AICH STTD Indicator

OMC Path


cell->Utran cell xx->Modify Advanced Parameter->AICH->AICH STTD Indicator



4.1.8.17 AichTranTime

OMC Path


cell->Utran cell xx->Modify Advanced Parameter->AICH->AICH Transmission Timing

4.1.8.18 AichPwr

OMC Path

Path:View->Configuration Management -> RNC Radio Resource Management->Modify

Advanced Parameter->Power Control not Related to Service->AICH Power

4.1.8.19 AICH Channelisation Code No.

OMC Path


cell->Utran cell xx->Modify Advanced Parameter->AICH->AICH Channelisation Code No.

4.1.8.20 SccpchUsage

OMC Path


cell->Utran cell xx-> Modify Advanced Parameter-> SCCPCH -> SCCPCH Usage

4.1.8.21 SccpchOffset

OMC Path


cell->Utran cell xx-> Modify Advanced Parameter-> SCCPCH-> S-CCPCH Frame Time

Offset(chip)



4.1.8.22 MplexPos

OMC Path


cell->Utran cell xx-> Modify Advanced Parameter-> SCCPCH-> Multiplexing Position

4.1.8.23 PCHInd

OMC Path


cell->Utran cell xx-> Modify Advanced Parameter-> SCCPCH-> Indicator for S-CCPCH

Carrying PCH

4.1.8.24 PICH Channelisation Code No.

OMC Path


cell->Utran cell xx->Modify Advanced Parameter -> PICH-> PICH Channelisation Code

No.

4.1.8.25 PICH Common Physical Channel ID

OMC Path


cell->Utran cell xx->Modify Advanced Parameter -> PICH -> PICH Common Physical

Channel ID

4.1.8.26 PICH Power

OMC Path


Advanced Parameter->Power Control not Related to Service->PICH Power



4.1.8.27 PICH STTD Indicator

OMC Path


cell->Utran cell xx->Modify Advanced Parameter -> PICH

4.1.8.28 S-CPICH Scrambling Code

OMC Path


cell->Utran cell xx->Modify Advanced Parameter->SCPICH-> S-CPICH Scrambling code

4.1.8.29 S-CPICH Channelisation Code No.

OMC Path


cell->Utran cell xx->Modify Advanced Parameter->SCPICH-> S-CPICH Channelisation

Code No.

4.1.8.30 S-CCPCH STTD Indicator

OMC Path

Path: View->Configuration Management->RNC NE->RNC Radio Resource

Management->UtranCell->Advanced Parameter Manage -> S-CCPCH -> S-CCPCH

STTD Indicator

4.1.8.31 Signature

OMC Path


Management->UtranCell->Advanced Parameter Manage ->PRACH->Available

Signature



4.1.8.32 AvailSubChanNum

OMC Path


Management->UtranCell->Advanced Parameter Manage ->PRACH ->PRACH Available

Subchannel Number

4.1.8.33 AvailableSF

OMC Path


Management->UtranCell->Advanced Parameter Manage ->PRACH ->PRACH Available

SF

4.1.8.34 PreamScraCode

OMC Path


Management->UtranCell->Advanced Parameter Manage ->PRACH ->PRACH

Preamble Scrambling Code

4.1.8.35 PcpichPwr

OMC Path


cell->Utran cell xx-> CellSetupParameters

4.1.8.36 PunctLimit

OMC Path


Management->UtranCell->Advanced Parameter Manage ->PRACH ->Puncturing Limit



4.1.8.37 S-CCPCH Scrambling code

OMC Path


Management->UtranCell->Advanced Parameter Manage ->SCCPCH ->S-CCPCH

Scrambling Code

4.1.8.38 S-CCPCH Channelisation Code No.

OMC Path


Management->UtranCell->Advanced Parameter Manage ->SCCPCH ->S-CCPCH

Channelisation Code No

4.1.8.39 SlotFmt

OMC Path


Management->UtranCell->Advanced Parameter Manage ->SCCPCH ->S-CCPCH Slot

Format

4.1.8.40 S-CCPCH STTD Indicator

OMC Path


Management->UtranCell->Advanced Parameter Manage ->SCCPCH ->S-CCPCH STTD

Indicator

4.1.8.41 SignalFach

OMC Path




cell->Utran cell xx->Modify Advanced Parameter-> FACH-> SignalFach

4.1.8.42 TfcsIndex

OMC Path


cell->Utran cell xx->Modify Advanced Parameter-> PRACH-> TFCS Index

4.1.8.43 CtfcNum

OMC Path


Advanced Parameter->Transmission Format Composition Set of PRACH

4.1.8.44 Ctfc

OMC Path


Advanced Parameter->Transmission Format Composition Set of PRACH

4.1.8.45 TfcsIndex

OMC Path


cell->Utran cell xx-> Modify Advanced Parameter-> SCCPCH

4.1.8.46 CtfcNum

OMC Path


Advanced Parameter->Transmission Format Composition Set of SCCPCH-> CTFC

Number



4.1.8.47 Ctfc

OMC Path


Advanced Parameter->Transmission Format Composition Set of SCCPCH-> CTFC Id

4.1.8.48 P-CPICH STTD Indicator

OMC Path


cell->Utran cell xx->Modify Advanced Parameter->PCPICH

4.1.8.49 P-CCPCH STTD Indicator

OMC Path


cell->Utran cell xx->Modify Advanced Parameter-> PCCPCH

4.1.8.50 SIB6 Indicator

OMC Path


Management->UtranCell->Advanced Parameter Manage ->UtranCell -> SIB6

Indicator

4.1.8.51 PCCPCH Information in SIB5 Configuration Tag

OMC Path


Management->UtranCell->Advanced Parameter Manage ->UtranCell -> PCCPCH

Information in SIB5 Configuration Tag



4.1.8.52 PCCPCH Information in SIB6 Configuration Tag

OMC Path


Management->UtranCell->Advanced Parameter Manage ->UtranCell -> PCCPCH

Information in SIB6 Configuration Tag



1 DynPstLevelInit Initial Dynamic Persistence Level

2 SIB7Originator SIB7 Originator

3 EXPTIMFACTOR Expiration Time Factor

4 PRACHSIB6PRE Dynamic Persistence Level Information of SIB6

PRACH in SIB7 Configuration Tag


4.1.10.1 DynPstLevelInit

OMC Path


Management->UtranCell->Advanced Parameter Manage ->UtranCell ->Initial Dynamic

Persistence Level

4.1.10.2 SIB7Originator

OMC Path


Management->UtranCell->Advanced Parameter Manage ->UtranCell ->SIB7 Originator

4.1.10.3 EXPTIMFACTOR

OMC Path




Management->UtranCell->Advanced Parameter Manage ->UtranCell -> Expiration

Time Factor

4.1.10.4 PrachSib6Pre

OMC Path


Management->UtranCell->Advanced Parameter Manage ->UtranCell -> Dynamic

Persistence Level Information of SIB6 PRACH in SIB7 Configuration Tag


4.1.11.1 SIB11orSIB12

OMC Path


cell->Utran cell xx->Modify Advanced Parameter->UE Measurement Configuration In

System Information -> Broadcast in either SIB11 or SIB12

4.1.12 SIB11bis Parameter Configuration

4.1.12.1 SIB11orSIB11bis

OMC Path


Management->UtranCell->Neighbouring Cell->Sib11orSib11bis



4.2 Parameters related to Connection Setup and

Release

4.2.1 Parameter List


1 NReTran Maximum number of retransmission of the RRC

CONNECTION RELEASE

2 Twait Wait Time for RRC Connection Reestablishment(s)

3 N308 maximum number of retransmissions of the RRC

CONNECTION RELEASE COMPLETE

4 FDDFreqRngNum Number of FDD UMTS Frequency Range

5 GsmBARangeNum Number of GSM BA Range

6 GsmLRange[32] GSM Lower Range

7 GsmURange[32] GSM Upper Range

8 Luarfcn [32] UARFCN(Nlow)

9 Uuarfcn[32] UARFCN(Nupper)

10 InitRrcLBSw Load Balance Switch of Initial RRC Procedure

11 InitRrcOnDch Type of Transport Channel for Initial RRC Connection

Setup

12 TRbRecfgCmpDtoF Wait Time for RADIO BEARER RECONFIGURATION

COMPLETE when CELL_DCH to CELL_FACH

4.2.2 Parameter Configuration

For more details on the T3212CS description, refer to the section 4.1.2.2611.

4.2.2.1 NReTran

OMC Path



->Maximum Number of Retransmissions of the RRC CONNECTION RELEASE

Message




Configuration Description:The parameter specifies the number of the RRC

CONNECTION RELEASE messages retransmitted by the RNC after the UE does not

return the RRC CONNECTION RELEASE COMPLETE message. If the value of this

parameter decreases, the possibility of process failed will increase.

4.2.2.2 Twait

OMC Path



->Wait Time for RRC Connection Reestablishment


Configuration Description:The smaller the parameter, it is easier to trigger access

request flow, the larger the chance of second failure.

4.2.2.3 N308

OMC Path



->N308


Configuration Description: The smaller the parameter, the higher the chance of judging

flow failure.

4.2.2.4 FDDFreqRngNum

OMC Path




Management->RPLMN Range Information -> Number of FDD UMTS Frequency Range

4.2.2.5 GsmBARangeNum

OMC Path


Management->RPLMN Range Information -> Number of GSM BA Range

4.2.2.6 GsmLRange[32]

OMC Path


Management->RPLMN Range Information ->GSM Lower Range


Configuration Description: The value range of GSM Lower Range must be consistent

with that of GSM Upper Range.

4.2.2.7 GsmURange[32]

OMC Path


Management->RPLMN Range Information ->GSM Upper Range


Configuration Description: The value range of GSM Upper Range must be consistent

with that of GSM Lower Range.

4.2.2.8 Luarfcn [8]

OMC Path




Management->RPLMN Range Information ->UARFCN (Nlow)

4.2.2.9 Uuarfcn[8]

OMC Path


Management->RPLMN Range Information ->UARFCN(Nupper)

4.2.2.10 InitRrcLBSw

OMC Path


Management->UtranCell->Advanced Parameter Manage ->Balance Information ->Load

Balance Switch of Initial RRC Procedure

4.2.2.11 InitRrcOnDch

OMC Path



->Type of Transport Channel for Initial RRC Connection Setup


Configuration Description:0:forcedly establish the RRC connection over the DCH

channel and use the common signaling; 1: Forcedly establish the RRC conn ection over

the DCH channel and use the high speed signaling; 2: Forcedly establish the RRC

connection over the FACH channel and use the high speed signaling;3:Establish the

RRC connection over the DCH channel in a non-forced manner and use the common

signaling; 4: Establish the RRC connection over the DCH channel in a non-forced

manner and use the high speed signaling. Generally, select 1 because the RRC

connection setup efficiency is the highest.



4.2.2.12 TRbRecfgCmpDtoF

OMC Path


Advanced Parameter Manage->RNC Configuration Supplement Information -> Wait

Time for RADIO BEARER RECONFIGURATION COMPLETE when CELL_DCH to

CELL_FACH(s)


Configuration Description: This parameter specify the time interval the RNC has to wait

before receiving the RADIO BEARER RECONFIGURATION COMPLETE when the RNC

orders the UE Leaving CELL_DCH to CELL_FACH.

4.3 DSAR Parameters



1 CsDsarSwh Switch of CS Domain DSAR

2 PsDsarSwh Switch of PS Domain DSAR

3 CSDsarPollingSwh Switch of Polling in CS Domain DSAR

4 PSDsarPollingSwh Switch of Polling in PS Domain DSAR

5 CSBarAcNum Number of Barred AC in CS Domain

6 PSBarAcNum Number of Barred AC in PS Domain

7 BarInterval Time Interval of Barred AC

8 PagingLocaBarSwh Switch of Paging and Location/Registration

Restriction

9 CellBarAcSwh CellBarPollingSwh

10 CellBarAcNum Number of Cell Barred AC

11 CellBarPollingSwh Switch of Polling in Cell Restriction

12 CsACBarredOmcr CS Domain Specific Access Class N Barred

Indicator

13 PsACBarredOmcr PS Domain Specific Access Class N Barred




Indicator

14 UpdaSIB3CelNum Number of Cells Updating SIB3

15 UpdSIB3Celnt Time Interval Updating SIB3 among Cells


4.3.2.1 CsDsarSwh

OMC Path


Management->UTRAN Cell ->-UTRAN Cell Global Infomation >Switch of CS Domain

DSAR


Configuration Description: The parameter value is:

0: Switch Off CS Domain DSAR by OMCR, DSAR function is closed;

1: Switch On CS Domain DSAR by OMCR, DSAR function is triggered manually;

2: RNC Controls Dynamically CS Domain DSAR (According to Accessibility of Iu), DSAR

function will be triggered when CS unreached happens.

3: RNC Controls Dynamically CS Domain DSAR (According to Load of Iu or Accessibility

of Iu, DSAR function will be triggered when CS overload or unreached happens

4.3.2.2 PsDsarSwh

OMC Path


Management->UTRAN Cell ->-UTRAN Cell Global Infomation >Switch of PS Domain

DSAR





0: Switch Off PS Domain DSAR by OMCR, DSAR function is closed

1: Switch On PS Domain DSAR by OMCR, DSAR function is triggered manually

2: RNC Controls Dynamically CS Domain DSAR (According to Accessibility of Iu), DSAR

function will be triggered when PS unreached happens.

3: RNC Controls Dynamically CS Domain DSAR (According to Load of Iu or Accessibility

of Iu, DSAR function will be triggered when PS overload or unreached happens

4.3.2.3 CSDsarPollingSwh

OMC Path


Management->UTRAN Cell ->-UTRAN Cell Global Infomation >Switch of Polling in CS

Domain DSAR


Configuration Description: The parameter value is 0 when access restriction in CS

domain is not by polling method., and 1 when access restriction in CS domain is by

polling method.

4.3.2.4 PSDsarPollingSwh

OMC Path


Management->UTRAN Cell ->-UTRAN Cell Global Infomation >Switch of Polling in PS

Domain DSAR


Configuration Description: The parameter value is 0 when access restriction in PS

domain is not by polling method., and 1 when access restriction in PS domain is by



polling method.

4.3.2.5 CSBarAcNum

OMC Path


Management->UTRAN Cell ->-UTRAN Cell Global Infomation >Number of Barred AC

in CS domain


Configuration Description: For polling method, i f the value of this parameter increases,

the amount of AC restricted in CS domain will increase.

4.3.2.6 PSBarAcNum

OMC Path


Management->UTRAN Cell ->-UTRAN Cell Global Infomation >Number of Barred AC

in PS domain



the amount of AC restricted in PS domain will increase.

4.3.2.7 BarInterval

OMC Path


Management->UTRAN Cell ->Advanced Parameter Manage ->Time Interval of Barred

AC(s)





the restriction interval for the restricted users will increase, i.e. these users can’t access

to the relevant domain in a longer time, and the SIB3 update times will decrease.

If the value of this parameter decreases, the restriction interval for the restricted users

will decrease, and the SIB3 update times will increase which increases system load.

4.3.2.8 PagingLocaBarSwh

OMC Path


Management->UTRAN Cell ->-UTRAN Cell Global Infomation > Switch of Paging and

Location/Registration Restriction


Configuration Description: When the value of parameter is 1, the system will restrict part

of UEs from responding to paging message and Initiating the location/registration.

4.3.2.9 CellBarAcSwh

OMC Path


Management->UTRAN Cell ->Advanced Parameter Manage -> Switch of Cell Restriction



0: Close Close Cell Restriction by OMCR, cell restriction function is closed;

1: Open Cell Restriction by OMCR, cell restriction function is triggered manually;

2: Open and Close Cell Restriction Dynamically by RNC, cell restriction function will be

triggered when uplink overload happens in the cell.



4.3.2.10 CellBarAcNum

OMC Path


Management->UtranCell->Advanced Parameter Manage ->Utran Cell ->Number of

Cell Barred AC


Configuration Description: For polling method of cell bar, the value of this parameter

increase, the number of users forbidden to access increases, that is the number of users

permitted to access decreases. Contrarily, the value of this parameter decreases, the

number of users forbidden to access decrease, and the effect of cell bar function

becomes little.

4.3.2.11 CellBarPollingSwh

OMC Path


Management->UTRAN Cell ->Advanced Parameter Manage -> Switch of Polling in Cell

Restriction


Configuration Description: The parameter value is 0 when cell restriction is not by polling

method., and 1 when cell restriction is by polling method.

4.3.2.12 CsACBarredOmcr

OMC Path


Management->UTRAN Cell -> UTRAN Cell Global Infomation -> CS Domain Specific

Access Class N Barred Indicator




Configuration Description: Bit0~9 correspond AC0~9, bit value = 0 means barred, 1

means not barred, Bit10~15 is reserved and should always set to 1. Default value of this

parament is 65535(All AC is not barred).

4.3.2.13 PsACBarredOmcr

OMC Path


Management->UTRAN Cell -> UTRAN Cell Global Infomation -> PS Domain Specific

Access Class N Barred Indicator


Configuration Description: Bit0~9 correspond AC0~9, bit value = 0 means barred, 1

means not barred, Bit10~15 is reserved and should always set to 1. Default value of this

parament is 65535(All AC is not barred).

4.3.2.14 UpdaSIB3CelNum

OMC Path



-> UpdaSIB3CelNum


Configuration Description: This parameter indicates the number of cells updating SIB3

when Iu overloads or is not accessible. The value of this parameter is larger, more cells

need to update the SIB3 when Iu is overload or not accessible, the load of Iu chang more

quickly,but PingPang of the load of Iu happens more easily, the signalling connection of

Uu in other frequencies/systems may increase instantaneously. Otherwise, less cells

need to update the SIB3,the load of Iu change more slowly, but Ping-Pong of the load of

Iu happens more difficultly, the signaling connection of Uu will increase smoothly.



4.3.2.15 UpdSIB3Celnt

OMC Path



-> UpdSIB3Celnt


Configuration Description: This parameter indicates the time interval updating SIB3

among cells when Iu overloads or is not accessible. The value of this parameter is

smaller, the time interval of updating the SIB3 is shorter when Iu is overload or not

accessible, the load of Iu change more quickly, but Ping -Pong of the load of Iu happens

more easily, the signaling connection of Uu in other frequencies/systems may increase

instantaneously. Otherwise, the time interval of updating the SIB3 is longer, the load of Iu

change more slowly, but Ping-Pong of the load of Iu happens more difficultly, the

signaling connection of Uu will increase smoothly.

4.4 Paging Parameters



1 KUtran UTRAN DRX Cycle Length Coefficient

2 PagingSendTimes Sending Times of Paging Message

3 Kcs CS Domain DRX Cycle Length Coefficient

4 Kps PS Domain DRX Length Coefficient

5 Np Number of Paging Indicators per PICH Frame

6 PichPwr PICH Power

7 VirtualLac Vitrual Location Aera Code

8 VLacPaingInd Vitrual LAC Paging Support Indication

9 RNCFEATSWITCH21 Vitrual LAC Paging Support Indication




For details on configuring the PichPwr parameter, refer to the section “SIB5/SIB6

Parameter Configuration” .

4.4.2.1 KUtran

OMC Path



->UTRAN DRX Cycle Length Coefficient

4.4.2.2 PagingSendTimes

OMC Path


Management->UtranCell->Advanced Parameter Manage ->UtranCell ->Sending Times

of Paging Message


Configuration Description: The system has not obtained the information on the number of

retransmitted paging message when receiving no response.

If the value of this parameter increases, the possibility of paging success will increase.

With the increase of the Uu interface messages, the Uu interface becomes more time

consuming.

4.4.2.3 Kcs

OMC Path


Management->Advanced Parameter Manage ->CN NAS Information ->CS Domain DRX




4.4.2.4 Kps

OMC Path


Management->Advanced Parameter Manage ->CN NAS Information ->PS Domain DRX


4.4.2.5 Np

OMC Path


Management->UtranCell->Advanced Parameter Manage ->PICH ->Number of Paging

Indicators per PICH Frame


Configuration Description: The larger the parameter, the higher the paging success rate,

but the larger the transmit power of the PICH channel. 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

4.4.2.6 DltaQRxLevMin

OMC Path


Management->Advanced Parameter Manage -> Power Control not Related to

Service -> PICH Power




Configuration Description: This parameter indicates the extension of Qrxlevmin, which

means Qrxlevmin = Qrxlevmin + DeltaQrxlevmin.

4.4.2.7 VirtualLac

OMC Path


Management->UtranCell->Advanced Parameter Manage->Utran Cell->VirtualLac


Configuration Description: This parameter indicates the Virtual LAC of the CELL. i f the

CELL is at the boundary of LAC, the Virtual LAC is set as the neighbour LAC.

4.4.2.8 VLacPaingInd

OMC Path


Management->Advanced Parameter Manage ->Rnc Function-> VLacPaingInd


Configuration Description: This parameter indicates RNC support Virtual LAC Paging or

not. If RNC support, set it as 1.otherwise 0

4.4.2.9 RNCFEATSWITCH21

OMC Path

Path: View->Configuration Management->RNC NE->RNC Ground Resource

Management->Network Element Information->Adjacent RNC Office->Adjacent RNC

Office-3-> RNCFEATSWITCH21


Configuration Description: This parameter indicates the adjacent RNC support Virtual



LAC Paging or not. If adjacent RNC support, set it as 1.otherwise 0

4.5 Ciphering Parameters

4.5.1 EncryAlg

OMC Path



->Encryption Algorithm

4.6 Integrity Protection Parameters

4.6.1 IntegrityAlg

OMC Path



->Integrity Protection Algorithm

4.7 AMR Service Forced Queue Parameters



1 ForcQueSwiAMR Forced Queue Switch for AMR Service

2 TTrueQForced Maximum Time in the True Queue when Service be

Forced into Queue




4.7.2.1 ForcQueSwiAMR

OMC Path


Management->Advanced Parameter Manage ->Global Access Control -> Forced

Queue Switch for AMR Service


Configuration Description: If the switch is set to open, the AMR supports queue function

even though queue isn’t supported in the relevant RAB assignment message.

4.7.2.2 TTrueQForced

OMC Path


Management->Advanced Parameter Manage ->Global Access Control -> Maximum

Time in the True Queue when Service be Forced into Queue


Configuration Description: If the value of parameter increases, the success probability of

service access will increase.

4.8 Radio Connection Monitor Parameters

For more details on the T3212CS description, refer to the section 4.1.2.26.



4.9 RRC Connection Redirection Parameters



1 EmgCallRdtSwitch Emergency Call Redirect Switch

2 PriRedirectRat Prior Redirect RAT Indicator

3 RrcRdtSwch Switch of RRC Redirection Triggered by Radio

Resource Congestion

4 EutranCellType EUTRAN Cell Type


4.9.2.1 EmgCallRdtSwitch

OMC Path

View->Configuration Management->RNC NE->RNC Radio Resource

Management->Advanced Parameter Manage



Value=0, the function “RRC redirect of Emergency call” is forbidden

Value=1, the function “RRC redirect of Emergency call” is permitted

4.9.2.2 PriRedirectRat

OMC Path

View->Configuration Management->RNC NE->RNC Radio Resource Management





0: system won’t provide the information of redirection

1: Prior to Inter-Frequency, secondly to Inter-RAT (Prior to GSM Cell

2: Prior to Inter-Frequency, Secondly to Inter-RAT (PS prior to E-UTRA, CS Prior to

GSM)

3: Prior to Inter-RAT (Prior to GSM), Secondly to Inter-Frequency

4: Prior to Inter-RAT (PS prior to E-UTRA, CS Prior to GSM), Secondly to

Inter-Frequency

4.9.2.3 RrcRdtSwch

OMC Path


Utran Cell -> Advanced Parameter Manage -> UtranCell –> RrcRdtSwch



0: RRC Redirection will not be Triggered by Radio Resource Congestion

0: RRC Redirection will be Triggered by Radio Resource Congestion

4.9.2.4 EutranCellType

OMC Path

View->Configuration Management->RNC NE->RNC Radio Resource

Management->External Eutran Cell->External Eutran Cell XXX->Eutran Cell Type



0:EUTRAN FDD



1:EUTRAN TDD

4.10 Iu Overload Control

4.10.1 TigOR

OMC Path


Management->Advanced Parameter Manage ->Iu Interface Timers and Constants

Information->Timer for Ignoring all OVERLOAD Message or Signalling Point Congested

Information (TigOR) (s)

4.10.2 TinTR

OMC Path


Management->Advanced Parameter Manage ->Iu Interface Timers and Constants

Information->Timer for Not Allowing to Increase Traffic (TinTR) (s)

4.11 Deferred SIB11/12



1 DefSibSuptSwch Switch of Deferred SIB11/11bis/12 Support

2 IntraRptQSib3 Intra-frequency reporting quantity SIB3 when

SIB11/11bis/12 deferred reading


4.11.2.1 DefSibSuptSwch

OMC Path




Management->UtranCell->Cell Setup Parameters -> Switch of Deferred SIB11/11bis/12

Support



Value=0, the function “Deferred SIB11/12” is forbidden

Value=1, the function “Deferred SIB11/12” is permitted

4.11.2.2 IntraRptQSib3

OMC Path


Management->UtranCell->Advanced Parameter Manage ->UTRAN

Cell->Intra-frequency reporting quantity SIB3 when SIB11/11bis/12 deferred reading



This parameter indicates when SIB11/11bis/12 are deferred reading, the intra -frequency

reporting quantity for RACH report in RRC connection request message.0: CPICH

Ec/No,1: CPICH RSCP

4.12 Direct Tunnel



1 SupportDTSwitch Support DT Switch




4.12.2.1 SupportDTSwitch

OMC Path

Path: View->Configuration Management->RNC NE->RNC Ground Resource

Management->Transmission Configuration->NE Information Configuration->SGSN ->

Support DT Switch



Value=0, the function “ Direct Tunnel” is forbidden

Value=1, the function “ Direct Tunnel” is permitted

4.13 Call Re-establishment



1 TWaitRlRestore Time of Waiting for RADIO LINK RESTORE

INDICATION

2 TWaitActSetUpCmp Waiting time length for ACTIVE SET UPDATE

COMPLETE

3 WaitRbCompTimer

Time of Waiting for RB

Setup/Reconfiguration/Release Response over Uu

Interface

4 CsReestSwitch0

Switch of CS Call Re-establishment Triggered by

Receiving the CELL UPDATE Message from UE

when SRNC is in Stable Status

5 CsReestSwitch1

Switch of CS Call Re-establishment Triggered by


when SRNC is in Handover Flow

6 CsReestSwitch2 witch of CS Call Re-establishment Triggered by




when SRNC is in RAB Setup Flow

7 CsReestSwitch3 Switch of CS Call Re-establishment Triggered by

RAN Network when SRNC is in Stable Status


RAN network when SRNC is in Handover Flow


RAN network when SRNC is in RAB Setup Flow

10 PsReestSwitch0

Switch of PS Call Re-establishment Triggered by


when SRNC is in Stable Status

11 PsReestSwitch1

Switch of PS Call Re-establishment Triggered by


when SRNC is in Handover Flow

12 PsReestSwitch2

witch of PS Call Re-establishment Triggered by


when SRNC is in RAB Setup Flow

13 PsReestSwitch3 Switch of PS Call Re-establishment Triggered by

RAN Network when SRNC is in Stable Status


RAN network when SRNC is in Handover Flow


RAN network when SRNC is in RAB Setup Flow


4.13.2.1 TWaitRlRestore

OMC Path


Management->Advanced Parameter Manage -> RNC Radio Resource Management

-> Time of Waiting for RADIO LINK RESTORE INDICATION





The value is smaller, the probability of synchronization failure and the probability of call

drop may be increased.

The value is bigger, the probability of synchronization success may be increased, but

when the radio environment is bad, the RNC may wait too long time to unnecessary wait

and increase the waiting time to Re-establishment the service.

4.13.2.2 TWaitActSetUpCmp

OMC Path



-> Waiting time length for ACTIVE SET UPDATE COMPLETE



The value is smaller, the probability of receiving the ACTIVE SET UPDATE COMPLETE

may be decreases, and the probability of call drop may be increased.

The value is bigger, the probability of receiving the ACTIVE SET UPDATE COMPLETE

may be increased, however, when the radio environment is bad, the RNC may wait too

long time to unnecessary wait and increase the wait time to Re-establishment the service

4.13.2.3 WaitRbCompTimer

OMC Path



-> Time of Waiting for RB Setup/Reconfiguration/Release Response over Uu Interface





The value is smaller, the probability of receiving the RB Setup/Reconfiguration/Release

Response may be decreases, and the probability of call drop may be increased.

The value is bigger, the probability of receiving the RB Setup/Reconfiguration/Release

Response may be increased; however, when the radio environment is bad, the RNC may

wait too long time to unnecessary wait and increase the wait time to Re -establishment

the service.

4.13.2.4 CsReestSwitch0

OMC Path


Management->UtranCell->Advanced Parameter Manage->Utran Cell-> CsReestSwitch0



When RNC is in STABLE state and receive CELL UPDATE from UE, and UE have CS

service, when if Call Re-esstabilishment is allowed, set the value is 1; if not allowed, set it

0.


OMC Path





When RNC is in Handover procedure and receive CELL UPDATE from UE, and UE have

CS service, if Call Re-esstabilishment is allowed, set the value is 1; if not allowed, set it

0.




OMC Path





When RNC is in RAB setup procedure and receive CELL UPDATE from UE, and UE

have CS service, i f Call Re-esstabilishment is allowed, set the value is 1; if not allowed,

set it 0.


OMC Path





When RNC is in STABLE state and the condition of Call Re-esstabilishment triggered by

RNC is fulfilled, and UE have CS service, if Call Re-esstabilishment is allowed, set the

value is 1; if not allowed, set it 0.


OMC Path







When RNC is in Handover procedure and the condition of Call Re-esstabilishment

triggered by RNC is fulfilled, and UE have CS service, if Call Re-esstabilishment is

allowed, set the value is 1; if not allowed, set it 0.


OMC Path





When RNC is in RAB setup procedure and the condition of Call Re-esstabilishment

triggered by RNC is fulfilled, and UE have CS service, if Call Re-esstabilishment is


4.13.2.10 PsReestSwitch0

OMC Path


Management->UtranCell->Advanced Parameter Manage->Utran Cell-> PsReestSwitch0



When RNC is in STABLE state and receive CELL UPDATE from UE, and UE have only

PS service, when if Call Re-esstabilishment is allowed, set the value is 1; i f not allowed,

set it 0.




OMC Path





When RNC is in Handover procedure and receive CELL UPDATE from UE, and UE have

only PS service, if Call Re-esstabilishment is allowed, set the value is 1; if not allowed,

set it 0.


OMC Path





When RNC is in RAB setup procedure and receive CELL UPDATE from UE, and UE

have only PS service, if Call Re-esstabilishment is allowed, set the value is 1; if not

allowed, set it 0.


OMC Path







When RNC is in STABLE state and the condition of Call Re -esstabilishment triggered by

RNC is fulfilled, and UE have only PS service, if Call Re-esstabilishment is allowed, set

the value is 1; if not allowed, set it 0.


OMC Path





When RNC is in Handover procedure and the condition of Call Re-esstabilishment

triggered by RNC is fulfilled, and UE have only PS service, if Call Re-esstabilishment is



OMC Path





When RNC is in RAB setup procedure and the condition of Call Re-esstabilishment

triggered by RNC is fulfilled, and UE have only PS service, if Call Re-esstabilishment is




5 Counter and Alarm

5.1 Counter List

Table 5-1 Connection Management Counter

Counter No. Description

C310080001

Number of attempted RRC connection

establishment,by cause

C310080002

C310080003

C310080004

C310080005

C310080006

C310080007

C310080008

C310080009

C310080010

C310080011

C310080012

C310080013

C310080014

C310080015

C310080016

C310080017

C310080018

C310080019

C310080020

C310080021

C310080022

C310080023

C310080024



C310080025

C310080026

C310080027

C310080028

C310080029

C310080030

C310080031

C310080032

C310080033

C310080034

C310080035

C310080036

C310080037

C310080038

C310080039

C310080040

C310080041

C310080042

C310080043

C310080044

C310080045


establishment,by CallType

C310080046

C310080047

C310080048

C310080049

C310080050

C310080051


establishment,by Domain

C310080052

C310080053

C310080054

C310080055 Number of attempted RRC connection

establishment,by UE Capability C310080056



C310080057


establishment,by UE AS Release

C310080058

C310080059

C310080060

C310080061

C310080062

C310080063

Number of RRC connection preparation

failure,by fail cause

C310080064

C310080065

C310080066

C310080067

C310080068

C310080069

C310080070

C310080071

C310080072

C310220073

C310220074

C310220075

C310080076

C310080077

C310080078

C310080079

C310080080


failure,by establishment cause

C310080081

C310080082

C310080083

C310080084

C310080085

C310080086

C310080087

C310080088



C310080089

C310080090

C310080091

C310080092

C310080093

C310080094

C310080095

C310080096

C310080097

C310080098

C310080099

C310080100

C310080101

C310080102


failure,by call type C310080103

C310080104

C310080105 Number of RRC connection preparation

failure,by domain C310080106

C310080107 Number of RRC connection Refuse for

Conversational Call C310080108


Voice C310080110

C310080111 Number of RRC connection preparation

success,by Channel type C310080112

C310080113


success,by Direct

C310080114

C310080115

C310080116

C310080117

C310080118

C310080119

C310080120



C310080121

C310080122

C310080123

C310080124

C310080125

C310080126

C310080127

C310080128

C310080129

C310080130

C310080131

C310080132

C310080133

C310080134

C310080135

C310080136

C310080137

C310080138

C310080139

C310080140

C310080141

C310080142

C310080143

C310080144

C310080145

C310080146

C310080147

C310080148

C310080149

C310080150

C310080151

C310080152



C310080153

C310080154

C310080155

C310080156

C310080157

C310080158

C310080159

C310080160

C310080161

C310080162

C310080163

C310080164

C310080165

C310080166

C310080167

Number of RRC access fail,by fail cause C310080168

C310080169

C310080170

Number of RRC access Success,by

establishment cause

C310080171

C310080172

C310080173

C310080174

C310080175

C310080176

C310080177

C310080178

C310080179

C310080180

C310080181

C310080182

C310080183

C310080184



C310080185

C310080186

C310080187

C310080188

C310080189

C310080190

C310080191

C310080192

Number of RRC access Success,by call

type C310080193

C310080194

C310080195 Number of RRC access Success,by

domian C310080196

C310080197 Number of RRC access Success,by UE

Capablity C310080198

C310080199

Number of RRC access Success,by UE

AS Release

C310080200

C310080201

C310080202

C310080203

C310080204

C310080205

Number of RRC access Success,by RRC

establish time

C310080206

C310080207

C310080208

C310080209

Number of RRC access Success,by UE

Phy Capability Category

C310080210

C310080211

C310080212

C310080213

C310080214

C310080215

C310080216



C310080217

C310080218

C310080219

C310080220

C310080221

C310080222

C310080223

C310080224

C310080225

C310080226

Number of Triggered RRC connection

re-establishment

C310080227

C310080228

C310080229

C310080230

C310080231

C310080232

C310080233

C310080234


re-establishment

C310080235

C310080236

C310080237

C310080238

C310080239

C310080240

C310080241

C310080242

Number of failed RRC connection

re-establishment C310080243

C310080244

C310080245


re-establishment C310080246

C310080247

C310080248 Number of failed RRC connection



C310080249 re-establishment,by traffic

C310080250

C310080251

C310555127

RRC Connection Establishment

Procedures

C310555128

C310555129

C310555130

C310555131

C310555132

C310555133

C310555134

C310555135

C310555162

C310555163

C310555164

C310555171

C310555172

C310555136

RRC Connection Release Procedures

C310555137

C310555138

C310555139

C310555140

C310555141

C310555142

C310555143

C310555144

C310555145

C310555146

C310555147

C310555148

C310555149

C310555150



C310555151

C310555152

Cell Paging Procedures

C310555153

C310555154

C310555155

C310555156

C310555157

C310555158

C310555159

C310555160

C310555161

C310555165

Cell Security Procedures

C310555166

C310555167

C310555168

C310555169

C310555170

C310565185

Radio Bearer Reconfiguration Procedures

Signaling Statistic

C310565186

C310565187

C310565188

C310565189

C310565190

C310565191

C310565192

C310565193

C310565194

C310565195

C310565196

C310595406

Radio Link Setup Procedures C310595407

C310595408



C310595409

C310595410

C310595411

C310595412

C310595413

C310595414

C310595415

C310595416

C310595417

C310595418

C310595419

C310595420

Counter No. Description

C301861019


establishment

C301861020

C301861021

C301861022

C301861023

C301861024

C301861025

C301861026

C301861027

C301861028

C301861029

C301861030

C301861031

C301861032

C301861033

C301861034

C301861035



C301861036

C301861037

C301861038

C301861081

C301861082

C310080023

C310080024

C310080025

C310080026

C310080027

C310080028

C310080029

C310080030

C310080031

C310080032

C310080033

C310080034

C310080035

C310080036

C310080037

C310080038

C310080039

C310080040

C310080041

C310080042

C310080043

C310080044

C310080048

C310080049

C310080050

C310080051

C310080052



C310080053

C310080054

C310080056

C310080057

C310080058

C310080059

C310080060

C310080061

C310080062

C310080063


success

C310080064

C310080065

C310080066

C310080067

C310080068

C310080069

C310080070

C310080071

C310080072

C310220073

C310220074

C310220075

C310080076

C310080077

C310080078

C310080079

C310080080

C310080081

C310080082

C310080083

C310080084

C310080085



C310080086

C310080087

C310080088

C310080089

C310080090

C310080091

C310080092

C310080093

C310080094

C310080095

C310080096

C310080097

C310080098

C310080099

C310080100

C310080101

C310080102

C310080103

C310080104

C310080105

C310080106

C310080111

C310080112

C310080113

C310080114

C310080115

C310080116

C310080117

C310080118

C310080119

C310080120

C310080121



C310080122

C310080123

C310080124

C310080125

C310080126

C310080127

C310080128

C310080129

C310080130

C310080131

C310080132

C310080133

C310080134

C310080135

C310080136

C310080137

C310080138

C310080139

C310080140

C310080141

C310080142

C310080143

C310080144

C310080145

C310080146

C310080147

C310080148

C310080149

C310080150

C310080151

C310080152

C310080153



C310080154

C310080155

C310080156

C310080157

C310080158

C310080159

C310080160

C310080161

C310080162

C310080163

C310080164

C310080165

C310080166

C310080167

Number of RRC access fail C310080168

C310080169

C310080170

Number of RRC access Success

C310080171

C310080172

C310080173

C310080174

C310080175

C310080176

C310080177

C310080178

C310080179

C310080180

C310080181

C310080182

C310080183

C310080184

C310080185



C310080186

C310080187

C310080188

C310080189

C310080190

C310080191

C310080192

C310080193

C310080194

C310080195

C310080196

C310080197

C310080198

C310080199

C310080200

C310080201

C310080202

C310080203

C310080204

C310080209

C310080210

C310080211

C310080212

C310080213

C310080214

C310080215

C310080216

C310080217

C310080218

C310080219

C310080220

C310080221



C310080222

C310080223

C310080224

C310080225

C310080226

Number of Triggered RRC connection

re-establishment

C310080227

C310080228

C310080229

C310080230

C310080235


re-establishment

C310080236

C310080237

C310080238

C310080248


re-establishment

C310080249

C310080250

C310080226


establishment for UE supported HSDPA

C301240926

Number of RRC connection release on

DCCH,by cause

C301240927

C301240928

C301240929

C301240930

C301240931

C301240932

C301240933

Number of RRC connection release on

CCCH,by cause

C301240934

C301240935

C301240936

C301240937

C301240938



C301240939

C301480445


establishment,by cause( in a certain cell)

C301480446

C301480447

C301480448

C301480449

C301480450

C301480451

C301480452

C301480453

C301480454

C301480455

C301480456

C301480457

C301480458

C301480459

C301480460

C301480461

C301480462

C301480463

C301480464

C301481551

C301481552

C301481403

C301481404

C301481497

C301480465

Number of successful RRC connection

establishment,by cause( in a certain cell)

C301480466

C301480467

C301480468

C301480469

C301480470



C301480471

C301480472

C301480473

C301480474

C301480475

C301480476

C301480477

C301480478

C301480479

C301480480

C301480481

C301480482

C301480483

C301480484

C301481553

C301481554

C301481405

C301481406

C301481498


re-establishment( in a certain cell)

C301480489


re-establishment( in a certain cell) C301480490

C301480491

C301481288 Total time of RRC connection

establishment( in a certain cell)

C301481289 Max time of RRC connection

establishment( in a certain cell)

C301481337 Number of RRC connection Release for

abnormal Cause( in a certain cell)


Conversational Call( in a certain cell) C301481339

C301481340 Number of RRC connection Request for



HSDPA UE( in a certain cell)


Voice( in a certain cell) C301481408

C301240940 Number of RRC connection release

complete

C301480485


establishment,by cause C301480486

C301480487

5.2 Alarm List

This feature has no related alarm.

6 Glossary

D

DRX Discontinuous Reception

DSAR Domain Specific Access Restriction

F

FD Feature Description

FP Frame Protocol

I

IuUP Iu Interface User Plane

M

MIB Master Information Block

N



NAS Non Access Stratum

Np Number of PI

O

OMCR OMC of the RNC

P

PI Page Indicator

PO Page Occasion

R

RAB Radio access bearer

RAT Radio Access Technology

RL Radio Link

RRC Radio Resource Control

S

SB Schedule Block

SIB system information block

T

TFC Transport Format Combination

7 Reference

ZTE UMTS Load Balance Feature Guide

ZTE UMTS IU Flex Feature Guide

148504581 ZTE UMTS Connection Management Feature Guide V6!1!201204

Documents

Transcript of 148504581 ZTE UMTS Connection Management Feature Guide V6!1!201204