14wcdma Po b en Accesspagingoptimization 55 130915133550 Phpapp02

8/20/2019 14wcdma Po b en Accesspagingoptimization 55 130915133550 Phpapp02

1/55

Access&Paging Optimization

ZTE CORPORATIONZTE Plaza, Keji Road South,Hi-Tech Industrial Park,

Nanshan District, Shenzhen,P. R. China518057Tel: (86) 755 26771900 800-9830-9830Fax: (86) 755 26772236URL: http://support.zte.com.cn

E-mail: [email protected]

http://support.zte.com.cn/mailto:[email protected]:[email protected]://support.zte.com.cn/


2/55


3/55

Contents

Chapter 1..........................................................................1

Overview ..........................................................................1

Introduction ...................................................................1

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

RRC Connection Establishment and Release ..............................2

Paging.................................................................................2

NAS Message Retransmission .................................................3

Encryption ...........................................................................4

Integrity Protection ...............................................................4

Radio Connection Monitoring ..................................................5

Radio Connection Reestablishment ..........................................5

High-speed Signaling Bearer...................................................5

System Broadcast ...........................................................6

System Broadcast Schedule and Delivery .................................6

Delivery Content Description of SIBs........................................8

RRC Connection Establishment and Release ......................16

Abnormal Process Handling of RRC Connection Establishment.... 19

RRC Connection Release ...................................................... 19

Paging .......................................................................21

Paging Flow ....................................................................... 21

PAGING TYPE 1 .................................................................. 22

PAGING TYPE 2 .................................................................. 24 Radio Connection Monitoring...........................................25

Radio Connection Reestablishment ..................................27

Chapter 2........................................................................29

Parameters and Configuration ......................................29

System Information Broadcast Parameters .......................29

SIB1 Parameter List ............................................................ 29

SIB1 Parameter Configuration............................................... 31


4/55

Connection Establishment and Release Parameters ............41

Parameter List ....................................................................41

Parameter Configuration.......................................................42

Paging Parameter..........................................................48

Parameter List ....................................................................48

Parameter Configuration.......................................................48


5/55

C h a p t e r

1

Overview

Introduction

System Broadcast

System broadcast fuction periodically transmitting the systeminformation to cells in a broadcast mode and accordingly updatethe system information. The system information is broadcast onBCH, including the following contents:

Network information such as PLMN ID, LA and RA

Timers and counters related with RRC connection

UTRAN Registration Area (URA) configuration information

Cell selection and cell re-selection parameters

Common channel configuration parameters such as FACH, PCHand RACH

UL interference information of auxiliary power control

UE measurement control message in the Idle or common

channel status

Neighbor cell configuration parametersAGPS location information

The contents of system information are involved in variousSystem Information Blocks (SIB). Except that the SIB7(including UL interference information) can be auto-measured,

encoded and transmitted by the Node B, all SIBs are controlledand encoded by RNC.

Confidential and Proprietary Information of ZTE CORPORATION 1


6/55


RRC Connection Establishment andRelease

This function manages establishment and release of RadioResource Control (RRC) connection between UTRAN and UE. Itestablishes the signaling bearer from UE to UTRAN access pointand provides the signaling transmission channel for the UE andUTRAN. When the UE needs to establish connection with thenetwork such as LA or RA update, service request and paging

response, the UE originates the RRC connection setup requeston RACH according to the parameter information of systembroadcast the UTRAN assigns related resources to the UE toestablish Signaling Radio Bearer (SRB). After the process of RRCconnection setup is completed, the UE generally establishes lu

connection with the CN to fulfill LA and RA update and serviceprocess, and meanwhile SRB provides the signaling transmissionchannel between UE and CE. The UTRAN monitors lu connectionstate and radio connection state of the UE. If all lu connectionsare released or radio connection with the UE is interrupted, the

UTRAN accomplishes RRC connection release to release allresources assigned for the UE.

Paging

When the CN has service requirements, the system uses thepaging function to trigger connection setup between UE and CN.For example, when the UE needs to receive the SMS or MMSinformation or other users call in this UE, the CN transmits the

paging message to the RNC over the lu interface. And the RNCselects different areas to transmit the paging message to the UE

based on the RRC connection state of UE.

UE in the IDLE status: The RNC does not detect the detailedlocation information of UE and thus transmits the paginginformation to the whole LA or RA according to the LA or RAinformation carried in the CN paging message.

UE in the PCH status: The RNC detects the URA locationinformation of UE and transmits the paging message to thewhole URA.

UE in the FACH or DCH status: The RNC detects the celllocation information of UE and transmits the paging message

to the whole cell.

The following paging scenarios originated by RNC aresupportable:

When the packets exist in the DL buffer area, the RNC

transmits the paging message to trigger the UE from theURA_PCH status to the CELL_FACH status to establish

service bearer for DL data transmission.

2 Confidential and Proprietary Information of ZTE CORPORATION


7/55

Chapter 1 0BOverview

When the system information changes, the RNC transmitsthe paging message to inform all UEs in the Idle or PCH

status within the cell of system information changed.

When it is required to interrupt the RRC connection of UE in

the PCH status, the RNC transmits the paging message torelease the RRC of UE.

Two paging modes such as PAGING TYPE 1 and PAGING TYPE 2are supportable:

For the UE in the IDLE or URA_PCH status, the RNCtransmits PAGING TYPE1.

For the UE in the CELL_FACH or CELL_DCH status, the RNCtransmits PAGING TYPE2.

NAS Message RetransmissionThe UTRAN is an essential network of signaling transmission onthe Non-Access Stratum (NAS) layer between UE and CN. TheNAS signaling is used in the control process such as UE locationupdate, authentication, call setup and release, and also used intransfer of SMS data. The NAS signaling and SMS datatransmitted between UE and CN are not resolved and processed

by UTRAN. The UTRAN assumes the NAS signaling and SMS dataas the CE content of the direct-transfer message defined in the

RANAP and RRC protocols and transparently transmits thembetween CN and UE. Three types of direct-transfer message are

available.

Initial direct transfer: Once the UTRAN receives theinitial-direct transfer message from the UE, the RNCestablishes connection with the Iu interface of MSC or SGSN(SCCP) according to the tag of CN domain (PS or CS) in themessage, and attaches the NAS message to the initial UE

message to transmit to the corresponding MSC or SGSN.Meanwhile, the RNC records the binding relation between

SCCP connection and UE RRC connection to establish achannel for the subsequent NAS message between UE andCN.

UL direct transfer: When receiving the uplink direct-transfermessage from the UE, the UTRAN attaches the NAS messageto the direct transfer message according to the tag of CNdomain in the message and then transmits to thecorresponding MSC or SGSN.

DL direct transfer: When receiving the direct transfermessage from the CN, the UTRAN attaches the NAS messageto the downlink direct-transfer message according to thecorresponding relation of SCCP and RRC connection, andthen transmits to the related UE.



8/55


When receiving the lu connection release message from the CN,the RNC releases the lu connection of CN and cancels the

binding relation of SCCP and RRC connection.

Encryption

This function performs encryption of users’ service data and

signaling data being transmitted over the Un interface, toguarantee confidentiality of user communication between RNCand UE. ZTE RAN supports the encryption algorithm UEA0 andUEA1: UEA0 indicates that the Uu-interface data is notencrypted; UEA1 is based on the KASUMI algorithm, f8 Isperforming encryption and decryption. The CN starts encryptionprotection and configures the type of ecryption is going to beused. The CN notifies the RNC to enable the encryption by theRANAP security mode command which carries the key of theencryption algorithm. According to its encryption ability, the UE

encryption algorithm ability and the priority of selectableencryption algorithms configured by the CN, the RNC selects a

proper encryption algorithm, and enables the encryption by theRRC security mode command. After enabling the encryption,when the RNC or UE is sending the data, with the help of theencryption key and the variables with the transmitted-datachange, the encryption function executes the f8 algorithm toencrypt the transmitted data. The receiver uses the samealgorithm to decrypt the data. The process of encryption anddecryption is executed on the RLC layer (AM or UM mode) or

MAC layer (TM mode).

Integrity Protection

To protect the signaling from the third-party’s hostile attack, thefunction provides the checking mechanism for the Un interfacesignaling over the air interface. ZTE RAN supports a uniqueintegrity protection algorithm UIA1 defined in 3GPP – based onthe KASUMI algorithm and the integrity protection performed byf9. The CN configures whether to enable the integrity protection

function. The CN informs the RNC to enable the integrityprotection through the command process of RANAP securitymode, the message carrying the secret key of the integrity

protection algorithm. The RNC enables the integrity protectionthrough the command process of RRC security mode. If theintegrity protection is enabled, during transmitting the RRCmessage, the RNC or UE first uses the f9 algorithm to calculatethe identification code MAC-I for the integrity protectionaccording to the secret key and transmitted message. Then theRNC or UE attaches the MAC-I to the message to be transmittedand transmits it. The receiving end must use the same algorithmand secret key with the transmitting end to calculate the

identification code XMAC-I of the received message and



9/55


compares the calculated value with the received MAC-I. If thetwo values are identical, the receiving message is considered to

be correct; or else, the receiving message is discarded. Not allUn interface signaling is protected. ZTE RAN executes the RRC

message of integrity protection abiding by the 3GPP TS25.331protocol.

Radio Connection Monitoring

This function monitors the radio connection states of UEs havingestablished RRC. For example, due to poor radio quality or othercauses, the RNC determines that radio connection between UEand network has interrupted, and immediately releases allresources assigned to the UE, including service-established RBresources and RRC connection. To monitor the radio connectionstate, the following mode supports:

The Node B monitors the RL state.

The RNC monitors the RLC connection state.

The RNC monitors the cell update message of UE.

The RNC monitors the UE keep-alive timer.

After releasing the radio resources, the RNC transmits the lu

release request message to the CN over the lu interface andinforms the CN to release the corresponding RAB resource.

Radio Connection Reestablishment

Because of sudden interference or abrupt change of radioenvironment, the UE on DCH suffers short interruption of radioconnection and does not continue performing services withoutnetwork signals. However, the UE recovers the network signalsbefore the UTRAN detects interruption of the radio connection.For this scenario, the UE transmits the cell update messagecarrying the cause of Radio link failure or RLC unrecoverableerror (only corresponding to the service RB) to attempt to

reestablish connection with the network. The RNC supports thefunction of reestablishing the radio connection between UE andUTRAN and recovering communication under the situation of notreleasing the previous RRC and lu connections. For userexperience, the reestablishing process brings about short-timeservice interruption, but call drop never occurs.

High-speed Signaling Bearer

The function supports the usage of 13.6 kbps Signaling RadioBearer (SRB) in the process of call establishment. When service



10/55


establishment is completed, 3.4Kbps SRB is recovered to saveradio resources. 13.6 kbps high-speed SRB can shorten the time

of call establishment up to 1s in various scenarios. TheInitRrcLBSw parameter enables and controls this function.

System BroadcastThe RNC manages construction and broadcast of the systemmessage. The system message, including NAS information, cellcommon-channel configuration information, cell selection andreselection parameter, initial access as well as measurementcontrol and location information, provides the necessary UTRANinformation for the processes of Location Area Update (LAU),Route Area Update (RAU) and RRC establishment originated by

EU under the cell.

The system information consists of three types: MasterInformation Block (MIB), Schedule Block (SB) and SystemInformation Block (SIB).

System Broadcast Schedule andDelivery

The MIB can save the schedule information of SB and SIB. The

SB saves the schedule information of SIB, including the SB1 andSB2. The SIB saves the detailed content of the systeminformation message. ZTE UTRAN system supports the SB1, SB2,

SIB3, SIB5, SIB7, SIB11 and SIB18. This version does notsupport the SIB11 bis. When the cell has been established oradded, the system broadcasts the system message. Update ofthe system information or timeout of the timer also triggersbroadcast of the system message. See Figure 1.



11/55


F I G URE 1 SYST EM B R O A D C A S T

When cell establishment is completed or the system informationis updated, the system first schedules system information

broadcast to confirm the transmission period of variousinformation blocks. According to importance of SIBs, the system

divides SIBs into two priorities. To promote the broadcastfrequency of important system information, the first-priority SIB

is scheduled by MIB and the second-priority SIB scheduled bySB1. Less-content SIBs can be connected in tandem in the sameTTI to transmit, while more-content SIBs can be partitioned intosections to transmit, such as the SIB5 and SIB11. Refer to thefollowing detailed classification.

The MIB is used to schedule the SB1, SIB1, SIB2, SIB3, SIB5

and SIB7.

The MIB is used to schedule the SIB11 and SIB18.

Except MIB, all SIBs are divided into two levels according toimportance. The level stands for the priority of filling the systeminformation. See Table 1.

T A B L E 1 SCHEDUL I NG L E V E L O F SYST EM I NF O RM AT I O N B L O C K

Level 1IB scheduled by MIB:SB1,SB2,SIB1,SIB2,SIB3,SIB5,SIB7

Level 2 IB scheduled by SB1: SIB11, SIB18

The SIB broadcast period relation of each level: Lev2 period>=Lev1 period

According to the scheduling principles, the RNC fills the system

information and transmits it to the Node B by SYSTEMINFORMATION UPDATE REQUEST. When receiving the SYSTEM



12/55


INFORMATION UPDATE RESPONSE message, the RNC assumesthat the system information is successfully updated. After

receiving the system information, the Node B broadcasts allinformation blocks on BCH according to a given scheduling

period. When the system information is updated, the systeminforms UEs respectively in the IDLE, PCH and FACH statesthrough different modes, as follows:

Inform UEs respectively in the IDLE and PCH states bypaging: The RNC transmits PAGING TYPE 1 to UEs; the CEBCCH modification info in the message indicates the system

information updated.

Inform UEs in the FACH state by system information changeindication: The system transmits SYSTEM INFORMATIONCHANGE INDICATION to UEs; the CE BCCH modification infoin the message indicates the system information updated.

Delivery Content Description of SIBs

SIB1

The SIB1 consists of CN information, timers and counters relatedto UEs. CEs configured by OMCR are as follows:

T300: Indicates the waiting duration after the UE transmitsthe RRC CONNECTION SETUP REQUEST message. The timer

is enabled after the UE transmits RRC CONNECTIONREQUEST (This example is excluded: If the cause of the RRCconnection request is MBMS Reception, T318 is enabled,instead of T300; the T318 value is a fixed value 1000 msconfigured in the RNC). If RRC CONNECTION SETUP isreceived, the timer stops. When the timer expires and the

retransmission times are less than N300, RRC CONNECTIONSETUP REQUEST is retransmitted.

N300: Indicates the maximum of retransmission times of theRRC CONNECTION SETUP REQUEST message. If T300 expires and the retransmission times are equal to or morethan N300, RRC CONNECTION SETUP is still not received and

then the UE enters the IDLE state.

T312Idle: Indicates the waiting time of “In Sync” receivedfrom L1 when the UE in the IDLE state is establishing thededicated physical channel. While the UE is establishing thededicated physical channel, this timer is enabled. While theUE detects that the number of Layer 1 receiving “In Sync” isequal to that of N312Idle, the timer is disabled. If the timerexpires, the physical channel fails to establish.

N312Idle: Indicates the number of “In Sync” continuouslyreceived from L1 before the UE succeeds in establishing the

dedicated physical channel.



13/55


T302: Indicates the waiting time after the UE transmits theCELL UPDATE or URA UPDATE message. While the UE is

transmitting CELL UPDATE or URA UPDATE, this timer isenabled. When the UE is receiving CELL UPDATE CONFIRM or

URA UPDATE CONFIRM, the timer is disabled. If the timerexpires and the number of retransmitting CELL UPDATE orURA UPDATE is less than N302, the UE retransmits CELLUPDATE or URA UPDATE.

N302: Indicates the maximum of retransmitting the CELLUPDATE or URA UPDATE message. When T302 expires and

the number of UE transmitting CELL UPDATE or URA UPDATEis equal to or more than N302, the UE enters the IDLE state.

T304: Indicates the waiting time after the UE transmits theUE CAPABILITY INFORMATION message. While the UE istransmitting UE CAPABILITY INFORMATION, this timer isenabled, While the UE is receiving UE CAPABILITYINFORMATION confirmed, the timer is disabled. If the timerexpires and the number of UE transmitting UE CAPABILITY

INFORMATION is less than N304, the UE retransmits UECAPABILITY INFORMATION.

N304: Indicates the maximum of retransmitting the UECAPABILITY INFORMATION message. When T304 expires andthe number of retransmitting UE CAPABILITY INFORMATIONis equal to or more than N304, the UE enables the CELLUPDATE process.

T305 : Indicates the period duration of UE performingperiodical cell update or URA update in the CELL_FACH,

CELL-PCH or URA_PCH state. When the UE is entering theCELL_FACH, CELL-PCH or URA_PCH state, this timer isenabled. While the UE is receiving the CELL UPDATEconfirmation or URA UPDATE CONFIRM message, the timer isdisabled. If the timer expires and the UE is in the servicearea, the UE transmits the CELL UPDATE message. If thetimer expires and the UE is out of the service area, the UE

enables the T307 timer.

T307 : Indicates the waiting timer of cell reselection after theUE disengages from the service area. When this timerexpires, the UE returns to the IDLE state.

T308: Indicates the waiting time after the UE in theCELL_DCH state transmits the RRC CONNECTION RELEASE

COMPLETE message. After the UE transmits RRCCONNECTION RELEASE COMPLETE, this timer is enabled. Ifthe timer expires and the number of UE transmitting RRCCONNECTION RELEASE COMPLETE is less than N308, the UEretransmits the RRC CONNECTION RELEASE COMPLETEmessage.

N308: Indicates the maximum of UE retransmitting RRCCONNECTION RELEASE COMPLETE. If T308 expires and the

number of UE transmitting RRC CONNECTION RELEASECOMPLETE is equal to or more than N308, the UE enters the

IDLE state.



14/55


T309: Indicates the waiting time after the UE enabling theaccess request to other RATs (such as, GSM). When the UE

receives the CELL CHANGE ORDER FROM UTRAN message,this timer is enabled. When the UE successfully receives the

ACK message of connection setup request in a new cell, thetimer is disabled. If the timer expires, the UE reaccesses theprimary UTRAN.

T312 Connected : A timer used in the connection mode;indicates the waiting time of receiving “In Async” from L1during the UE in the connection mode establishing the

dedicated physical channel. When the UE starts establishingthe dedicated channel, this timer is enabled. When the UE

detects that the number of L1 “In Async” is equal to thatdefined in N312, the timer is disabled. If the timer expires,the physical channel fails to establish.

N312Connected : A counter used in the connection mode;indicates the number of UE in the Connection modecontinuously receiving “In Sync” from L1 before successful

establishment of dedicated physical channel.

T313: Indicates the waiting time of the UE in the DCH stateconfirming asynchronization of the established DPCCH. Whenthe UE in the DCH state continuously receives “In Async”N313 times from L1, this timer is enabled. When the UE inthe DCH state continuously receives “In Sync” N315 timesfrom L1, the timer is disabled. If the timer expires, all radiolinks related to “In Async” fail.

N313: Indicates the maximum of UE continuously receiving

“In Async” from L1.

N315 : Indicates the maximum of UE continuously receiving “In Sync” from L1 under the T313-activated status.

T314: Defines RL failure and indicates the time of the RB(related to T314) waiting for completion of cell updateprocess. During establishing a RB, the system assumes theRB uses T314 or T315. When the radio link fails and thecurrent RB uses T314, this timer is enabled. When theprocess of cell update is completed, the timer is disabled. If

the timer expires, the UE first judges whether T302 is stillrunning. If yes, the UE continues waiting the CELL UPDATE

CONFIRM or URA UPDATE CONFIRM message; if no, the UE judges whether T315 is running. If T315 is still running, theUE only releases the RAB resources related to T314. If T315stops running, the UE releases all RAB resources to enter theIDLE state.

T315 : Defines RL failure and indicates the time of the RB(related to T315 ) waiting for completion of cell updateprocess. During establishing a RB, the system assumes the

RB uses T314 or T315. When the radio link fails and thecurrent RB uses T315 , this timer is enabled. When the

process of cell update is completed, the timer is disabled. IfT315 expires, the processing method is similar to that of



15/55


T314. The UE performs corresponding processing accordingto the running status of T302 and T314.

T316: Indicates the waiting time for cell selection/reselectionafter the UE in the CELL_PCH or URA_PCH state is out of the

service area. When the UE in the PCH state is out of theservice area, this timer is enabled. When the UE is in theservice area, the timer is disabled. If the timer expires andthe UE is in the service area, cell update is enabled. If the UE

is out of the service area, the T317 is enabled; until the UEin the FACH state is in the service area, the cell update is

enabled.

T317 : Indicates the waiting time for cell selection/reselectionafter the UE in the CELL_FACH state is out of the servicearea. When T316 expires or when the UE in the FACH state isout of the service area, this timer is enabled. When the UE isin the service area, the timer is disabled.

MCC : Mobile country code

MNC : Mobile network code

CnDomain: CN domain supported

T3212Cs: The timer of periodical location update. Thelocation update is classified into two types, one of which isoriginated by the UE after finding change of LAC and the

other of which is periodical update of UE specified by thesystem. T3212Cs is a timer of periodical location update.

ATTIndCs: Switching variable; indicates whether the IMSI

ATTACH and DETACH flows are adopted. NMOPs: Indicates the mode of network operation. The

network mode Ⅰ indicates the Gs interface exists between

MSCServer and SGSN; the network mode Ⅱ indicates the Gs

interface does not exist.

Kcs: The cycle length coefficient of CS-domain discontinuousreceiving. While counting the paging occasion, the UE in theIDLE or PCH state monitors the PICH within the durationspecified in the this parameter.

Kps: The cycle length coefficient of PS-domain discontinuousreceiving. While counting the paging occasion, the UE in the

IDLE or PCH state monitors the PICH within the durationspecified in this parameter.

MbmsModPrdCoeff: The period coefficient of MBMSmodification.

The preceding parameters can be configured by OMCR.

SIB2

The SIB2 indicates the URA ID of the cell, used for URA updateof the UE in the URA_PCH status. The following CEs can be

configured by OMCR. See Table.



16/55


T A B L E 2 S I B 2 CE CO NF I G URED BY OMCR

Name Description

URANum UTRAN registration area number

URA[4] UTRAN registration area ID

SIB3/SIB4

The SIB3 and SIB4 fill the parameters related to cell selectionand reselection. The SIB3 fills the information required by theUE in the IDLE state and the SIB4 fills the information requiredby the UE in the CONNECT state (on FACH and DCH, controlledby the measurement strategy). If the SIB4 is not delivered, theSIB3 also serves the UE in the CONNECT state. The Sib3orSib4 parameter (SIB3 broadcast or SIB4 broadcast) can be

configured on the OMCR. Currently, the SIB4 does not broadcastand thus the Sib3orSib4 is set to 0 (broadcast over the SIB3).

The following CEs can be configured by OMCR. See Table 3.

T A B L E 3 S I B 3 / S I B 4 CE CO NF I G URED BY OM CR

Name Description

Cid Cell ID

QualMeas Measurement Quantity for Cell Selection andReselection

SIntraSearchP

re

Sintrasearch whether to configure the tag

(Sintrasearch Configuration Tag)

SIntraSearch Co-frequency measurement trigger thresholdduring cell reselection (Sintrasearch)

SInterSearchP re

Whether to configure the Sintersearch parameter(Sintersearch Configuration Tag)

SInterSearch Inter-frequency measurement trigger thresholdduring cell reselection (Sintersearch)

SSearchHCSPre

Whether to configure the SsearchHCS parameter(SsearchHCS Configuration Tag)

SSearchHCS Measurement trigger threshold during HCS cell

reselection (SsearchHCS)SSearchRat Inter-system measurement trigger threshold during

cell reselection (Ssearch,RAT)

SHCSRatPre Whether to configure the SHCS and RATparameters (SHCS, RAT Configuration Tag)

SHCSRat Inter-system cell measurement threshold duringHCS cell reselection (SHCS,RAT)

SLimitRat High-HCS-priority inter-system cell measurementthreshold during cell reselection (Slimit,SearchRAT)

QQualMin Minimum level of cell quality (Qqualmin)

QRxLevMin Minimum receiving level threshold of cell



17/55



Name Description

(Qrxlevmin)

DltaQRxLevMi nPr

Whether to configure the minimum receiving levelthreshold gain of cell (DeltaQrxlevmin ConfigurationTag)

DltaQRxLevMi n

Minimum receiving level threshold gain of cell(DeltaQrxlevmin)

SIB5/SIB6

The SIB5 and SIB6 are used to configure the common

transmission channel and common physical channel. The SIB5fills the auxiliary common control PCH configuration parametersused in the IDLE state and the SIB6 fills the common PCH or

sharing PCH configuration parameters used in the connectionstate. The UE in the IDLE state uses the configuration of SIB5and in the connection state uses the configuration of SIB6.Without the SIB6, the contents of SIB5 are instead in theconnection state. The parameter SIB5ORSIB6 (SIB5 broadcast

or SIB6 broadcast) can be configured on the OMCR. Currently,the SIB6 does not broadcast and thus SIB5ORSIB6 is configured

to 0 (SIB5 broadcast). The following CEs can be configured byOMCR. See Table 4.

T A B L E 4 S I B 5 / S I B 6 CE C O NF I G URED BY OMCR

Name Description

TfsIndex

Transmission format index (TFS Index), used toconfigure the transmission channel indicationsincluding a set of transmission format parameterssuch as channel type, transmission formation No.,transmission block No., transmission time interval,coding rate and 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

MichPwr MICH Power(dB)

MichChCode MICH Channelisation Code No.

SttdInd MICH STTD Indicator

SttdInd AICH STTD Indicator


18/55



Name Description

ChCode AICH Channelisation Code No.

AichTranTime AICH Transmission Timing

AichPwr AICH Power

SCCPCHUsage SCCPCH Usage

SccpchOffset S-CCPCH Frame Timing Offset

MplexPos Indicates whether the multiplexing position fromthe transmission channel to physical channel isfixed or flexible.

PCHInd Indicator for S-CCPCH Carrying PCH

DlScraCode S-CPICH Scrambling Code

ChCode S-CPICH 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

SttdInd S-CCPCH STTD Indicator

Signature Available Signature

AvailSubChanN um

PRACH Available Subchannel Number

AvailableSF PRACH Available SF

PreamScraCode PRACH Preamble Scrambling Code

PunctLimit Puncturing Limit

SignalFach FACH Usage

TfcsIndexTransmission format combination set index (TfcsIndex): Both S-CCPCH and PRACH are configured.

CtfcNum

Transmission format combination set No. (CTFCNumber): Both S-CCPCH and PRACH areconfigured.

Ctfc

Transmission format combination ID (CTFC Id):

Both S-CCPCH and PRACH are configured.

DlScraCode (S-CCPCH) Scrambling Code

DlChCodeNo S-CCPCH Channelisation Code No.

SlotFmt S-CCPCH Slot Format

SttdInd S-CCPCH STTD Active Indicator

SIB7

The SIB7 serves as an update timer. The timer refers to the

following formula:


19/55


Expiration timer = MAX (32, SIB_REP * ExpirationTimeFactor)

In the formula above, SIB_REP indicates the transmission periodof SIB7, dynamically obtained during system broadcast schedule;ExpirationTimeFactor is a factor of SIB7 timeout and the system

fixedly configures it to 2.

The SIB7 can be transmitted by RNC or Node B, determined by

configuration of the OMCR parameter SIB7Originator . To shortenthe transmission time of SIB7, the system configures the Node Bto transmit the SIB7 by default.

The SIB7 fills the parameters as required during UE calculating

the initial power of PRACH preamble. The following CEs can beconfigured by OMCR. See Table 5.

T A B L E 5 S I B 7 CE CO NF I G URED BY OMCR

Name Description

DynPstLevelInit PRACH dynamic permanence-level initialvalue

SIB11/SIB12

The SIB11 and SIB12 configure the measurement controlinformation of cell. The SIB11 configures the measurementcontrol information needed by the UE in the IDLE state, while

the SIB12 configures the measurement control information

needed by the UE in the connection status on FACH. Theparameter Sib11orSib12 can be configured on the OMCR.Currently, the SIB12 does not broadcast. Thus, the UE in theconnection state also uses the configuration information ofSIB11 and the parameter value configured on the OMCR is 0(broadcast over the SIB11). For related parameters, refer to ZTEUMTS Idle Mode and Common channel behavior .

SIB15

The SIB15 includes auxiliary GPS information, such as DGPS,

ephemeris and almanac information, UTC and ionization updateinformation, cell location information as well as whether to

encrypt the information being transmitted. Refer to ZTE UMTSLocation Service feature description. Currently, the SIB15 doesnot broadcast.

SIB18

The SIB18 fills the PLMN tags of neighbor cells considered by theUE in the idle and connection state. The following CEs can be

configured by OMCR. See Table 6 and Table 7.



20/55


T A B L E 6 S I B 1 8 CE CO NF I G URED BY OMCR ( I NT RA - SYST EM CE L LINF O RM AT I O N )

Name Description

NMCC Mobile Country Code of Neighboring Cell

NMNC Mobile Network Code of Neighboring Cell

T A B L E 7 S I B 3 / S I B 4 CE CO NF I G URED I N OMCR ( I NT ER - SYST EM CE L LINF O RM AT I O N )

Name Description

MCC Mobile Country Code of Neighboring GSM Cell

MNC Mobile Network Code of Neighboring GSM Cell

RRC ConnectionEstablishment and ReleaseRRC connection establishment is divided into two scenarios:

Establishment on DCH

Establishment on CCH

Figure 2 illustrates the flow of RRC connection establishment.



21/55


F I G URE 2 RRC CO N N E C T I O N ES T A B L I S H M E N T FL OW

RRC Connection Establishment on DCH

When receiving the RRC CONNECTION REQUEST message from

the UE, the RNC determines which channel used to establish theRRC connection according to configuration of the OMCRparameter “InitRrcOnDch” .

If the “InitRrcOnDch” value is set to 0 (DCH-forced and using

common signaling) or 1 (DCH-forced and using high-speed



22/55


signaling), the RNC establishes the RRC connection on DCH. Ifthe “InitRrcOnDch” value is set to 3 (not forced, using common

signaling for DCH) or 4 (not forced, using high-speed signalingfor DCH), the RNC decides according to Establishment_cause of

RRC connection reported in RRC CONNECTION REQUEST. IfEstablishment_cause is of establishing a service, for example,UE originates call as a caller, then the RNC first selects DCH toestablish the RRC connection.

The cells required to establish radio links is calculated by theinter-frequency load balance algorithm.

The RNC establishes the radio link on the lub interface.

After successfully establishing the radio link, the RNC transmits

the RRC CONNECTION SETUP message to the UE. If the OMCRparameter “InitRrcOnDch” is configured to the high-speedsignaling, the RNC fills 13.6 K high-speed SRB in Dynamic

Transport Format Information of RRC CONNECTION SETUP; orelse, the RNC fills 3.4 K common SRB. Suppose the 13.6 Khigh-speed SRB is established, delete RNC reconfigures to 3.4 KSRB at the starting of RAB assignment. After receiving the RRCCONNECTION SETUP COMPLETE message from the UE, the RNCsuccessfully sets up the RRC connection. The establishmentprocess ends.

RRC Connection Establishment on CCH

When receiving the RRC CONNECTION REQUEST message from

the UE, the RNC determines which channel to be used toestablish the RRC connection according to configuration of theOMCR parameter “InitRrcOnDch” .

If the “InitRrcOnDch” value is set to 2 (FACH-forced), the RNCestablishes the RRC connection on FACH. If the “InitRrcOnDch”value is set to 3 (not forced, using common signaling on DCH) or

4 (not forced, using high-speed signaling on DCH), the RNCdecides according to Establishment_cause of RRC connectionreported in RRC CONNECTION REQUEST. If the RNC immediatelyoriginates services after RRC connection establishment (forexample, the Establishment_cause value is OriginatingConversational Call), the RNC establishes the RRC connection onDCH. If the RNC only accomplishes the flow such as LA updateafter RRC connection establishment but does not establishservices (for example, the Establishment_cause value isregistration), the RNC selects the common channel bearer

signaling. According to Initial UE Identify of UE, the RNC selectSCCPCH: Index of selected SCCPCH" = “Initial UE Identity” mod

K; among them, K indicates the SCCPCH number bearing FACHin the cell. On the selected SCCPCH, the RNC transmits the RRCCONNECTION SETUP message to the UE and delivers SRBconfiguration.



23/55


After receiving the RRC CONNECTION SETUP COMPLETEmessage from the UE, the RNC successfully establishes the RRC

connection. The establishment process ends.

Abnormal Process Handling of RRCConnection Establishment

Abnormal Process Handling of RRC ConnectionEstablishment on DCH

If radio link establishment fails, the RNC transmits the RRC

CONNECTION REJECT message to the UE, involving the Wait

time in this message to inform UE of the waiting time fromreceiving RRC CONNECTION REJECT to permitting to retransmitthe access request. The waiting time can be configured by OMCR(Twait ). If the RNC does not receive the RRC CONNECTIONSETUP COMPLETE message from the UE within 5s (for the airinterface message to be acknowledged, the RNC sets a 5s timerto wait for response), it deletes the radio link on the lubinterface. The RRC connection fails to establish and the UE is stillin the IDLE status.

Abnormal Process Handling of RRC Connection

Establishment on CCH

When the RNC does not receive the RRC CONNECTION SETUPCOMPLETE message from the UE within 5s, it indicates that RRC

connection establishment fails and the UE is still in the IDELstatus.

RRC Connection Release

The causes of triggering RRC connection release include the

following:

The service and NAS signaling connections are normallyreleased.

The Node B detects that radio link establishment is failed.

The RNC detects that RLC connection is failed.

The UE on DCH or FACH requests cell update, for the AM_RLCerror indication (RB2, RB3 or RB4) value is TRUE. Or the UE onFACH transmits the CELL UPDATE message to the RNC, becauseof radio link failure or RLC unrecoverable error.



24/55


The UE on FACH or PCH does not communicate any messageand data with the RNC within the specified time (T305 +11 min.).

The preceding situations trigger the release flow of RRCconnection. Figure 3 illustrates the release flow of RRC

connection.

F I G URE 3 RRC CO NNECT I O N R E L E A S E F L O W

In Figure 3,using the SRB1, the RNC transmits the RRCCONNECTION RELEASE message to the UE. To make the UErapidly searching cell stations after entering the IDLE status, theRRC CONNECTION RELEASE message contains the GSM networkand UMTS FDD network frequency-point information under thesame PLMN control with the current cell, as well as the potentialBCCH frequency range of surrounding the GSM cell and thepotential transmission frequency range of surrounding UMTS cell.The involved frequency point information of the GSM network

and FDD network includes: GSM band number(GsmBARangeNum), GSM frequency point upper limit

(GsmURange[32]), GSM frequency point lower limit

(GsmLRange[32]), FDD band number (FDDFreqRngNum), FDDUMTS frequency point lower limit (Luarfcn [8]) and FDD UMTSfrequency point upper limit (Uuarfcn[8]).

RRC Connection Release on DCH

When the UE on DCH receives the RRC CONNECTION RELEASEmessage from the RNC, it transmits the RRC CONNECTIONRELEASE COMPLETE message over the UM mode and meanwhilestarts up the timer T308. When T308 expires, the UEretransmits RRC CONNECTION RELEASE COMPLETE, the

retransmitting times determined by N308. T308 and N308 are all



25/55


configured by OMCR. When the UE on FACH receives the RRCCONNECTION RELEASE message from the RNC, it transmits the

RRC CONNECTION RELEASE COMPLETE message once.Receiving RRC CONNECTION RELEASE COMPLETE, the RNC

releases the radio link on the lub interface.

RRC Connection Release on CCH

The RNC transmits the RRC CONNECTION RELEASE message tothe UE on CCCH or on SRB2. When the UE on FACH receives theRRC CONNECTION RELEASE request from the RNC, it onlytransmits the RRC CONNECTION RELEASE COMPLETE message

once on CCCH. Receiving RRC CONNECTION RELEASECOMPLETE, the RNC releases the local resources and RRC

connection release is successful.

Abnormal Process Handling of RRC ConnectionRelease

When the RNC transmits the RRC CONNECTION RELEASEmessage to the UE but does not receive the RRC CONNECTIONRELEASE COMPLETE message from the UE, the RNC retransmitsRRC CONNECTION RELEASE. The retransmitting times aredetermined by the maximum retransmitting number (NreTran )of RRC CONNECTION RELEASE configured in the OMCR. Whenthe RNC does still not receive RRC CONNECTION RELEASECOMPLETE within 5 s after retransmitting RRC CONNECTIONRELEASE for NreTran, it assumes completion of RRC connection

release and then releases the local resources.

Paging

Paging Flow

According to different paging originators, paging is classified intothe following as shown in Figure 4.



26/55


F I G URE 4 P A G I NG F L O W

After receiving the paging from the CN, the SRNC deliversthe Node B broadcast.

The RNC transmits the PAGING TYPE1 to the UEs in the IDLEor PCH state and transmits the PAGING TYPE2 to the UEs inthe CELL_FACH or CELL_DCH state.

Paging originated by the SRNC not over the lur interface orby the DRNC

The RNC transmits the PAGING TYPE1 to the UEs in the IDLEor PCH state and transmits the PAGING TYPE2 to the UEs inthe CELL_FACH or CELL_DCH state.

Paging originated by the SRNC, over the lur interface

To request the DRNC to originate paging to the UE, the RNC

transmits the Paging Request message to the DRNC over theRNSAP.

PAGING TYPE 1

The RNC receives the paging from the CN and transmits thePAGING TYPE 1 to the UE in the IDLE or URA_PCH state on PCH.To promote the possibility of UE receiving the paging, the RNCrepeatedly transmits PAGING TYPE 1 to the UE and theretransmitting times are configured by OMCR (PagingSendTime).

The PCH has the corresponding PICH physical channel which



27/55


transmits the Page Indicator (PI). Each PI corresponds to agroup of UEs. The PI algorithm is as follows:

PI = DRX Index mod Np

Among:DRX Index = IMSI div 8192

Np: The number of PI included by one PICH radio frame can be

configured by OMCR.

By monitoring the UE’s own PI, the UE decides whether thenetwork is paging itself. Each PICH frame can include the PIs ofmulti-UEs and the OMCR can configure all PIs (Np) included ineach PICH. When each PICH frame includes more PIs, thetransmission power (PichPwr ) of PICH is being enhanced. The

corresponding relation is as follows.

PI No, perFrame Bit Repeat No. Transmission Power ofPICH Related to CPICH

18 16 -7

36 8 -7

72 4 -5

144 2 -2

To save power, the UE in the IDLE and PCH states use theDiscontinuous Reception (DRX) mode to monitor the PICH. By

this method, the UE only needs to monitor the PI once withinper DRX period. Each UE has its own Paging Occasion (PO).

Therefore, the UE only monitors one PICH frame on the SFNcorresponding to the PO and finds the PI of the frame’s own bythe calculated PI. The RNC fills the PI information on the PICHaccording to the PO of the UE. For the FDD system, the DRXperiod is equal to 2k frame. In the OMCR, the RNC configuresthree types of DRX cycle length coefficients: CS-domain DRXcycle length coefficient (Kcs), PS-domain DRX cycle lengthcoefficient (Kps) and UTRAN DRX cycle length coefficient(KUtran).

Refer to the following calculation:

When the UE is in the IDLE state, by using CS-domain DRX

cycle length coefficient (Kcs), PS-domain DRX cycle lengthcoefficient (Kps) and DRX parameter (DRX cycle lengthcoefficient) delivered by CN in the paging message, the RNC

decides the K value within the DRX period.

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

For the paging from the PS domain, if the CN delivers theDRX Cycle Length Coefficient, then K is equal to Min(Kcs,Kps,DRX Cycle Length Coefficient); if the CN does notdeliver the DRX Cycle Length Coefficient, then K is equal toMin (Kcs,Kps).

When the UE is in the PCH state, the RNC decides the K

value by using CS-domain DRX cycle length coefficient



28/55


(Kcs), PS-domain DRX cycle length coefficient (Kps) andUTRAN DRX cycle length coefficient (KUtran) and DRX

parameter (DRX cycle length coefficient) delivered by CN inthe paging message.

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

For the paging from the PS domain, if the CN delivers the

DRX Cycle Length Coefficient in the paging message, then Kis equal to Min (Kps,KUtran,DRX Cycle Length Coefficient); ifthe CN does not deliver the DRX Cycle Length Coefficient,then K is equal to Min (Kps, KUtran).

Refer to the PO calculation formula as follows:

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

Among:

N = SCCPCH channel number of intra-cell bearer PCH

DRX cycle length = 2k frame; the K value refers to the

preceding content.

PBP = 1

n = SFN

When the content of system broadcast updates, the RNCvoluntarily originates PAGING TYPE 1 to inform the UEs inthe IDLE and PCH states. The system cyclically transmits thePI on PICH within the whole DRX period. The K value of 2k ofthe DRX period is set to MAX (Kcs, Kps, KUtran).

PAGING TYPE 2

When the UE is in the DCH or FACH state, the UTRAN originatesthe paging process and transmits the PAGING TYPE 2 message

on DCCH. The UTRAN sets the paging cause in the Paging Causeof PAGING TYPE 2. Receiving PAGING TYPE 2, the UE in the DCHor FACH state starts up the receiving process of paging andreports the paging cause and paging record type identifier to theupper layer.

UE Capacity Enquiry

The RNC transmits the UE CAPABILITY ENQUIRY message to theUE to query the capacity information of UE. After receiving the

message, the UE transmits the UE CAPABILITY INFORMATIONmessage to the RNC; The RNC retransmits the UE CAPABILITY

INFORMATION CONFIRM information for acknowledgment. SeeFigure 5.



29/55


F I G URE 5 UE C A P A CI TY ENQ UI RY

As shown in Figure 5 , under the following scenarios, the RNCwill query the UE capacity:

When the RNC needs to know of the UE capacity information,

it establishes the UE CAPABILITY ENQUIRY information andtransmits the message to the UE.

When the UE is in the connection mode and its capacityinformation changes, the UE transmits the UE CAPABILITY

INFORMATION message to the RNC. The message includesthe capacity information such as protocol version realized by

UE (R99/R4/R5), whether to support HS-PDSCH, whether tosupport to concurrently read SCCPCH, DPCH and HS-PDSCHas well as to concurrently configure the DL capacity ofHS-PDSCH and the physical layer classification of HS-DSCH,whether to support to estimate HS-PDSCH and HS-SCCHaccording to the dedicated pilot. After saving the UE capacity

information, the RNC constructs the UE CAPABILITYINFORMATION CONFIRM message and transmits themessage to the UE.

If the RNC does not receive the CAPABILITY INFORMATIONmessage from the UE within 5s, it assumes that the UE capacityinformation enquiry is failed.

Radio Connection Monitoring

While the radio connection state of UE having the establishedRRC, if the poor radio quality or other causes make the RNC todecide that the radio connection between a UE and network hasbeen actually interrupted, the RNC immediately releases allresources that assigned to the UE, including all RB resources

having established services as well as release of RRC connectionand lu interface connection. The RAN supports the following

modes to monitor the radio connection state:

The Node B monitors the RL state.

It is suitable for the UE on DCH. While monitoring the radiolink state of UE, the Node B finds UL RL out of frame or other

causes resulting in the radio link unavailable. the Node B



30/55


transmits the RL failure message to the RNC. The intervalshould be 10s from UL out of frame to the time the Node B

transmits the RL failure message.

F I G URE 6 R A D I O L I N K F A I L U RE

CRNC Node B

RADIO LINK FAILURE INDICATION

If the cause value of RADIO LINK FAILURE INDICATION is

unrecoverable, or the cause value is recoverable but the RNCdoes not receive RADIO LINK RESTORE INDICATION within

10s, the RNC assumes that the radio link of the UE isinterrupted.

The RNC monitors the connection state of RLC.

After establishing the RRC connection, if the RNC has

transmitted the message on the RLC layer but does notreceive the UE response, it will retransmit the message.When the retransmitting number reaches 15, the RLC layerget reset. Once the Once the number reset reaches 6. theRNC assumes user-plane processing to be incorrect.

Depending on this method, the RNC can monitor all RLCconnections using the AM mode (the AM mode is used for theSRB). Further, the RNC can also monitor all UEs in theconnection state.

The RNC monitors the cell update message of UE.

The UE on DCH or FACH transmits the CELL UPDATEmessage to the RNC, of which the AM_RLC error indication(RB2, RB3 or RB4) value is true. The UE on FACH transmitsthe CELL UPDATE message to the RNC, carrying the cause

value such as Radio link failure or RLC unrecoverable error.When the received CELL UPDATE message from the UE

indicates the preceding two errors, the RNC assumes theradio link of the UE is interrupted.

The RNC monitors the keep-alive timer of UE.

For the UE on FACH or PCH, the RNC does not exchange any

message and data with the UE within the specified duration(T305 +11 min.) and assumes the UE radio connectioninterrupted. When monitoring the radio connection of a UEthat interrupted by the preceding four approaches, the RNCreleases the radio resources and transmits the lu ReleaseRequest message to the CN via the lu interface to inform theCN for releasing the corresponding RAB resources.



31/55


Radio Connection

ReestablishmentDuring link interruption caused by poor radio quality, the UE onDCH reports CellUpdate message, carrying the cause value, andthe RNC attempts to reestablish radio resources for the UE, asshown in Figure Figure 7

F I G URE 7 C A L L RE E S T A B L I S H M E N T

When the Cell update cause reported in the CELL UPDATEmessage is Radio link failure (for example, T313 expiration) orRLC unrecoverable error (for example, the UL RB is reset on the

RLC layer due to multiple data retransmission), and the value ofAM_RLC error indication (RB2, RB3 or RB4) is FALSE, the RNCoriginates reestablishment of radio link. To delete the existingRL of the UE: If the RL belongs to the SRNC, the SRNC deletesthe lub-interface RL process; if the belongs to other RNCs, theSRNC informs the DRNC of deleting the radio link. The RNCreconfigures the RB for the UE, reselects a channel andreconfigures the signaling and service parameters based on theselected channel. Meanwhile, it establishes the radio link via the

lub interface and then transmits the contents of physical channel



32/55



and RB reconfiguration to the UE through the CELL UPDATECONFIRM message. To ensure the UE properly receiving the

message, the RNC consecutively transmits the message threetimes with the identical RRC SNs. According to the contents

delivered in the CELL UPDATE CONFIRM message, the UEperforms the physical channel reconfiguration or RBreconfiguration. After completing reconfiguration, the UEresponds the Physical Channel Reconfiguration Complete or RBReconfiguration Complete message.


33/55

C h a p t e r

2

Parameters andConfiguration

System InformationBroadcast Parameters

SIB1 Parameter List

Field Name Description

UE Timers and Constants in idle mode

T300 Waiting Time After UE Sending RRCCONNECTION SETUP REQUEST Message(T300)

N300 Maximum Number of Retransmissions of theRRC CONNECTION REQUEST Message (N300)

T312Idle T312 in Idle Mode)(Waiting Time for Receiving"In Sync" from L1 in Idle Mode (T312 in IdleMode)

N312Idle Maximum Number of "In Sync" Received from

L1 in Idle Mode (N312 in Idle Mode)UE Timers and constants in connected mode

T302 Waiting Time After UE Sending CELL/URAUPDATE Message(T302)

N302 Maximum Number of Retransmissions of theCELL/URA UPDATE Message (N302)

T304 Waiting Time After UE Sending UE CAPABILITYINFORMATION Message(T304)

N304 Maximum Number of Retransmissions of the UECAPABILITY INFORMATION Message (N304)



34/55



Field Name Description

T305 Period of Cell/URA Update When UE is inCELL_FACH/CELL_PCH/ URA_PCHState(T305)(min)

T307 Waiting Time for Cell Reselection After UE is outof Service(T307)

T308 Waiting Time After Sending RRC CONNECTIONRELEASE COMPLETE Message in CELL_DCHState(T308)

T309 Waiting Time After Requesting ConnectionEstablishment in Other System (eg. GSM)(T309)

T312Connected T312 in Connected Mode)(Waiting Time forReceiving "In Sync" from L1 in Connected Mode

(T312 in Connected Mode)

N312Connected N312 in Connected Mode)(Maximum Number of"In Sync" Received from L1 in Connected Mode(N312 in Connected Mode)

T313 Waiting Time After DPCCH Established inCELL_DCH State Losing Synchronization (T313)

N313 Maximum Number of Successive "Out of Sync"Received from L1(N313)

T314 Waiting Time for Completion of Cell UpdateWhen Radio Link Fails and Radio Bearer(s)Associated with T314 Exist (T314)

T315 Waiting Time for Completion of Cell Update

When Radio Link Fails and Radio Bearer(s)Associated with T315 Exist (T315)

N315 Maximum Number of Successive "In Sync"Received from L1 During T313 is Activated( N315)

T316 Waiting Time for Cell Selection/Reselection AfterUE is out of Service in CELL_PCH/URA_PCHState(T316)(s)

MCC Mobile Country Code

T317 Waiting Time for Cell Selection/Reselection AfterUE is out of Service in CELL_FACH State(T317)

CN NAS Information

MNC Mobile Network Code

CnDomain CN Domain Supported

T3212Cs T3212(hour)

ATTIndCs IMSI Attach and Detach Indicator

NMOPs Network Mode of Operation

Kcs CS Domain DRX Cycle Length Coefficient

Kps PS Domain DRX Cycle Length Coefficient

MbmsModPrdCoeff Modification Period Coefficient for MBMS


35/55

Chapter 2 1BParameters and Configuration

SIB1 Parameter Configuration

T300

Wireless Parameter

Full NameWaiting Time After UE Sending RRC CONNECTIONSETUP REQUEST Message (T300)(ms)

Abbreviation T300

Value Rangeand StepLength

OMCR:(100, 200, 400, 600, 800, 1000, 1200,1400, 1600, 1800, 2000, 3000, 4000, 6000, 8000)ms

RNC: [0,14]ms

Unit msDefault Value(Note)

1000ms

OMC Path:View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->Waiting TimeAfter UE Sending RRC CONNECTION SETUP REQUESTMessage(T300)

Configuration description: Beyond the time specified by theparameter, When UE does not receive the response message yet,it will decide timeout and retransmits the RRC Connection Setup

Request message. To reduce the waiting time is to shorten theduration of RRC connection setup under the condition of goodair-interface quality.

N300

Wireless Parameter

Full NameMaximum Number of Retransmissions of the RRCCONNECTION REQUEST Message(N300)

Abbreviation N300


[0,7]

Unit Null

Default Value(Note)

3

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->MaximumNumber of Retransmissions of the RRC CONNECTION REQUEST

Message (N300)



36/55


Configuration description: When the retransmission number ofRRC connection request exceeds the maximum, call drop is

decided. By increasing the value is to reduce the possibility ofcall drop, but meanwhile to add burden of air interfaces.

T312Idle

Wireless Parameter

Full NameWaiting Time for Receiving "In Sync" from L1 inIdle Mode(T312 in Idle Mode)(s)

Abbreviation T312Idle


[1,15]s

Unit s

Default Value(Note)

2s

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->Waiting Timefor Receiving "In Sync" from L1 in Idle Mode (T312 in Idle Mode)

Configuration description: By decreasing the waiting time is toquicken signaling exchange with the L1 layer. However, underthe condition of poor air-interface quality, the flow is easy to fail.

N312Idle

Wireless Parameter

Full NameMaximum Number of “In Sync” Received from L1 in

Idle Mode(N312 in Idle Mode)

Abbreviation N312Idle


OMCR: (1, 2, 4, 10, 20, 50, 100, 200, 400, 600, 800,1000)

RNC:(0,11)

Unit Null

Default Value(Note)

10

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->MaximumNumber of "In Sync" Received from L1 in Idle Mode (N312 inIdle Mode)

Configuration description: The less number of synchronization

decision is easier to decide whether synchronization is completed.

However, the false synchronization is generated greatly, when



37/55


the number of synchronization decision increases, the reliabilityis correspondingly enhanced. However, it costs more time.

T302

Wireless Parameter

Full NameWaiting Time After UE Sending CELL/URA UPDATEMessage(T302)(ms)

Abbreviation T302


OMCR:(100,200,400,600,800,1000,1200,1400,1600,1800,2000,3000,4000,6000,8000)ms

RNC:(0,14)ms

Unit ms

DefaultValue (Note)

1000ms

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->Waiting TimeAfter UE Sending CELL/URA UPDATE Message(T302)

Configuration description: After the waiting time expires, the UEdoes not receive the response message yet, and decided timeout.When the waiting time is set longer, the possibility of timeout isless but the efficiency of flow processing is reduced.

N302

Wireless Parameter

Full NameMaximum Number of Retransmissions of theCELL/URA UPDATE Message(N302)

Abbreviation N302

Value Range andStep Length

[0,7]

Unit Null

Default Value(Note)

2

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->MaximumNumber of Retransmissions of the CELL/URA UPDATE Message(N302)

Configuration description: The UE decides that the flow fails

after the maximum number of retransmission Exceeds thethreshold. If the set value is less, the failure is generated moreeasily.



38/55


T304

Wireless Parameter

Full NameWaiting Time After UE Sending UE CAPABILITYINFORMATION Message(T304)(ms)

Abbreviation T304


OMCR:(100, 200, 400, 1000,2000)ms

RNC:(0,4)ms

Unit ms

Default Value(Note)

2000ms

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage

->UE counter and timer constant information ->Waiting TimeAfter UE Sending UE CAPABILITY INFORMATIONMessage(T304)

Configuration description: The UE decides timeout when the

response message not received beyond the waiting time. If theset value is less, the failure is generated more easily.

N304

Wireless Parameter

Full NameMaximum Number of Retransmissions of theUE CAPABILITY INFORMATION Message(N304)

Abbreviation N304


[0,7]

Unit Null

Default Value(Note)

2

OMC path: View->Configuration Management->RNC NE->RNC

Radio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->MaximumNumber of Retransmissions of the UE CAPABILITY INFORMATIONMessage (N304)

Configuration description: The UE decides that the flow is failedafter the maximum number of retransmission Exceeds thethreshold. If the set value is less, the failure is generated more

easily.



39/55


T305

Wireless Parameter

Full NamePeriod of Cell/URA Update When UE is inCELL_FACH/CELL_PCH/ URA_PCHState(T305)(min)

Abbreviation T305


OMCR:(noUpdateNoupdate,5,10,30,60,120,360,720)min

RNC:(0,7)min step1,0 indicates No update

Unit min

Default Value(Note)

5min

OMC path:View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information -> Period of

Cell/URA Update When UE is in CELL_FACH/CELL_PCH/URA_PCH State(T305)(min)

Configuration description: The lesser set value cause morefrequent periodical update and URA update.

T307

Wireless Parameter

Full NameWaiting Time for Cell Reselection After UE is out ofService(T307)(s)

Abbreviation T307

ManagementObject

ueCnst


OMCR:(5,10, 15,20,30,40,50)s

RNC:[0,6]s

Unit s

Default Value(Note)

5s

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->Waiting Timefor Cell Reselection After UE is out of Service(T307)

Configuration description: The lesser set value makes UE toreaccess the network faster, however, it increases the UE andsystem loads.



40/55


T308

Wireless Parameter

Full NameWaiting Time After Sending RRC CONNECTIONRELEASE COMPLETE Message in CELL_DCHState(T308)(ms)

Abbreviation T308


OMCR:(40, 80, 160, 320)ms

RNC:(0,3)ms

Unit ms

Default Value(Note)

80ms

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->Waiting TimeAfter Sending RRC CONNECTION RELEASE COMPLETE Messagein CELL_DCH State(T308)

T309

Wireless Parameter

Full NameWaiting Time After Requesting Connection

Establishment in Other System(eg.GSM)(T309)(s)Abbreviation T309


[1,8]s

Unit s

Default Value(Note)

3s


->UE counter and timer constant information ->Waiting TimeAfter Requesting Connection Establishment in Other System(eg.GSM) (T309)

Configuration description: Timeout is decided when the messageis not received yet even the waiting time expiers.

T312Connected

Wireless Parameter

Full NameWaiting Time for Receiving "In Sync" from L1 in

Connected Mode(T312 in Connected Mode)(s)



41/55



Wireless Parameter

Abbreviation T312Connected

Value Range

and StepLength [1,15]s

Unit s

Default Value(Note)

1s


Radio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->Waiting Time

After Sending RRC CONNECTION RELEASE COMPLETE Messagein CELL_DCH State(T308)

Configuration description: Timeout is decided when the messageis not received yet even the waiting time expiers

N312Connected

Wireless Parameter

Full NameMaximum Number of "In Sync" Receive from L1 inConnected Mode(N312 in Connected Mode)

Abbreviation N312Connected

Value Range

and StepLength

OMCR:(1,2,4,10, 20,50,100,200,

400,600,800,1000)RNC:(0,11)

Unit None

Default Value(Note)

1

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->MaximumNumber of "In Sync" Received from L1 in Connected Mode(N312 in Connected Mode)

Configuration description: When the value is set low, thedecision on synchronization completion is simpler, but theprobability of the false synchronization rises. When the value isset high, the reliability is enhanced and it also costs much time.

T313

Wireless Parameter Name

Full NameWaiting Time After DPCCH Established inCELL_DCH State LosingSynchronization(T313)(s)


42/55




Abbreviation T313

Value Range and

Step Length

[0,15]s

Unit None

Default Value(Note)

3s

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->Waiting TimeAfter DPCCH Established in CELL_DCH State LosingSynchronization (T313)


N313

Wireless Parameter

Full NameMaximum Number of Successive "Out of Sync"Received from L1(N313)

Abbreviation N313


OMCR: (1, 2, 4, 10, 20, 50, 100, 200)

RNC:[0,7]

Unit None

Default Value(Note)

20

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->MaximumNumber of Successive "Out of Sync" Received from L1(N313)

Configuration description: When the value is set low, thedecision on synchronization completion is simpler, but theprobability of the false synchronization rises. When the value is

set high, the reliability is enhanced and it also costs much time.

T314

Wireless Parameter

Full NameWaiting Time for Completion of Cell UpdateWhen Radio Link Fails and Radio Bearer(s)Associated with T314 Exist(T314)(s)

Abbreviation T314

Value Range andOMCR: (0, 2, 4, 6, 8, 12, 16, 20)s


43/55



Wireless Parameter

Step Length RNC:[0,7]

Unit s

Default Value (Note) 4s

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->Waiting Time

for Completion of Cell Update When Radio Link Fails and RadioBearer(s) Associated with T314 Exist (T314)


T315


Full NameWaiting Time for Completion of Cell UpdateWhen Radio Link Fails and Radio Bearer(s)Associated with T315 Exist(T315)(s)

Abbreviation T315


OMCR:(0,10, 30, 60, 180, 600, 1200,

1800)s

RNC: [0,7]

Unit s

Default Value (Note) 30s


->UE counter and timer constant information ->Waiting Timefor Completion of Cell Update When Radio Link Fails and RadioBearer(s) Associated with T315 Exist (T315)

Configuration description: Timeout is decided when the messageis not received yet even the waiting time expiers

N315

Wireless Parameter

Full NameMaximum Number of Successive "In Sync"Received from L1 During T313 is Activated(N315)

Abbreviation N315


OMCR: (1, 2, 4, 10, 20, 50, 100, 200, 400, 600,800, 1000)

RNC:[0,11]

Unit None

Default Value 1


44/55



Wireless Parameter

(Note)


Radio Resource Management->Advanced Parameter Manage->UE counter and timer constant information ->MaximumNumber of Successive "In Sync" Received from L1 During T313is Activated ( N315)

Configuration description: When the value is set low, thedecision on synchronization completion is simpler, but theprobability of the false synchronization rises. When the value isset high, the reliability is enhanced and it also costs much time.

T316

Wireless Parameter

Full NameWaiting Time for Cell Selection/ReselectionAfter UE is out of Service inCELL_PCH/URA_PCH State(T316)(s)

Abbreviation T316


OMCR:(0, 10, 20, 30, 40, 50, Infinity)s

RNC: [0,6]s

Unit s

Default Value(Note)

0s


->UE counter and timer constant information -> Waiting Timefor Cell Selection/Reselection After UE is out of Service inCELL_PCH/URA_PCH State(T316)(s)


T317

Wireless Parameter

Full NameWaiting Time for Cell Selection/Reselection AfterUE is out of Service in CELL_FACH State(T317)(s)

Abbreviation T317


OMCR:(0,10, 30, 60, 180, 600, 1200, 1800)s

RNC:[0,7]

Unit Null

Default Value

(Note)

0s


45/55



->UE counter and timer constant information ->Waiting Timefor Cell Selection/Reselection After UE is out of Service in

CELL_FACH State(T317)Configuration description: Timeout is decided when the messageis not received yet even the waiting time expiers.

T3212Cs

Wireless Parameter

Full Name T3212(hour)

Abbreviation T3212Cs

Description Timer of periodic location update

ManagementObject

CnInfo


OMCR:(0,[0.1,25.5])hours Step0.1hour

0: No Periodic Updating

RNC:D=P*10

[0,255]

Unit Null

Default Value(Note)

1hour

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->CN NAS Information ->timer of Periodic location update

Configuration description: If the set value is less, the roprtlocation comes close to real location.

Connection Establishment

and Release ParametersParameter List

Name Description

NReTran Maximum number of retransmission of the RRCCONNECTION RELEASE

Twait Wait Time for RRC ConnectionReestablishment(s)



46/55



Name Description

N308 N308

FDDFreqRngNum Number of FDD UMTS Frequency Range

GsmBARangeNum Number of GSM BA Range

GsmLRange[32] Wait Time for RRC ConnectionReestablishment(s)

GsmURange[32] GSM Upper Range

Luarfcn [32] UARFCN(Nlow)

Uuarfcn[32] UARFCN(Nupper)

InitRrcLBSw Load Balance Switch of Initial RRC Procedure

InitRrcOnDch Type of Transport Channel for Initial RRCConnection Setup

Parameter Configuration

NReTran


Full NameMaximum number of retransmission of the RRCCONNECTION RELEASE

Abbreviation NReTran


[1,10]

Unit Null

Default Value(Note)

3

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->RNC Radio Resource Management ->Maximum Number ofRetransmissions of the RRC CONNECTION RELEASE Message

Configuration description: The maximum number RNCretransmitting the RRC CONNECTION RELEASE when the UEdoes not respond the RRC CONNECTION RELEASE COMPLETEmessage. The less set value cause easy generation of flowfailure.

Twait

Wireless Parameter

Full Name Wait Time for RRC Connection Reestablishment(s)


47/55



Wireless Parameter

Abbreviation Twait

Description

The waiting time from UE receiving the RRC

CONNECTION REJECT message to retransmittingthe access request message; The parameter iscarried in the RRC CONNECTION REJECT messageto the UE.


[0,15]s

Unit s

Default Value(Note)

5s


Radio Resource Management->Advanced Parameter Manage->RNC Radio Resource Management ->Wait Time for RRCConnection Reestablishment

Configuration description: The less set value cause more easyretransmission flow of access request is triggered. Meanwhile,the possibility of failure is enhanced.

N308

Wireless Parameter

Full Name N308

Abbreviation N308

DescriptionMaximum of retransmitting the RRC ConnectionRelease Complete message


[1,8]

Unit Null

Default Value

(Note)1

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->Advanced Parameter Manage->RNC Radio Resource Management ->N308

Configuration description: The less set value case more easyflow failure generation.

FDDFreqRngNum

Wireless Parameter

Full Name Number of FDD UMTS Frequency Range


48/55



Wireless Parameter

Abbreviation FDDFreqRngNum

Description

This parameter indicates the UTRAN FDD

frequency number under the PLMN control. Whilereturning to the IDLE state from the RRCconnection state, the UE selects a cell to station.To make the UE quickening the speed of cellsearch, the UTRAN carries this parameter in theRRC CONNECTION RELEASE message, indicatingthe possible transmission frequency range ofsurrounding cells.


[0,32]

Unit Null

Default Value(Note)

2


Radio Resource Management->RPLMN Range Information ->Number of FDD UMTS Frequency Range

GsmBARangeNum

Wireless Parameter

Full Name Number of GSM BA Range

Abbreviation GsmBARangeNum

Description

This parameter indicates the number of GSMBCCH assignment table. When the UTRAN andBSS networks belong to the same PLMN, the UEselects a cell to station while returning to the IDLEstate from the RRC connection state. To make theUE quickening the speed of cell search, the UTRANcarries this parameter in the RRC CONNECTIONRELEASE message, indicating the possible BCCHfrequency range of surrounding GSM cells.


[0,32]

Unit Null

Default Value(Note)

3


Radio Resource Management->RPLMN Range Information ->Number of GSM BA Range


49/55


GsmLRange[32]

Wireless Parameter

Full Name GSM Lower Range

Abbreviation GsmLRange[32]

Description

This parameter indicates the frequency lower limitof a GSM BCCH allocation table under the PLMNcontrol. When the UTRAN and BSS networksbelong to the same PLMN, the UE selects a cell tostation while returning to the IDLE state from theRRC connection state. To make the UE quickeningthe speed of cell search, the UTRAN carries thisparameter in the RRC CONNECTION RELEASEmessage, indicating the possible BCCH frequencyrange of surrounding GSM cells.


[512,885],[0,124] and [975,1023]

Description:

DCS1800 band (ARFCN ＝ [512,885])

GSM900 band (ARFCN ＝[0,124],[975,1023]).

Unit Null

Default Value(Note)

[512, 0,975]

OMC path: View->Configuration Management->RNC NE->RNCRadio Resource Management->RPLMN Range Information->GSM Lower Range

Configuration description: The GSM Lower Range should beconsistent with the GSM Upper Range.

GsmURange[32]

Wireless Parameter

Full Name GSM Upper Range

Abbreviation GsmURange[32]

Description

This parameter indicates the frequency upper limitof a GSM BCCH allocation table under the PLMNcontrol. When the UTRAN and BSS networksbelong to the same PLMN, the UE selects a cell

14wcdma Po b en Accesspagingoptimization 55 130915133550 Phpapp02

Documents