ZTE UMTS Connection Management Feature Guide V6!1!201204

Connection Feature Guide
WCDMA RAN
Management
Connection Management Feature Guide

Version Date Author Reviewer Notes 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 2.1.16 3.2.1.1 3.2.1.4 4.3.2.1 4.3.2.2 4.3.2.14 V6.0 2011-5-30 FengChao Lu Li 4.3.2.15 RrcRdtSwch:add Iu Interface Interruption Protection: add Enable the DSAR:modify Disable the DSAR:modify CsDsarSwh:modify PsDsarSwh:modify Number of Cells Updating SIB3:add 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 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: Call Re-establishment Triggered By
ZTE Confidential Proprietary
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 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 Huangmeiqing V6.1 2012-02-22 fengchao 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 2 2.1 2.1.1 2.1.2 2.1.3 2.1.4 2.1.5 2.1.6 2.1.7 2.1.8 2.1.9 2.1.10 2.1.11 2.1.12 2.1.13 2.1.14 2.1.15 2.1.16 3 3.1 3.1.1 3.1.2 3.2 3.2.1 3.2.2 3.3 3.3.1 3.3.2 3.3.3 3.4 3.4.1 3.4.2 3.5 3.5.1 3.5.2 3.6 Functional Attribute............................................................................................... 8 Overview ................................................................................................................. 8 Function Introduction................................................................................................ 8 System Information Broadcasting ............................................................................ 8 Connection Setup and Release ............................................................................... 9 Paging .................................................................................................................... 10 NAS Message Transfer.......................................................................................... 11 Ciphering Algorithm UEA0 and UEA1 ................................................................... 12 Integrity Protection Algorithm UIA1........................................................................ 13 Radio Connection Monitor ..................................................................................... 14 Radio Connection Re-establishment ..................................................................... 14 27.2Kbps High Speed Signaling RB ...................................................................... 15 RRC Connection Redirect...................................................................................... 15 Domain Specific Access Restriction (DSAR)......................................................... 16 Ciphering Algorithm UEA2 ..................................................................................... 16 Integrity Protection Algorithm UIA2........................................................................ 17 Deferred SIB11/12 ................................................................................................. 17 Direct Tunnel .......................................................................................................... 18 Iu Interface Interruption Protection ........................................................................ 18 Technical Description.......................................................................................... 19 System Broadcast .................................................................................................. 19 System Information Broadcasting, Scheduling, and Transmission....................... 20 Information Sent by SIBs ....................................................................................... 22 DSAR and Cell Bar Access.................................................................................... 32 Overview of DSAR ................................................................................................. 32 Cell Bar Access (CBA) ........................................................................................... 37 RRC Connection Setup and Release .................................................................... 39 RRC Connection Setup.......................................................................................... 39 Handling Abnormality in the RRC Connection Setup ............................................ 41 Releasing the RRC Connection ............................................................................. 42 RRC Connection Redirection ................................................................................. 44 Redirection for Load Reduction ............................................................................. 44 Redirection for Emergency Call ............................................................................. 48 NAS Message Transfer.......................................................................................... 50 NAS Message Forwarding Flow ............................................................................ 50 Setting up and Releasing the Iu Interface Connection .......................................... 51 Paging .................................................................................................................... 57
3.6.1 3.6.2 3.6.3 3.6.4 3.7 3.7.1 3.7.2 3.7.3 3.8 3.9 3.10 3.10.1 3.10.2 3.11 3.11.1 3.11.2 3.11.3 3.12 3.12.1 3.12.2 3.13 3.14 3.15 4 4.1 4.1.1 4.1.2 4.1.3 4.1.4 4.1.5 4.1.6 4.1.7 4.1.8 4.1.9 4.1.10 4.1.11 4.1.12 4.2 4.2.1 4.2.2 4.3
Paging Flow............................................................................................................ 57 PAGING TYPE 1 .................................................................................................... 58 PAGING TYPE 2 .................................................................................................... 60 Virtual Location Area Paging ................................................................................. 60 Security Mode Control............................................................................................ 61 Security Mode Control Flow ................................................................................... 61 Encryption Algorithm and Parameters ................................................................... 66 Integrity Protection Algorithm and Parameters...................................................... 68 RAB Force Queue .................................................................................................. 69 Radio Connection Monitor ..................................................................................... 70 Call Re-establishment ............................................................................................ 71 Processing of Call Re-establishment..................................................................... 72 Call Re-establishment Triggered By Network ....................................................... 74 Managing the Iub Interface Radio Link .................................................................. 77 Establishing the Iub Interface Radio Link .............................................................. 77 Reconfiguring the Iub Interface Radio Link ........................................................... 78 Releasing the Iub Interface Radio Link.................................................................. 79 Managing the Iur Interface Radio Link................................................................... 79 Reconfiguring the Iur Interface Radio Link ............................................................ 79 Releasing the Iur Interface Radio Link .................................................................. 80 RB reconfiguration .............................................................................................. 80 Iu Overload Control ................................................................................................ 81 Deferred SIB11/12 ................................................................................................. 83 Configuration and Parameters........................................................................... 84 System Information Broadcasting Parameters ...................................................... 84 SIB1 Parameter List ............................................................................................... 84 SIB1 Parameter Configuration ............................................................................... 86 SIB2 Parameter List ............................................................................................... 97 SIB2 Parameter Configuration ............................................................................... 97 SIB3/SIB4 Parameter List ...................................................................................... 98 SIB3/SIB4 Parameter Configuration ...................................................................... 99 SIB5/SIB6 Parameter List .................................................................................... 106 SIB5/SIB6 Parameter Configuration .................................................................... 108 SIB7 Parameter List ............................................................................................. 119 SIB7 Parameter Configuration ............................................................................. 119 SIB11/SIB12 Parameter List ................................................................................ 120 SIB11bis Parameter Configuration ...................................................................... 120 Parameters related to Connection Setup and Release ....................................... 121 Parameter List ...................................................................................................... 121 Parameter Configuration ...................................................................................... 121 DSAR Parameters................................................................................................ 125
4.3.1 4.3.2 4.4 4.4.1 4.4.2 4.5 4.5.1 4.6 4.6.1 4.7 4.7.1 4.7.2 4.8 4.9 4.9.1 4.9.2 4.10 4.10.1 4.10.2 4.11 4.11.1 4.11.2 4.12 4.12.1 4.12.2 4.13 4.13.1 4.13.2 5 5.1 5.2 6 7
Parameter List ...................................................................................................... 125 Parameter Configuration ...................................................................................... 126 Paging Parameters .............................................................................................. 132 Parameter List ...................................................................................................... 132 Parameter Configuration ...................................................................................... 133 Ciphering Param eters ....................................................................................... 136 EncryAlg ............................................................................................................... 136 Integrity Protection Parameters ........................................................................... 136 IntegrityAlg............................................................................................................ 136 AMR Service Forced Queue Parameters ............................................................ 136 Parameter List ...................................................................................................... 136 Parameter Configuration ...................................................................................... 137 Radio Connection Monitor Parameters ............................................................... 137 RRC Connection Redirection Parameters ........................................................... 138 Parameter List ...................................................................................................... 138 Parameter Configuration ...................................................................................... 138 Iu Overload Control .............................................................................................. 140 TigOR ................................................................................................................... 140 TinTR .................................................................................................................... 140 Deferred SIB11/12 ............................................................................................... 140 Parameter List ...................................................................................................... 140 Parameter Configuration ...................................................................................... 140 Direct Tunnel ........................................................................................................ 141 Parameter List ...................................................................................................... 141 Parameter Configuration ...................................................................................... 142 Call Re-establishment .......................................................................................... 142 Parameter List ...................................................................................................... 142 Parameter Configuration ...................................................................................... 143 Counter and Alarm ............................................................................................ 150 Counter List .......................................................................................................... 150 Alarm List.............................................................................................................. 170 Glossary.............................................................................................................. 170 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
Functional Attribute
System version: [RNC V3.11.10/V4.11. 10, Node B V4.11.10, OMMR V 3.11.10/V4.11.10, OMMB V4.11.10] Attribute: necessary function NEs involved: UE 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 t wo RNCs. Node B RNC MSCS MGW SGSN GGSN HLR
2
2.1
2.1.1
Overview
Function Introduction
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 cont ents: Public Land Mobile Net work (PLMN) ID, location area (LA ), rout e area (RA) Information on the timers and counters related to the Radio Resource Control (RRC) connections
Configuration information of the UTRA N registration area (URA ) Cell selection and reselection paramet ers Parameters for configuring the common channels, such as FACH, PCH, and RA CH 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, SIB 18, 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 partitions 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 S IB is 96, it may exceed the 3552bit. To solve this problem and keep the current system information process stratege, the SIB11bis is introduced, its structure is similar to SIB11 but optimized. For adaption SIB11bis, the SIB 18 is als o add the PLMN indicator for the cells whic h inside the SIB11bis. ZTE RAN lifted t he 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 SIB 11 or SIB11bis. The system will construct the SIB 11 and SIB 11bis according t o the adjacent cell configuration, and modify the SIB18 content according to the 3GPP prot ocol.
2.1.2
Connection Setup and Release

This function is used to manage the set up and release of the RRC connections between the UTRAN and the UE so that the signaling bearer can be established bet ween 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 res ources to set up the Signaling Radio Bearer (S RB) 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 S RB als o 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 set up, the UTRAN monitors the Iu connection and radio connection of the UE. If all Iu connections are releas ed or the radio connection to the UE is interrupt ed (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 interfac e 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.
10
The UE is in FACH or DCH state The RNC knows the loc ation information of the UE in the cell and sends paging messages to the cell.
The ZTE RA N 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 servic e bearer for the downlink dat a transmission. After the system information changes, the RNC sends the paging message t o 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 RA N 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_FA CH, or CE LL_DCH state, send paging message of PAGING TYPE 2. To improve the success paging rate at boundary of Loc ation area, RNC introduce Virtual Location A rea Paging. When a cell is at boundary of Location area, the paging in this cell also will be sent to the cell of adjacent Loc ation area.
2.1.4
NAS Message Transfer

Signaling in the Non-Access Stratum (NAS) layer between the UE and the CN must pass the UTRA N. The signaling in the NAS layer is used to control the UE location updating, authentication, call setup, call release, and SMS data trans fer. The UTRA N 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 TRA NSFER messages defined by the RA NAP and RRC protocols bet ween the CN and the UE. The ZTE RA N supports three types of direct forward messages:
11
INITIAL DIRECT TRA NSFER message Once the UTRAN receives the INITIAL DIRE CT TRA NSFE R 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 S CCP connection and the UE RRC connection, and sets up a channel for NAS messages between the UE and the CN.
UPLINK DIRECT TRA NSFER message When rec eiving the UPLINK DIRECT TRANS FER message from the UE, the UTRA N adds the NAS message to the DIRECT TRANSFE R message according to the label of the CN domain in the message, and forwards the message to the MSC or SGSN.
DOWNLINK DIRECT TRANSFE R message When rec eiving the DIRECT TRA NSFER message from the CN, the UTRAN adds the NAS message to the DOW NLINK DIRECT TRA NSFER message according to the relation between the S CCP 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 bet ween 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 prot ect the security of the communication between the RNC and the UE. The ZTE RA N supports the encryption algorithms UEA0 and UEA1: UEA0 means that the data from t he Uu interface are not encrypted; UEA1 is based on the encryption algorithm f8 of the KASUMI algorithm and supports encryption and decryption.
12
Whether the encryption protection function should be enabled and which enc ryption algorithm is to be applied can be configured in the CN. Through the security mode command process of the RA N 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 t he 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 encry pts the data to be transmitted in compliance with the f8 algorit hm, with the encryption key and variables varying with the data volume. The receiver dec rypts the data using the same algorithm. Encryption is implemented in the RLC layer (AM or UM mode) or MAC lay er (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 RA N supports the unique integrity protection algorithm UIA 1 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 prot ection mode through the RRC security mode command process. If t he integrity protection is enabled, when the RNC or the UE sends the RRC message, it first calculates the integrity protection authentication code (MA C-I) through the f9 algorithm, and then adds MA C-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 c ompare XMA C-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
13
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 releas es the resources allocated to the UE (including RB resources with services) and releases the RRC connection. The ZTE RA N monit ors 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 interrupt ed line of a UE, the RNC releases the radio res ources and sends an Iu release request message through the Iu interface to the CN to release the relat ed RAB resources.
2.1.8
Radio Connection Re-establishment

A UE in t he DCH state may suffer from t emporary radio connection int erruption and cannot continue the services due to burst interference or abrupt changes to the radio environment. Before the UTRA N detects the radio connection interruption, the UE recovers the servic es. 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 bet ween the UE and the UTRA N 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.
14
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 servic es reception. It improves users experience. The feature enables the system to use the 27.2 kbps Signaling Radio Bearer (S RB) 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 RA N will setup SRB at 27.2kbps to speed up trans ferring the NAS signaling messages (including location update message, aut hentication 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 net works or between UTRA N and GSM net work or bet ween UTRAN and E-UTRAN network and so increas es success rate of users service access. During RRC connection procedure, when UTRA N receiving RRC Connection Request message from UE, admission control is performed. If proc essor 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 UTRA N network. And if there is other UTRA N cell or GSM cell or E -UTRAN cell
collocated with the cell which the UE t ries to access, RNC t ransmits RRC Connection Reject message with Redirect info IE to inform UE about frequency information of collocated adjacent UTRA N 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-UTRA N carrier. The RNC support the E-UTRAN FDD cells and the E-UTRA N TDD cells.
15
2.1.11
Domain Specific Access Restriction (DSAR)

For some critical conditions, e.g. in t he sports match, or the large party, large amount of user access will make the CN overloaded. DSA R 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 net work 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. UTRA N selects part of UEs for access restriction by periodic polling method or parameter configuration on OMC. When CN overload is resolved, DSA R is stopped for relative domain. Further more, ZTE UTRAN support manual DSA R triggering on OMC. In this way, the operators can control network access more flexibly. For example, the net work 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 dat a and signalling s ent between the UE and the RNC. The followings are the diffirences bet ween UEA2 and UEA1: 1. UEA1 is KASUMI bas ed algorithm and UEA2 is SNOW 3G based algorit hm. 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 int egrity capability when a user subscribes for the service, then a proper algorithm is selected. Thus more and more flexible enc ryption algorithms are provided. This feature complies with the security mechanism and SNOW 3G algorithms specified
16
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 bet ween the UE and the RNC. The followings are the diffirences bet ween UIA2 and UIA 1: 1. UIA1 is KASUMI based algorithm and UIA 2 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 support ed by the UE in MS/US IM Classmark. RNC compares the information with the integrity capability when a us er 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 S IB11, SIB 11bis or SIB12 should be read and stored by the UE before sending message or acting on received message on FA CH 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 specificatio n, UE is allowed to send messages through RACH or receive messages through FA CH before reading and storing S IB11/12 information. UTRA N broadcasts through SIB3 to notice if the network supports this feature. If the feature is applied, UEs 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
17
needs to complete SIB 11/11bis/12 reading and storing. This feat ure complies with TS 25.331 CR2557R2
2.1.15
Direct Tunnel
After HSPA/ HSPA+ is introduced to WCDMA net work, data throughput is greatly increased and the requirements for bandwidth and lat ency are much higher. Direct tunnel is officially defined in 3GPP R7 standard. It supports direct connection of user plane between RNC and GGS N. Direct Tunnel feat ure is trans parent to RNC. SGSN decides when to use Direct Tunnel. RNC is not involved during direct tunnel establishment and release. ZTE RA N system supports the following functions, which interoperates with SGS N to implement Direct Tunnel feat ure. 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. A TM on Iu PS is able to connect to Gn interface as well, but its 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 users complaints for service inc apability. To avoid simult aneous registration of all term inals moving to other networks, cell barring will be made in sequenc e. The number of cells to be barred one time is configurable by operator. If only one of core domain losses its connection wit h RA N, RA N 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
18
classes is not going to request the service for the domain, It avoids too many UE connection request signaling for rejection from net work. So the signaling load to RAN is reduced. Iu Interfac e 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, PagingLocaBarS wh is set to UE -initiated paging response and location registration barred, CsACBarredOmcr/PsACB arredOmcr 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
3.1
Technical Description
System Broadcast
The RNC is responsible for creating and broadcasting system information. The system information include t he 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 UTRA N information necessary to Location Area Update (LA U), 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 (S IB).
19
3.1.1
System Information Broadcasting, Scheduling, and Transmission

The MIB can store the scheduling information of the SB and S IB; the SB stores the scheduling information of the SIB, including SB1 and SB2; the SIB stores the system information. The ZTE UTRAN s upports SB1, SB2, S IB3, SIB 5, SIB6, S IB7, S IB11, 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 SIB 7), the system also broadcasts system messages. See the following figure.
Figure 3-1
System broadc asting
UE
NodeB
DRNC
SRNC
system information broadcast scheduler
SYSTEM INFORMATION UPDATE REQUEST SYSTEM INFORMATION UPDATE RESPONSE System information broadcast
Conditioninforming UE of idle, CELL_PCHURA_PCH that system information changed PagingPAGING TYPE1
Conditioninforming UE of CELL_FACH that system information changed
RRC
SYSTEM INFORMATION CHANGE INDICATION
RRC
When a cell is created or the system information is updated, the system first schedules the system information broadc asting 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 S IB 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
20
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 SIB 11. This following describes the division of the S IB 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 Level 1 Level 2
Scheduling levels of the SIBS Information blocks scheduled by the MIB: SB1, SIB1, SIB 2, SIB3, and SIB7 Information blocks scheduled by SB1: SIB11, SIB 18
Broadcast interval of t he S IBs 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 INFORMA TION UP DA TE REQUES T message to the Node B. When the RNC rec eives the correct SYSTEM INFORMA TION UP DA TE RESPONSE message, it considers system information updating successful. After rec eiving 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 updat ed, the system notifies the UE in the Idle, PCH, or FA CH state through the following means: Notify the UE in the Idle or PCH state through paging: The RNC s ends 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
21
information has been updated.
3.1.2
3.1.2.1
Information Sent by SIBs

SIB1
SIB1 mainly contains the CN information, UE behavior related timers and counters. The following describes the cells configured in the OMCR: T300 s pecifies the waiting time after the UE sends the RRC CONNE CTION SE TUP 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 SE TUP REQUEST message. N300 specifies the maximum retransmit event count of the RRC CONNE CTION SE TUP REQUEST message. If the T300 timer ex pires and the retransmit event count is equal to or larger than N300 but the RRC CONNECTION SE TUP message has not been received, the UE enters the Idle mode. T312I dle specifies the time during which the UE in Idle mode has to wait for the synchronization indication from layer 1 when it establishes the dedicat ed 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 ex pires, 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 s pecifies the waiting time after the UE sends the CELL UPDATE or URA UPDATE message. The counter is started when the UE sends the CELL UP DATE or URA UPDATE message; the counter is stopped when the UE receives the CE LL UPDATE
22
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 UP DATE 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 UP DATE messages sent by the UE is larger than or equal to N302, the UE enters the Idle mode. T304 s pecifies the waiting time after the UE sends the UE CAPAB ILITY INFORMATION message. When the UE sends the UE CAPAB ILITY INFORMATION message, the timer is started; when t he UE receives the UE CAPABILITY INFORMATION Confirmed message, the timer is stopped. When the T304 timer ex pires 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 count er expires and the ret ransmit event count is equal to or larger than N304, the UE starts the CELL UP DATE process. T305 specifies the interval at which the cell or URA is updated when the UE is in the CELL_FA CH, or CELL_P CH/ URA _PCH state. The T30 5 timer is started when the UE enters the CELL_FACH, or CELL_P CH/ URA _PCH state. When the UE receives the CELL UP DATE 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 CE LL UP DATE 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 CE LL_DCH state sends the RRC CONNE CTION RELEASE COMPLE TE message. The T308 timer is started after the UE sends the RRC CONNE CTION RE LEASE COMPLE TE message. When the T308 timer expires and the number of the RRC CONNECTION RE LEASE COMP LE TE messages sent by the UE is smaller than N308, the UE retransmits the RRC CONNECTION RELEASE COMP LE TE message.
23
N308 specifies the maximum retransmit event count of the RRC CONNECTION RELEASE COMPLE TE message. When the T308 counter expires and the number of the RRC CONNE CTION RE LEASE COMP LE TE messages sent by the UE is larger than or equal to N308, the UE enters the Idle mode. T309 specifies the waiting time after t he UE initiat es the request of accessing other system (such as GSM). When the UE receives the CELL CHA NGE OR DE R FROM UTRA N message, the T309 timer is start ed; when the UE in the new cell successfully receives the response t o 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 rec eived from layer 1 before the UE in connected mode sets up the dedicated channel successfully. T313 specifies the waiting time after the DP CCH channel set up by the UE in the DCH state loses synchronization. When the number of synchronization loss indications received by the UE in the DCH state from layer 1 reaches the value of N313, the UE starts T313. When the UE receives synchronization indications from layer 1 for N315 times, it stops the T313 timer. When the T313 timer expires, the radio links involved in the lost synchronization fail. N313 specifies the maximum number of synchronization loss indications received by the UE from layer 1. N315 specifies the maximum number of synchronization loss indications received by the UE from layer 1 when T313 is in active status. T314 is a UE timer. When the criteria for radio link failure are fulfilled, T314 is started if radio bearer(s) that are associated with T314 exist or if only RRC connection exists only
24
to the CS domain. When the Cell Update proc edure 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 whet her T302 is still in running status. If yes, the UE waits for the CELL UPDATE CONFIRM or URA UP DATE 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 res ources and enters the Idle mode. If T315 ex pires, 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_P CH state waits for cell selection or reselection after leaving the serving cell. When the UE in the P CH 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 t he CELL_FA CH state waits for cell selection or res election after leaving the serving cell. When the T316 timer expires, the system starts the T317 timer; when the UE in the FA CH 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.
25
T3212Cs is a periodic location updating timer. Location updating involves two occasions: The UE detects LAC variation and initiates loc ation updating; the system updates locations periodically. T3212Cs is a periodic location updating timer. ATTIndCs is a digital variable and specifies whether the IMS I ATTA CH flow or the DE TACH flow should be adopted. NMOPs specifies a net work 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. MbmsModP rdCoeff 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
SIB 2 parameters that can be configure d in the OMCR Parameter Description Number of UTRA N registration areas ID of a UTRA N registration area
Parameter Name URA Num URA[4]
3.1.2.3
SIB3/SIB4
Parameters in SIB3 and SIB 4 are related to the cell selection and cell reselection. SIB3
26
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).SIB 4 is not broadcasted in this version, so the value of paramet er Sib3orSib4 is fixed and zero (S IB3 is sent). In the OMCR, you can configure the following parameters.
Table 3-3
SIB 3/SIB4 parameters that can be configured in the OMCR Parameter Description Cell ID Measurement Quantity for Cell Selection and Reselection Sintrasearch Configuration Tag The thres hold that triggers the intra-frequency measurement in the cell reselection proc ess
Parameter Name Cid QualMeas SIntraSearchPre SIntraSearch
SInterSearchPre SInterSearch
Sintersearch Configuration Tag The thres hold that triggers the inter-frequency measurement in the cell reselection proc ess
SSearchHCS Pre SSearchHCS
SsearchHCS Configuration Tag The threshold that triggers the measurement in the HCS cell reselection proc ess
SSearchRat
The threshold that triggers the inter-system measurement in the cell reselection proc ess
SHCS RatPre SHCS Rat
SHCS,RAT Configuration Tag 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 QRxLevMin DltaQRxLevMinP r DltaQRxLevMin
The minimum cell quality requirement level The minimum cell receive electrical level threshold DeltaQrxlevmin Configuration Tag The minimum cell receive electrical level threshold increment
27
3.1.2.4
SIB5/SIB6
SIB5 and SIB6 are mainly used to configure the common transport channels and common physical channels. SIB5 c ontains the parameters of t he auxiliary c ommon control channels in IDEL mode; S IB6 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 S IB6 does not exist, the UE in the connected mode also uses SIB5. Whether broadcasting the paramet ers of common transport channels and common physical channels through SIB 5 or SIB 6 can be configured at OMCR (Sib5orSib6). SIB6 is not broadcasted in this version, so the value of parameter Sib5orSib6 is fixed and zero (SIB 5 is sent).. In the OMCR, you can configure the following parameters.
Table 3-4
SIB 5/SIB6 parameters that can be configured in the OMCR Parameter Description Transmission format index. It is used to indicate the attributes
Parameter Name
TfsIndex
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 TfNum TrBlk Num RlcSize TTI CodingRate RateMatchAttr CRCSize NiNumPerFrame CPCId MichP wr MichChCode SttdInd SttdInd
Channel Type Transport Format Number Number of Transport Blocks Transport Block Size Transmission Time Interval Coding Rate Rate Matching Attribute CRC Size Number of NI per Frame MICH Common Physical Channel ID MICH Power(dB ) MICH Channelisation Code No. MICH S TTD Indicator AICH S TTD Indicator
28
Parameter Name ChCode AichTranTime AichPwr MplexPos PCHInd DlScraCode ChCode ChCode SttdInd CPCId PichPwr SttdInd Signature AvailSubChanNum AvailableSF PreamScraCode PcpichP wr PunctLimit SignalFach TfcsIndex
Parameter Description AICH Channelisation Code No. AICH Transmission Timing AICH Power Multiplexing Position Indicator for S CCP CH Carrying PCH SCPICH Scrambling Code SCPICH Channelisation Code No PICH Channelisation Code No. PICH S TTD Indicator Pich Common Physical Channel ID PICH Power PCCP CH S TTD Indicator Available Signature PRACH A vailable Subchannel Number PRACH A vailable SF PRACH Preamble Scrambling Code P-CP ICH Power(dBm) Puncturing Limit FACH Usage Index of a transmission format combination set. It must be configured for S-CCPCH or PRACH. Number of transmission format combination sets. It must be
CtfcNum
configured for S-CCPCH or PRACH. ID of a transmission format combination. It must be configured
Ctfc SCCP CHUsage SccpchOffset SttdInd DlScraCode DlChCodeNo SlotFmt SttdInd
for S-CCPCH or PRACH. SCCP CH Usage SCCP CH Frame Timing Offset SCCP CH S TTD Indicator S-CCPCH Scrambling Code S-CCPCH Channelisation Code No. S-CCPCH Slot Format P-CP ICH S TTD Indicator
29
3.1.2.5
SIB7
SIB7 is the system information block that is updated periodic ally. The timer of S IB7 is calculated as follows: Expiration timer = MA X(32,SIB _REP * ExpirationTimeFactor) SIB_REP is the transmission interval of SIB 7 and is obtained at the time of broadcast scheduling; ExpirationTimeFactor is the timeout factor of S IB7 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 cont ains the parameters needed in the c alculation of the P RACH preamble power. The table below lists the parameters that can be configured in the OMCR.
Table 3-5
SIB 7 parameters that can be configured in the OMCR Parameter Description Initial Dy namic Persistence Level
Parameter Name DynPstLevelInit
3.1.2.6
SIB11/SIB12
SIB11/S IB12 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 SIB 11 or SIB 12 is sent can be configured at OMCR (Sib11orSib12).SIB 12 is not broadcasted in this version, so t he value of Sib11orSib12 is fixed and zero (S IB11 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 encry ption or not. SIB15 is not broadc asted in this version. For more details, refer to ZTE UMTS Location Service Feature Description.
30
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.
Table 3-6
SIB 18 parameters that can be configured in the OMCR Parameter Description Mobile Country Code of Neighbouring Cell Mobile Network Code of Neighbouring Cell
Parameter Name NMCC NMNC
3.1.2.9
SIB11bis
The content of SIB 11bis is same with SIB11, it can alleviate the lack of SIB11 space when there is too many adjacent cells. The parameter SIB11orSIB 11bis can specify if an adjacent cell information can be broadcast through SIB 11bis. So the adjacent cells information will broadcast by SIB11bis when the spac e of S IB11 is depleted.
Table 3-7
SIB 11bis parameters that can be configured in the OMCR (intra, inter,
inter-RA T adjacent cell information) Parameter Name SIB11ORSIB11BIS Parameter Description Specify if an adjacent cell information can be broadcast through S IB11bis
3.1.2.10
SIB19
The S IB19 contains Inter-RAT frequency and priority information to be used in
the cell. The frequency and priority E-UTRAN.
information is related to UTRA N or GSM or
If the parameter Absolute Priority Reselection Criteria Switch is set as 1,
SIB19 can be broadcast to UE; if If the parameter Absolute Priority Res election Criteria Switch is set as 0, RNC will not broadcast SIB19.
Table 3-8
Absolut e Priority Reselection Criteria Switch Parameter Description
Parameter Name
31
AbsPriReselS wch
Absolute Priority Reselection Criteria Switch
3.2
3.2.1
DSAR and Cell Bar Access

Overview of DSAR
RNC can exercise control over the access of UEs in case of emergencies (for ex ample, 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 int o the USIM by the carrier. An AC ranges between 0 and 15. 0 9: for common users; 1115: 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 P LMN is enabled and disabled by setting the DSA R function switch ( CsDsarS w or PsDsarS wh) 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 (CsDsarS w or PsDsarS wh ), If the DSA R function switch is set to RNC Controls Dynamically CS Domain DSA R (According to Load of Iu or Accessibility of Iu) / RNC Controls Dynamically PS Domain DSAR (According to Load of Iu or Accessibility of Iu) ( CsDsarS w or PsDsarS wh =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),
32
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 DSA R function switch is set to RNC Controls Dynamically CS Domain DSA R (According to Accessibility of Iu)) / RNC Cont rols Dynamically PS Domain DSA R (According to Accessibility of Iu)( CsDsarS w or PsDsarS wh =2 ): RNC detect the office direction or subsystem of CN is unavailable, RNC enables the DSA R 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 unreachable. RNC det ect CN is reachable, RNC disables the DSA R function of the domain. If the DSA R function switch is set to Switch On CS Domain DSA R by OMCR /Switch On PS Domain DSA R by OMCR ( CsDsarS w or PsDsarSwh =1), RNC enables the DSA R function directly.
3.2.1.2
Determine the Barred AC

After the DSAR function is enabled, RNC determines the barred AC in the following t wo ways: Polling mode: When the DSAR polling/non - polling switch is enabled
(CS DsarPollingS wh or PSDsarP ollingS wh= 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 eac h period based on the parameters CSB arAcNum and PSBarAcNum. RNC selects the AC barred list by adopting the following method: i When the DSAR function is enabled, RNC starts the counter CS DsarCounter or
33
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 bas ed on its current value. ii At the end of each polling period (set through the parameter BarInterval ), the counter value increments: CSDsarCounter=CS DsarCounte r + CsBarAcNum (CsBarAcNum: refers to the number of A Cs barred from access to the CS domain in each period. This parameter can be set through the background) PSDsarCounterPS=PSDs arCounterPS + PsBarAcNum (PsBarAcNum: refers to the number of A Cs barred from access to the PS domain in each period. This parameter can be set through the background) iii The start number of the A C barred from access to the CS domain: CSDsarCounter mod 10; the end number of the AC barred from access to the CS domain: (CS DsarCount er + CsBarAcNum - 1) mod 10. The start number of the A C 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:
34
Figure 3-2
Example of
DSAR polling mode
Timer (minute) 1
AC0 AC1 AC2 AC3 AC4 AC5 AC6 AC7 AC8 AC9
2 o o o x x o o o
4 o o
6 x x o o
7 o
10
x x
o x x x o x x x o o x x o o o o o o o o
x CS Domain O PS Domain
x x o o o o x x x x
o o
Non-polling mode: When the DSAR polling/non - polling switch is disabled (CS DsarPollingS wh or PSDsarP ollingS wh=0), the non-polling mode is adopt ed 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 bas ed on the parameters CsACB arredOmcr 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 S pecific Access Class Barred List. When enabling t he 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
35
registration (PagingLoca BarS wh ) 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 Cont rol Parameters For PLMN Of MIB or Paging P ermission with Access Cont rol 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 A C of the specific domain; if both CS and PS domains need to be barred, then RNC fills the information based on the A C of the PS and CS domains.
3.2.1.4
Disable the DSAR

RNC disables the DSA R in any of the following cases: When CSDsarS wh/PSDsarS wh is set to Switch Off CS Domain DSAR by OMCR /Switch Off PS Domain DSAR by OMCR (Cs DsarS w or PsDs arS wh =0), RNC disables the DSA R function of the CS/PS domain on t he PLMN and stops and clears the started counter. When CSDsarS wh/PSDsarS wh 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 DSA R (According to Accessibility of Iu)/ RNC Controls Dynamically CS Domain DSA R (According to Load of Iu or Accessibility of Iu)/ RNC Controls Dynamically PS Domain DSA R (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 count er. Note: When Iu-Flex mode is adopted, the DSAR function of related domain is disabled only when the CS or PS domain of all lu interfaces recovers from overload or lu interface is restored.
36
When the value of CSDs arS wh/PSDsarS wh 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. Note: When Iu-Flex mode is adopted, the DSAR function of related domain is 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 CellBarAcS wh.
3.2.2.1
Enable the CBA

When CellB arAcS wh is set to OMCR enables CBA ( CellBarAcS wh=1), RNC enables the CBA function. When CellBarAcS wh is set to RNC dynamically enables and disables CBA (CellB arAcS wh=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 parameters configuration, please refer to ZTE UMTS Overload Cont rol Feature Description U9.2)and enables the CBA if the uplink is overloaded.
3.2.2.2
Determine the Barred AC

If CellB arPollingS wh is set to Polling Mode ( CellBarPollingS wh =1), RNC sets the number of ACs barred from c ell 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
37
counter CellB arCounter is already started (in the case of changeover between the two modes "OMCR enabl es 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 = CellB arCounter + 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 CellBarPollingS wh is set to Non -Polling Mode (CellB arPollingS wh =0), RNC selects the ACs barred from cell access based on the value of the background parameter ACBarredOmc r. 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 co unter. When CellBarAcS wh is set to RNC dynamically enables and disables CBA (CellB arAcS wh=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 count er. When the value of CellBarAcS wh 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 count er.
38
3.3
3.3.1
RRC Connection Setup and Release

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

UE Target Node B Source Node B Drift RNC Source RNC
RRC
RRC CONNECTION REQUEST [CCCH]
RRC
Transport channel selection
Conditionsetup RRC connection on DCH Load balance of RRC
RL Set up
ConditionRL setup successful RRC
RRC CONNECTION SETUP [CCCH] RRC CONNECTION SETUP COMPLETE [DCCH]
RRC
RRC
RRC
Conditionexpiration of waiting RRC CONNECTION COMPLETE RL Delete
ConditionRL setup failed RRC RRC CONNECTION REJET [CCCH] RRC
Conditionsetup RRC connection on FACH RRC RRC CONNECTION SETUP [CCCH] RRC CONNECTION SETUP COMPLETE [DCCH] RRC
RRC
RRC
ConditionRRC connection reject
RRC
RRC CONNECTION REJET [CCCH]
RRC
39
3.3.1.1
Establishing an RRC Connection over a Dedicated Transport channel

When receiving the RRC CONNECTION RE QUES T message from a UE, the RNC specifies the channel over which the RRC connection is to be established according to the parameter InitRrcOnDch ( Ty pe 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 St ate), the RNC selects to establish the RR C connection over the DCH according to the Establishment_cause (for example, the UE initiates a call) in the RRC CONNE CTION REQUES T 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 Int erface 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 CONNE CTION SE TUP message. Ot herwise, 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 ag ain if RNC havent received RRC CONNECTION SE TUP COMPLE TE message from UE after 0.7 seconds. The RNC receives the RRC CONNECTION SE TUP COMPLE TE message from t he UE, indicating that the RRC connection is established successfully. The process ends.
40
3.3.1.2
Establishing an RRC Connection over a Common Transport channel

When receiving the RRC CONNECTION RE QUES T message from a UE, the RNC specifies the channel over which the RRC connection is to be established according to the paramet er 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 Init RrcOnDch is set to 3 , 4, or 6, the RNC establishes the RRC connection according to the Establishment _cause:if servic es 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 SCCP CH = Initial UE Identity mod K. K represents the number of FACH SCCP CH channels of the cell. The RNC sends the RRC CONNE CTION SE TUP message over the SCCPCH channel to the UE and sends the S RB configuration. RNC will retransmit RRC CONNECTION SETUP message on ce again if RNC havent received RRC CONNECTION SE TUP COMPLE TE message from UE after 0.7 seconds. The RNC receives the RRC CONNECTION SE TUP COMPLE TE message from t he UE, indicating that the RRC connection is established successfully. The process ends.
3.3.2
3.3.2.1
Handling Abnormality in the RRC Connection Setup

Wireless Link Setup Failure
If the radio link setup fails, the RNC sends the RRC CONNE CTION RE JECT 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 RE JECT message to the time of sending access request) during which the UE has to wait. The paramet er Twait can be configured in the OMCR.
41
3.3.2.2
Failure to Receive RRC Connection Setup Response From UE

If RNC havnt received RRC CONNECTION SETUP COMPLE TE for waiting 5 seconds from the first transmitting of RRC CONNE CTION 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 Interfac e 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 releas ed 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 indic ation (RB2, RB 3 or RB 4) 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.
42
Figure 3-4
RRC connection release flow

UE Target Node B Source Node B Drift RNC Source RNC
ConditionRRC connection release on DCH RRC RRC CONNECTION RELEASE [DCCHUM RLC RB1] RRC CONNECTION RELEASE COMPLETE [DCCHUM RLC RB1] RRC
RRC
RRC
RL Delete
ConditionRRC connection release on FACH RRC RRC CONNECTION RELEASE [CCCHDCCHAM RLC RB2] RRC
RRC
RRC CONNECTION RELEASE COMPLETE [CCCHDCCHAM RLC RB2]
RRC
As shown in the above figure, the RNC sends RRC CONNE CTION RELEASE message to the UE using S RB1 to request for the release of the RRC connection. The RNC fills in information in the RRC CONNE CTION 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 c an 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 CONNE CTION RE LEASE COMPLE TE message in the UM mode to the RNC and starts the T308 timer. When the T308 timer expires, the UE retransmits the RRC CONNE CTION RELEASE COMPLE TE 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 FA CH state receives the RRC release request from the RNC. The UE only
43
sends the RRC CONNE CTION RELEASE COMPLE TE message for once. The RNC releases the radio link from the Iub interface (for more det ails, 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 CONNE CTION RELEASE message over the CCCH channel to the UE or sends the RRC CONNE CTION RELEASE message through SRB 2 to the UE, requesting the UE to release the RRC connection. The UE in the FA CH state receives the RRC release request from the RNC. The UE only sends the RRC CONNECTION RELEASE COMPLE TE message through the CCCH for only one time. The RNC receives the RRC CONNE CTION RE LEASE COMPLE TE 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 CONNE CTION RELEASE COMP LE TE message from the UE after sending the RRC CONNECTION RE LEASE message to the UE, the RNC retransmits the RRC CONNE CTION RELEASE message. The paramet er NreTran specifies the maximum retransmit event count of the RRC CONNE CTION RE LEASE 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 RE LEASE COMPLE TE message, the RNC considers the RRC connection release complete and releases the local resources.
3.4
3.4.1
RRC Connection Redirection

Redirection for Load Reduction
This function support that RNC can reject a RRC connection setup request because of overload or congestion .
44
When receiving a RRC CONNE CTION REQUEST which the establishments cause is not Emergency call, RNC check whether system is overloaded or congestion. RCP Overload The system queries the RCP CP U utilization rate every 2s, the CPU utilization rate for load control is the average value of the continuous eight times. When the CPU utilization rat e 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 rat e is lowered to 75% in a cycle, the system sets R to 1 and then cancels the restriction on servic e admission. The RCP is returned from congested to normal. When receiving a RRC Connection request, if R is less than 1, RNC generat e 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 rec eived overload message from CN Without Iu Flex or Network sharing(i.e. the RNC connect with only one MS C and one SGS N) 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
45
RRC Connection failed to establish bec ause of Radio Resource Congestion If S witch 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 CONNE CTION RE JECT to UE , reject this RRC connection to reduce load on Uu interface. In the message RC CONNECTION RE JECT, 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 dont provide related information, RNC wont fill IE Redirection Information; If t he value of P riRedirectRat is 1 which inform system Prior to Inter-Frequency, secondly to Inter-RAT (P rior to GSM Cell , RNC will fill IE Redirection Information with the information of a cell which satisfy the following conditions: The cell coverage t he area which is same with or including serving cells, and the cell doesnt belong to the RNCs inter -frequency adjac ent cell.( remark 1) The frequency of the cell is different with all t he inter -frequency adjacent cells of the current cell If t herere 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 ther es not any cell satisfied the above conditions, RNC will check if theres any inter-RAT adjacent cell satisfied the related conditions. If the value of P riRedirectRat 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 t he area which is same with or including serving cells, and the cell doesnt belong to the RNCs inter -frequency adjac ent cell.( remark 1)
46
The frequency of the cell is different with all t he inter -frequency adjacent cells of the current cell The GSM cells coverage the area which is same with or including serving cells in case of CS service. If t herere GSM cells satisfied the above c ondit ions, RNC will fill the BCCH A RFCN, frequency information of the GSM cells in IE Redirection Information, and the number of the GSM cells wont over 32. If therere 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 P riRedirectRat 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 cells. the cell doesnt belong to the RNCs inter -frequency adjac ent 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 obt ain the cells satisfied the following conditions: The GSM cells coverage the area which is same with or including serving cells in case of CS service. The E-UTRA cells coverage the area which is same with or including serving cells in case of PS service. the cell doesnt belong to the RNCs inter -frequency adjac ent cell. RNC support both E-UTRA FDD cells and E-UTRA TDD cells.
47
The parameter EutranCellType is the type of the E -UTRA cell. The value 0 means EUTRA N FDD; the value of 1 menas EUTRA N TDD. If the Pre-redirection info IE is included in the RRC CONNE TION REQUES T, 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 t herere E -TRA cells satisfied the redirection conditions, and there are E -UTRA FDD adjacent cells, and t he UE support only the E-UTRA FDD frequency, then RNC can redirect the UE to the E-UTRA FDD cells. If t herere E -TRA cells satisfied the redirection conditions, and there are E-UTRA TDD adjacent cells, and t he UE support only the E-UTRA TDD frequency, then RNC can redirect the UE to the E-UTRA TDD cells. If therere E -TRA cells satisfied the redirection conditions, and there are bothe E -UTRA FDD adjac ent 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 theres not any cell satisfied the above conditions, RNC will check if theres any inter-frequency adjacent cell satisfied the related conditions. If theres neither inter -frequency cell nor inter-RAT cell satisfied the related conditions, RNC wont fill IE Redirection Information. Remark 1: the purpose of RRC connection redirection is reduce the RNCs load, hence the frequency information filled in IE Redirection Information doesnt belong to the current RNC. Remark 2: When RRC CONNE CTION REJE CT 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 net work deployment, if the operat or has a mature GSM system
48
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 EmgCallRdtS witch (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 EmgCallRdtS witch is 1 There are GSM cells coverageing the area which is same with or including serving cells. If the above conditions are satisfied, RNC will reject the RRC connection request, and fill the relat ed IEs in message RRC Connection Reject: (1) Rejection cause=unspecified (2) (3) Wait time=2s Redirection Information: the value of sub-IE Inter- RAT info is GSM. RNC wont 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.
49
3.5
3.5.1
NAS Message Transfer

NAS Message Forwarding Flow
Figure 3-5
UE
NAS message forwarding flow

Target Node B Source Node B Drift RNC Source RNC CN
Initial direct transper message PreconditionRRC set up success RRC INITIAL DIRECT TRANSFER [DCCHAM RLC RB3] RRC Conditionwithout Iu signaling connection SCCP Link set up
Conditionwith Iu signaling connection RANAP DIRECT TRANSFER RANAP
Uplink direct transper RRC UPLINK DIRECT TRANSFER [DCCHAM RLC RB3/RB4] RRC
RANAP
DIRECT TRANSFER
RANAP
Downlink direct transper RANAP RRC DOWNLINK DIRECT TRANSFER [DCCHAM RLC RB3/RB4] RRC DIRECT TRANSFER RANAP
The NAS message forwarding involves thre e occasions: initial direct trans fer, uplink direct trans fer, and downlink direct transfer. Initial direct transfer: When the RNC rec eives the INITIAL DIRECT TRA NSFE R message from the UE, it establishes the Iu int erface connection (for more details, refer to the section "Establishing Iu Interface Connection"). Uplink direct trans fer: The RNC receives the UPLINK DIRECT TRA NSFER message from the UE, forwards the information in the message to the CN, and then sends the DIRE CT TRASFER message to the CN. Downlink direct transfer: The RNC receives the DIRE CT TRASFE R message from the
50
CN, forwards the information in the DIRE CT TRASFE R message to the UE, and transmits the DOWNLINK DIRECT TRA NSFER message to the UE.
3.5.2
3.5.2.1
Setting up and Releasing the Iu Interface Connection

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 set up of the Iu interfac e 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 int erface connection
UE RRC INITIAL DIRECT TRANSFER EP
RNC
CN
RRC
Without Iu connection
NNSF SCCP connection setup RANAP INITIAL UE MESSAGE Iu connection has already Setup RANAP DIRECT TRANSFER EP RANAP
After the RRC connection setup, the UE sends the initial message to the RNC (for det ails, refer to the section NAS Message Trans fer). The RNC receives the direct transfer message from the UE. The RNC judges whether the Iu interface connection bet ween itself and the CN. If yes, the RNC sends direct trans fer 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 s election 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
51
initial direct trans fer 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 REQUES T ACK NOWLEDGE 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 releas e. The Iu interface release may be initiated by the CN or RNC. The Iu int erface connection release initiated by the CN involves two occasions: Iu interface connection release caused by service releas e; 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 t he UE initiates simultaneous multiple s ervices and then releases all simultaneous multiple services.
Figure 3-7
UE
UE in DCH state releases the Iu interface connection

Node B RNC CN
Iu Release Command Iu CS service bearer release Iu PS service bearer release
Iu Release Complete Iu signaling bearer release
RRC connection release
RL release
52
The CN sends the IU RELEASE REQUES T message to the RNC. The RNC releases the RAB resources and returns the IU RELEASE COMP LE TE 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 servic es are provided concurrently.
Figure 3-8
UE
Release the service of one domain

Node B RNC CN
Iu Release Command Iu CS or PS service bearer release Iu Release Complete
Iu signaling bearer release

RL reconfigure
RB release
Signaling connection release
The CN sends the IU RELEASE REQUES T message to the RNC. The RNC releases the RAB resources and returns the IU RELEASE COMP LE TE message to the CN. 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 corres ponding domain.
53
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 FA CH state releas es the Iu int erface connection

UE Node B RNC CN
Iu Release Command Iu CS service bearer release Iu PS service bearer release
Iu Release Complete Iu signaling bearer release
RRC connection release
The CN sends the IU RELEASE REQUEST message to the RNC. The RNC releases the RAB resources and returns the IU RELEASE COMP LE TE message to the CN. 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
UE
Node B
RNC
CN
Iu Release Command Iu CS service bearer release Iu PS service bearer release Paging type 1 Cell update Iu Release Complete Iu signaling bearer release RRC connection release
The CN sends the IU RE LEASE 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
54
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 RE LEASE COMPLE TE 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 interfac e connection release caus ed by signaling releas e
UE
Node B
RNC
CN
Iu Release Command Iu Release Complete Iu signaling bearer release RRC connection release
Condition UE in DCH
RL release
The CN s ends the IU RELEASE RE QUES T message to the RNC. The RNC returns the IU RELEASE COMP LE TE 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.
55
Figure 3-12
The RNC initiates the Iu interface connection release

UE Node B
RNC
CN
ConditionSignaling connection release originated by UE
Signaling Connection Release Indication Iu Release Request Iu Release Command Iu Release Complete
Iu signaling bearer release
Signaling Connection Release
The RNC initiates the Iu interfac e 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 releas e caused by the UE signaling connection release. For example, the UE performs location updating in the CS domain and rout e updating in the PS domain. When the loc ation 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 CONNE CTION RELEASE INDICATION message to the RNC. When the RNC rec eives the SIGNALLING CONNE CTION RELEASE INDICATION message, if the domain where the signaling connection is releas ed is the only CN domain of the UE, the RNC releas es the RRC connection. Otherwis e, the RNC sends the IU RE LEAST REQUEST message, requesting for the release of the Iu interfac e. When the CN receives the IU RELEAS T REQUES T message, if the CN decides to release the Iu interface connection, it sends the IU RE LEASE COMMA ND message to the RNC. The RNC returns the IU RELEASE COMPLE TE message and releas es the Iu interface signaling bearer.
56
3.6
3.6.1
Paging
Paging Flow
According to the paging initiators, the paging involves the following occasions:
Figure 3-13
Paging flow
UE NodeB DRNC SRNC CN
ConditionPAGING originated by CN
PAGING
ConditionUE in IDLEPCH PAGING TYPE 1 ConditionUE in DCHFACH PAGING TYPE 2
ConditionPAGING originated by RNC , on Iur interface PAGING REQ ConditionPAGING originated by RNC ConditionUE in IDLEPCH PAGING TYPE 1 ConditionUE in DCHFACH PAGING TYPE 2
Receive the paging message from the CN and broadcast message through the Node B under the RNC. The RNC sends paging messages of PAGING TYPE 1 to the UE in Idle or PCH state and sends the paging message of PAGING TYPE2 to the UE in the CELL_FA CH 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 TYPE 1 to the UE in Idle or PCH state and sends the paging message of PAGING TYPE2 to the UE in the CELL_FA CH or CELL_DCH state The local RNC initiates paging that must span an Iur interface.
57
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_P CH 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 chanc e of receiving the paging message by the UE, the RNC repeatedly sends the paging message of PAGING TYPE 1 to the UE. The maximum ret ransmit event count (PagingSendTimes) can be configured in the OMCR. The PCH channel has a corresponding PICH physical channel. The page indicat or (P I) is transmitted over the P ICH channel, with each PI correspon ding to a group of UEs. The following lists the formula for calculating the P I: 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 P ICH 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 (PichP wr) will be. The table shows the relations between the parameter Np and the transmit power. Number of PIs in each frame 18 36 72 144 Number of repeated bits in the PICH 16 8 4 2 Transmit power of the PICH in comparison with that of the CPICH -7 -7 -5 -2
For saving power, the UE in the Idle or PCH state monitors the PICH channel in the Discontinuous Rec eption (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
58
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 = 2 frames In the OMCR, you can configure three DRX cycle lengt h coefficients: CS Domain DRX Cycle Length Coefficient (Kcs), PS Domain DRX Cycle Length Coefficient (Kps), and UTRA N DRX Cycle Length Coefficient (K Utran). 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 Lengt h Coefficient in t he 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 Cy cle 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 P CH in a cell
k
59
DRX cycle length = 2 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 P CH 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 proc ess 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 lay er.
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 A rea Paging. RNC will send PAGING to the c ells which belong to anot her LA C 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 als o match the virtual LACs, if the LAC of PAGING match virtual LACs of some cell, these cells will send the paging to UE even t hough the LA C of CE LL is not the LAC of PA ING. If the boundary of TWO LACs is at the boundary of Two RNCs, IUR PA ING is sent if the adjacent RNC support Virtual LA C paging. In order to decreas e paging load, RNC adopt Virtual LA C paging only for repeated CS Voice Paging.
60
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 net work. User domain security: Provide secure access measures for UEs. Application domain security: Provide safe information exchange for the users and the servic e applications bet ween 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 attribut es. The encryption and integrity protection belong to the sec urity mechanism of the net work access security.
3.7.1
Security Mode Control Flow

The security mode control flow specifies the algorithms and parameters of the encryption and integrity prot ection between t he UE and the RNC. The CN sends the s ecurity mode control message t o 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 COMPLE TE message to the CN. Figure 3-14 shows the process of RAN resource allocation.
61
Figure 3-14
Security mode control flow

Source RNC
UE
CN
RANAP
Security Mode CommandEP
RANAP
Condition arithmetic is not supported

RANAP Security Mode RejectEP RANAP
Condition arithmetic is supported

RRC RRC Security Mode CommandEP Security Mode CompleteEP RRC RRC RANAP RRC Security Mode FailureEP RRC RANAP Security Mode RejectEP RANAP Security Mode CompleteEP RANAP
As shown in the above figure, the RNC receives the SECURITY MODE COMMAND message from the CN. The message contains the Integrity Prot ection Information and Encryption Information, or the Integrity Protection Information only. The Integrity Protection Information contains two parts: integrity protection algorit hm and integrity protection key commended by CN. The integrity protection currently supports two algorithms: UIA1 and UIA 2. The E ncryption 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 t he security algorithms of phase 1, UEA2 and UIA2 support higher rate and efficiency, better security performance. ZTE UTRAN supports all of these security algorit hms.. The control procedure of security mode is as following: When RNC receive SE CURITY MODE COMMA ND message from CN, RNC selects security algorithms according to: Encryption algorithm selection:
62
The RNC judges whet her it supports the encry ption algorithm configured in the CN. If not, the RNC ret urns the SE CURITY MODE RE JECT message to CN. The encryption algorithm (EncryAlg ) and integrity protection algorithm (IntegrityAlg ) supported by the RNC can be configured in the OMCR.
ii
If theres intersection bet ween 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 algorit hm. 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 algorit hm inters ection supported by CN and RNC. If the selection result is UEA0 or theres no intersection in CN, RNC a nd UE, RNC select on encryption. If it isnt the first time, RNC selects the encryption algorithm used for the UE. Integrity prot ection algorithm selection:
The RNC judges whether it supports the integrity protection algorithm configured in the CN. If not, the RNC returns the SECURITY MODE RE JECT message to CN. The encryption algorithm (EncryAlg) and integrity protection algorithm (IntegrityAlg ) supported by the RNC can be configured in the OMCR.
If theres intersection between the algorithms sup ported by CN and RNC, RNC selects the algorithms supported by RNC and CN, and holds the priority queue of the algorithms commended by CN.
RNC judges whether the UE supports the algorithm. If t he RNC lacks the capability of the UE, it queries the c apability of the UE. For det ails, refer to the section Querying the UE Capability.
63
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 algorit hm 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 RB 2.After the RNC sends a SECURITY MODE COMMAND message to the UE through S RB2, it then provides integrity protection for the downlink data carried through SRB 2. After the UE receives an encryption command, if processing fails, it returns the SECURITY COMMAND FA ILURE message to the RNC. After the RNC receives the failure message, it recovers the suspended SRBs and sends the SECURITY COMMA ND REJE CT message to the CN. After the UE receives the encryption command, if processing succeeds, it returns the SECURITY COMMAND COMPLE TE message to t he RNC. After the RNC receives the SECURITY COMMAND COMPLE TE message, it recovers the suspended S RBs and implements integrity protection and encryption for all uplink and downlink signaling of all S RBs. The RNC returns the SECURITY COMMAND COMPLE TE message to the CN.
After the security mode is terminated, the enc ryption and int egrity 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.
64
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. Aft er receiving the message, the UE sends the UE CAPAB ILITY INFORMATION message with the UE capability. The RNC finally sends the UE CAPABILITY INFORMATION CONFIRM message as confirmation.
Figure 3-15
UE
Querying the UE capability

Source RNC
RRC RRC RRC
UE Capability Enquiry UE Capability Information UE Capability Information Confirm
RRC RRC RRC
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 CAPAB ILITY 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 -P DSCH supported or not, supporting SCCP CH, DP CH, and HS -PDS CH or not, downlink capability when the HS -DS CH is configured concurrently, physical layer of the SH-DSCH, and whether it is allowed to estimate the capability of the HS-P DSCH and HS-S CCH 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 informatio n query failed.
65
3.7.2
3.7.2.1
Encryption Algorithm and Parameters

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 UTRA N are generated, including enc ryption keys (CK) and integrity protection key (IK). The VLR/SGS N initiates the authentication request to the HE/HLR. The HE/HLR generates multiple authentication vectors. Through the aut hentication responses, the HE/HLR brings these authentication vectors to the V LR/SGS N. The VLR/SGSN saves the authentication vectors, selects a vector, and initiat es an aut hentication 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 t he same. If yes, the authentication succeeds. The net work 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 t he MA C layer (TM mode). Currently, the encryption algorithms of the Uu interfac es of the 3G system have three types: UEA0, UEA1 and UEA2. UEA 0 means that the dat a of the Uu interface is not encrypted. UEA1 means that the KASUMI algorithm based encryption algorit hm f8 should be adopted, and UEA2 means that the SNOW 3G algorithm based enc ryption algorithm f8. The parameters of encryption algorithm f8 include: Encryption key CK COUNT-C (it varies with time) BEARER (bearer tag) DIRE CTION (direction indication)
66
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 enc ryption key; the cipher text can decrypted into plain text by adding the same encryption key. The following describes the enc ryption and decryption proc ess.
Figure 3-16
Encryption and decryption process

DIRECTION LENGTH COUNT-C DIRECTION LENGTH
COUNT-C
BEARER
BEARER
CK
f8
CK
f8
KEYSTREAM BLOCK
KEYSTREAM BLOCK
PLAINTEXT BLOCK Sender UE UE/RNC RNC
CIPHERTEXT BLOCK Receiver RNC/UE RNC UE
PLAINTEXT BLOCK
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 STA RT to form the first 20 bits of the initial COUNT-C, and the left bits are all 0s. The S TART value is sent by the UE to the RNC through the uplink message (such as CE LL UPDATE message) of the
67
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. DIRE CTION: 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 corres ponds to each RB. BEARER = RB ID - 1 LENGTH: It indicat es the lengt h of the key stream block. DA TA: 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 UIA 2 algorithms, thereinto UIA1 means that the KASUMI based encryption algorithm f9, and UIA2 means that the SNOW 3G based enc ryption
algorithm f9. F9 algotithm is as shown in the figure blow.
Figure 3-17
Using the f9 algorithm for integrity protection

COUNT-I DIRECTION FRESH COUNT-I DIRECTION FRESH
MESSAGE
MESSAGE
IK
f9
IK
f9
MAC -I
SenderUE/RNC
XMAC -I
ReceiverRNC/UE
UE RNC
RNC UE
The input parameters of the algorithm include IK (integrity protection key), COUNT-I (integrity SN), FRESH (random number generated in the network), DIRE CTOR (direction bit), and MESSAGE (signaling message). Based on thes e input parameters, the transmit ting end calculates the authentication code MAC -I using f9 algorit hm. MAC-I is added to
68
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 MA C-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 algorit hm, the initial value of HFN consists of the first 20 bits of the parameter S TART and all 0s in the left bits. The HFN inc reases once every RRC SN period. The SN is a 4-bit RRC-S N. The RRC-S N can be obtained from each RRC PDU. IK: integrity key. It is obtained in the authentication process. FRESH: The FRESH parameter prevents th e users from using t he signaling message repeatedly. FRESH is a random number generated by the RNC. The FRESH varies with each UE. In the security mode, the FRES H is sent to the UE. DIRE CTOR: 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 t he RAB assignment message (only including the set up a nd 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 RE QUES T message does not contain Allocation/ Retention priority) or specify that the RAB does not have the queuing c apability (that is, Queuing Allowed carried in the RAB ASSIGNMENT REQUES T message is 0 (queuing not allowed)), RNC will judge whether the RAB has the queuing capability according t o whether t he ForcQueS wi is enabled or not.
69
If ForcQueS wiA MR is enabled, the AMR service has the queuing capability and its maximum queue time can be set with the paramet er TTrueQForced. If ForcQueS wiA MR is disabled, the AMR service cannot queue. If ForcQueS wiCS64 is enabled, the CS64k service has the queuing capability and its maximum queue time can be set with the parameter TTrueQForced. If ForcQueS wiCS64 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 res ources where services are distributed, RRC resources, and Iu int erface connection. The ZTE RA N 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
T_RLFAILURE, NumInSyncInd , please refer to <ZTE UMTS Node B Management Feature Description U9.2>. )
configuration including NUMOUTSYNCIND, Figure 3-18 Radio link failure
CRNC
Node B
RADIO LINK FAILURE INDICATION
70
If the cause value in the RA DIO LINK FA ILURE INDICATION message indicates that the radio link is unrecoverable or the radio link is recoverable but the RNC has not received the message RA DIO 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 messag es over the RLC layer but has not received responses from the UE, the RNC ret ransmits the message. If the retransmit event count reaches 15, the RLC layer reset. If the res et 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 FA CH state sends the CELL UPDATE message t o the RNC. The value of the parameter AM_RLC error indication (RB2, RB 3 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 indic ating 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 t he 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 met hods, 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
71
is interrupted due to poor radio quality, if the UE in DCH state detects an RlC Unrecoverable Error or RL FA ILURE and the durations of all service re -establishment timers (T314 and T315) are neither 0 nor in timeout state, the UE will s witch to FACH state and reports the Cell Update to UTRA N through a CCCH, expecting the UTRA N 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 UTRA N 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 UP DATE 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 wit h a cause value to the RNC. The RNC t hen s ets up a radio connection to the UE. See the following figure.
72
Figure 3-19
UE
Call re-establishment
NODEB RNC
Cell update
Reconfigure SRB on FACH
RL deletion request RL deletion response RL setup request RL setup response

Reconfigure SRB and DRB
Cell update confirm PhyCH info RB info

Condition: UE reconfigured Physical channel
Physical channel reconfiguration complete
RB reconfiguration complete
As shown in the above figure, the UE in the DCH state sends the CELL UPDATE message to t he 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. Delet e 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 se ction 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
73
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 updat e call re-establishment procedure to improve t he call completion rate and reduce the call drop rate, when RNC detected the Uu response timeout or RL fail or RLC unrecover Error
74
Figure 3-20
UE
Call re-establishment triggered by Network

Node B RNC
Condition: rb setup procedure RB SETUP Set the timer 1 for response on Uu Condition: handover procedure ACTIVE SET UPDATE/TRCH RECONFIGURATION/PHYCH RECONFIGURATION
Set the timer 1 for response on Uu
Condition: RNC receive Radio link failure from NodeB
RL FAIL
Set the timer 1 for RL restore from NodeB
Condition: RNC detected DL RLC unrecover error DL RLC unrecover error detected
Condition: call re-establishment process is initialed Condition: RNC receive cell update before timer 1 expiry CELL UPDATE Condition: RNC doesn't receive any message on Uu befor timer 1 expiry Timer 1 expiry RL DEACTIVE Set timer 2 for CELL UPDATE CELL UPDATE Call re-establishment process Condition: RNC doesnt receive CELL UPDATE before timer 2 expiry Exception handling
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
75
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 rec eiving 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 immediat ely. Note: (i)For rb setup procedure and soft-handover procedure, If the RNC receive the CELL UPDA TE before the Timer1 expires, the RNC trigger the call re-establishment proc edure and doesnt sent RADIO LINK ACTIVA TION COMMA ND message to the NODEB. For hard procedure, the call will be released. (ii)If RNC is handling another RRC procedure, the call is opened, the call re-establishment is triggered
re-establishment will not be triggered. (iii)when RNC receive CELL UP DA TE, 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 servic e 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 RA DIO LINK ACTIVATION COMMA ND message to the Node B, to which all radio links of the UE active set belong . Here CHOICE Delay ed Activation Update of the cell related to every radio link is set to Deactivate in order to deactivate the radio link.
76
Upon rec eiving the RA DIO 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 CE LL UP DATE 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
3.11.1
Managing the Iub Interface Radio Link

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 FA CH; establishing the RAB over the DCH, HS -DS CH, 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 REQUES T message carrying dedicated channel configuration parameters to the control port of the Node B; The RNC receives the RADIO LINK SE TUP RESPONSE message from t he control port of the Node B; The RNC establishes the user plane bearer over the dedicated transport channel and
77
shared transport channel (if 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 -DS CH; Establishing the RAB over the DCH, E-DCH, or HS -DS CH; reconfiguring the RAB over the DCH, E-DCH, or HS -DS CH; Provisioning the CS+PS servic e 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 cont rol, code resource allocation, and application for the dedicated channels, it sends the RADIO LINK RECONFIGURATION P REPARE message to each Node B; When the RNC applies for the channels for the s ervices, if the admission cont rol 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 rec eives the RADIO LINK RECONFIGURATION READY messages from each Node B. If the RNC receives the RADIO LINK RE CONFIGURATION FA ILURE 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 RE CONFIGURATION CA NCEL message to the Node Bs with successful reconfiguration or reconfiguration timeout.
78
If the setup of any transmission link fails, the radio link reconfiguration fails. The RNC sends the RA DIO LINK RECONFIGURATION CA NCEL 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 RA DIO LINK RECONFIGURATION CA NCEL COMMIT message to the related Node Bs. The RNC and Node Bs adopt the new configuration data simultaneously. 3 Canc el RL synchronization reconfiguration If t he RNC judges that the radio link synchronization must be reconfigured, it sends the RADIO LINK RE CONFIGURATION CA NCEL 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
3.12.1
Managing the Iur Interface Radio Link

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 RA DIO LINK RE CONFIGURATION 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 RA DIO 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
79
sends the RA DIO LINK RECONFIGURATION COMMIT message to the Node B. The SRNC and the DRNC simultaneously activates the new configuration dat a 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 RE CONFIGURATION CA NCEL message to the DRNC. The DRNC receives the RA DIO LINK RECONFIGURATION CA NCEL MESSAGE from the SRNC, cancels the rec onfiguration task, deletes the transmission bearer, and then sends the RA DIO 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.
80
Figure 3-21
UE
RB reconfiguration
Source RNC
RRC
Radio Bearer Reconfiguration
RRC
ConditionRB reconfiguration success RRC ConditionRB reconfiguration failed RRC Radio Bearer Reconfiguration Failure RRC Radio Bearer Reconfiguration Complete RRC
ConditionRNC didnt receive response message from UE after 5 second
Return the status before RB reconfiguration
As shown in the above figure, the RNC sends the RA DIO BEAER RE CONFIGURATION 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 BEARE R RECONFIGURATION COMP LE TE 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 RA DIO BEARE R RE CONFIGURATION message over the RRC connection to the UE. The RNC receives the RADIO BEARE R RE CONFIGURATION COMPLE TE message from the UE. If the RNC rec eives the RADIO BEARE R 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 ret urns to the status before the RB reconfiguration.
3.14
Iu Overload Control
When the traffic of Iu is overload, RNC sho uld take measures of overload control to
81
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 s etup request of UE exclude the reason of emergency call, RNC should check if the CN is overload first. If CN is overload and current net work have neither Iu Flex nor networkshare(MS C number is 1,SGS N 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 t he 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 tak e the load balance in the CN which is reachable and overload.
82
Figure 3-22
Iu overload control
RNC OVERLOAD
MSC Server
RNC OVERLOAD
SGSN
3.15
Deferred SIB11/12
In order to avoid the obvious interruption of services due to reading SIB 11, SIB11bis or SIB12, especially a lot of neighbouring cells are configured (over 20 neighboring cells for example). UE is allowed to send messages through RA CH or receive messages t hrough FACH before reading and storing SIB 11/12 information, whic h named deferred SIB11/12. RNC will include the IE Deferred measurement control UTRA N support in S IB3 message if the UTRAN support this feather. If UE receive this IE in SIB 3, then it can
add the IE Deferred measurement control reading into Radio Bear Reconfig Complete or RRC Connection Setup Complete or UTRA N Mobility informaion Confirm message, which notify UTRA N the incomplete reading S IB11/11bis/12. After switching t o a non CELL-DCH status, UE needs to complete SIB11/11bis/12 reading and storing, RNC will judge the ability of deferred SIB 11/12 according to whether the
DefSibSuptSwch is enabled or not. If DefSibS uptSwch is 1, RNC will include the IE Deferred meas urement cont rol UTRA N support In S IB3 Message. If DefSibS uptSwch is 0, RNC will not include the IE Deferred meas urement cont rol UTRA N support In S IB3 Message.
83
4
4.1
4.1.1
Configuration and Parameters

System Information Broadcasting Parameters
SIB1 Parameter List
Id 1 Abbreviate T300 Parameter name Waiting Time After UE Sending RRC CONNE CTION SETUP REQUES T Message(T300) Maximum Number of Retransmissions of the RRC CONNE CTION REQUES T Message (N300) T312 in Idle Mode)(Waiting Time for Receiving "In Sync" from L1 in Idle Mode (T312 in Idle Mode) Maximum Number of " In Sync" Received from L1 in Idle Mode (N312 in Idle Mode) Waiting Time After UE Sending CELL/URA UPDA TE Message(T302) Maximum Number of Retransmissions of the CELL/ URA UPDA TE Message (N302) Waiting Time After UE Sending UE CAPABILITY INFORMA TION Message(T304) Maximum Number of Retransmissions of the UE CAPABILITY INFORMA TION Message (N304) Period of Cell/URA Update When UE is in CELL_FACH/CE LL_PCH/ URA _PCH State(T305)(min) Waiting Time for Cell Reselection A fter UE is out of Service(T307) maximum number of retransmissions of the RRC CONNE CTION RELEASE COMPLE TE Waiting Time After Sending RRC CONNECTION RELEASE COMPLE TE Message in CELL_DCH State(T308) Waiting Time After Requesting Connection Establishment in Other System(eg. GSM) (T309) T312 in Connected Mode,Waiting Time for Receiving "In Sync" from L1 in Connected Mode (T312 in Connected
N300 T312Idle (RL synchronization) N312Idle
T302
N302
T304
N304
T305
10
T307
11
N308
12
T308
13
T309
14
T312Connected
84
Id
Abbreviate Mode)
Parameter name
N312 in Connected Mode,Maximum Number of "In Sync" 15 N312Connected Received from L1 in Connected Mode (N312 in Connected Mode) 16 T313 Waiting Time After DPCCH Established in CE LL_DCH State Losing Sychronization (T313) Maximum Number of Successive "Out of Sync" Received from L1(N313) Waiting Time for Completion of Cell Upate When Radio Link Fails and Radio Bearer(s) Associated with T314 Exist (T314) Waiting Time for Completion of Cell Upate When Radio Link Fails and Radio Bearer(s) Associated with T315 Exist (T315) Maximum Number of Successive "In Sync" Received from L1 During T313 is Activated ( N315) Waiting Time for Cell Selection/ Reselection After UE is out of Service in CELL_PCH/URA_P CH State(T316)(s) Mobile Country Code Mobile Network Code CN Domain Supported T3212 (hour) IMSI Attach and Detach Indicator Network Mode of Operation CS Domain DRX Cycle Length Coefficient PS Domain DRX Cycle Length Coefficient Modification Period Coefficient for MBMS Switch of T323 Broadcasting UEs Waiting Time of Sending Message Signaling Connection Release Indication(wit h cause)
17
N313
18
T314
19
T315
20
N315
21 22 23 24 25 26 27 28 29 30 31 32
T316 mobility MCC MNC CnDomain T3212Cs ATTIndCs NMOPs Kcs Kps MbmsModP rdC oeff T323S wch T323
85
4.1.2
4.1.2.1
SIB1 Parameter Configuration

T300
OMC Path Management-> RNC NE->RNC Radio Resource
Path:View-> Configuration
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER A ND TIMER ->Waiting Time A fter UE Sending RRC CONNE CTION SETUP REQUES T 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 t he time taken in RRC connection setup, provided that the quality at the air interface is desirable.
4.1.2.2
N300
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER A ND TIME R ->Maximum Number of Retransmissions of the RRC CONNECTION REQUEST Message (N300) Parameter Configuration
Configuration Description: If the Maximum Number of Ret ransmissions of t he RRC CONNE CTION RE QUES T 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 als o increases accordingly.
4.1.2.3
T312Idle
OMC Path
86
Management-> RNC
NE->RNC
Radio
Resource
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTE R AND TIME R ->Waiting Time for Receiving "In Sync" from L1 in Idle Mode (T312 in Idle Mode) Parameter Configuration
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
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER A ND TIMER ->Maximum Number of "In Sync" Received from L1 in Idle Mode (N312 in Idle Mode) Parameter Configuration
Configuration Description: The smaller the parameter, it is easier to judge whether the synchronization finishes, but the chance of fake synchronization also increas es; the larger the parameter, the higher the reliability, but it is more time consuming.
4.1.2.5
T302
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER A ND TIME R ->Waiting Time A fter UE Sending CE LL/URA UPDATE Message(T302) Parameter Configuration
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
87
to judge the occurrence of timeout, and the lower the flow processing efficiency.
4.1.2.6
N302
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER A ND TIME R ->Maximum Number of Retransmissions of the CELL/ URA UPDATE Message (N302) Parameter Configuration
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 m ore easy to judge that the flow fails.
4.1.2.7
T304
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER A ND TIME R ->Waiting Time After UE Sending UE CAPABILITY INFORMATION Message(T304) Parameter Configuration
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
88
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER A ND TIME R ->Maximum Number of Retransmissions of the UE CAPABILITY INFORMATION Message (N304) Parameter Configuration
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
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTE R AND TIMER -> Period of Cell/URA Update When UE is in CELL_FA CH/ CELL_PCH/ URA_P CH State(T305)(min) Parameter Configuration
Configuration Description: The smaller the parameter, the system updates cells and URA more frequently.
4.1.2.10
T307
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTE R AND TIMER ->Waiting Time for Cell Reselection Aft er UE is out of Service(T307) Parameter Configuration
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 net work, but this may
89
increase the load of the UE and the system.
4.1.2.11
N308
Management->Advanced Parameter Manage ->RNC Radio Resource Management ->N308 Parameter Configuration
Configuration Description: The smaller the parameter, the higher the chanc e of judging flow failure.
4.1.2.12
T308
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTE R AND TIME R ->Waiting Time After Sending RRC CONNECTION RELEASE COMP LE TE Message in CELL_DCH State(T308)
4.1.2.13
T309
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTE R AND TIME R ->Waiting Time After Requesting Connection Establishment in Other System(eg. GSM) (T309) Parameter Configuration
Configuration Description:If the system has not received the message after the waiting time, it considers the occurrence of timeout.
90
4.1.2.14
T312Connected
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTE R AND TIME R ->Waiting Time After Sending RRC CONNECTION RELEASE COMP LE TE Message in CELL_DCH State(T308) Parameter Configuration
Configuration Description: If the system has not received the message after the waiting time, it considers the occurrence of timeout.
4.1.2.15
N312Connected
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER A ND TIMER ->Maximum Number of "In Sync" Received from L1 in Connected Mode (N312 in Connected Mode) Parameter Configuration
Configuration Description: The smaller the paramete r, it is easier to judge whether the synchronization finishes, but the chance of fake synchronization also increas es; the larger the parameter, the higher the reliability, but it is more time consuming.
4.1.2.16
T313
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTE R AND TIMER ->Waiting Time After DP CCH Established in CELL_DCH State Losing Sychronization (T313)
91
Parameter Configuration
4.1.2.17
N313
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER AND TIME R ->Maximum Number of Successive "Out of Sync" Received from L1(N313) Parameter Configuration
4.1.2.18
T314
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTE R AND TIMER ->Waiting Time for Completion of Cell Upat e When Radio Link Fails and Radio Bearer(s) Associated with T314 Exist (T314) Parameter Configuration
4.1.2.19
T315
OMC Path
92
Management-> RNC
NE->RNC
Radio
Resource
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTE R AND TIMER ->Waiting Time for Completion of Cell Upat e When Radio Link Fails and Radio Bearer(s) Associated with T315 Exist (T315) Parameter Configuration
Configuration Description:If the system has not received the message after the waiting time, it considers the occurrence of timeout.
4.1.2.20
N315
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER A ND TIME R ->Maximum Number of Successive "In Sync" Received from L1 During T313 is Activated ( N315) Parameter Configuration
4.1.2.21
T316
Management->Advanced P arameter Manage ->INFORMATION ON THE CONS TA NTS OF THE UE COUNTER A ND TIMER -> Waiting Time for Cell Selection/ Reselection After UE is out of Service in CELL_PCH/URA_P CH State(T316)(s) Parameter Configuration
93
4.1.2.22
MCC
Management-> CN NAS Configuration Information ->Mobile Country Code Parameter Configuration
Configuration Description: The parameter specifies the mobile country code.
4.1.2.23
MNC
Management-> CN NAS Configuration Information ->Mobile Network Code Parameter Configuration
Configuration Description: The parameter specifies the mobile network code.
4.1.2.24
CnDomain
Management-> CN NAS Configuration Information -> CN Domain Supported Parameter Configuration
Configuration Description: The parameter specifies the supported CN domains.
4.1.2.25
T3212Cs
OMC Path Management-> RNC NE->RNC ->CN NAS Radio Resource
Management->Advanced Paramet er Manage
Information->Timer for
94
updating location periodically Parameter Configuration
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
Management-> CN NAS Configuration Information -> IMSI Attach and Detach Indicat or
4.1.2.27
NMOPs
Management-> CN NAS Configuration Information -> Network Mode of Operation Parameter Configuration
Configuration Description:0: Net work operation mode I indic ates that the Gs interface appears; 1: The network operation mode 2 indicates that the Gs interface does not appear.
4.1.2.28
Kcs
Management->Advanced P arameter Manage ->CN NAS Information ->CS Domain DRX Cycle Length Coefficient Parameter Configuration
Configuration Description: The parameter specifies the CS Domain DRX Cycle Length
95
Coefficient.
4.1.2.29
Kps
Management->Advanced P arameter Manage -> CN NAS Information ->PS Domain DRX Cycle Length Coefficient Parameter Configuration
Configuration Description: The parameter specifies the PS Domain DRX Cycle Length Coefficient.
4.1.2.30
MbmsModPrdCoeff
Management->Advanced Parameter Manage ->CN NAS Information->Modification Period Coefficient for MBMS Parameter Configuration
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 Res ource Management-> Advanced Parameter Manage->UE Timers and Constants Information -> Switch of T323 broadcasting Parameter Configuration
96
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
Path:View-> Configuration Management-> RNC NE-> RNC Radio Resource Management-> Advanced Paramet er Manage->UE Timers and Constants Information -> UE's Waiting Time of S ending Message "Signaling Connection Release Indic ation"(with
cause)(T323)(s) Parameter Configuration
Configuration Description: This parameter s pecifies indicates the int erval of reporting signaling connection release indication(wit h cause).
4.1.3
SIB2 Parameter List

Id 1 2 URA Num URA[4] Abbreviate Parameter name URA Number URA Identity
4.1.4
4.1.4.1

URANum
Management-> UtranCell-> UtranCell global Info ->URA Number Parameter Configuration
Configuration Description: The parameter specifies the number of URAs for the current cell. The system supports up to 4 URAs.
97
4.1.4.2
URA[4]
Management-> UtranCell-> UtranCell global Info ->URA Identity Parameter Configuration
Configuration Description: The parameter specifies the No. of the URA to which the current area belongs.
4.1.5
SIB3/SIB4 Parameter List

Id 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 Cid Sib3orSib4 QualMeas SIntraSearchPre SIntraSearch SInterSearchPre SInterSearch SSearchHCS Pre SSearchHCS SSearchRat SHCS RatPre SHCS Rat SLimitRat QQualMin QRxLevMin DltaQRxLevMinP r CellBarredInd InFreqReselInd TBarred Abbreviate Cell Identity Broadcast in either S IB3 or S IB4 Measurement Quantity for Cell Selection and Reselection Sintrasearch Configuration Tag Sintrasearch Sintersearch Configuration Tag Sintersearch SsearchHCS Configuration Tag SsearchHCS Ssearch,RA T SHCS,RA T Configuration Tag SHCS,RA T) Slimit,SearchRA T Qqualmin Qrxlevmin DeltaQrxlevmin Configuration Tag) Cell Barred Indicator Intra-Frequency Cell Re-Selection Indicator Tbarred Parameter name
98
Id 20 21 22 23
Abbreviate OperatorUseInd CellRs vExt ACBarredOmcr DltaQRxLevMin
Parameter name Cell Reserved for Operator Use Cell Reservation Extension Access Class N Barred Indicat or (N=09) DeltaQrxlevmin
4.1.6
4.1.6.1
SIB3/SIB4 Parameter Configuration

CId
Management-> UtranCell-> UtranCell global Info ->Cell Identity Parameter Configuration
Configuration Description: The parameter specifies the ID of a c ell and is used to distinguish different cells.
4.1.6.2
Sib3orSib4
Management-> UtranCell-> Cell Selection and Reselection ->Broadcast in either SIB3 or SIB4
4.1.6.3
QualMeas
OMC Path Management-> RNC Selection and NE->RNC Radio Resource Parameter
Management-> UtranCell-> Cell
Reselection ->Advanc ed
Manage ->Cell S election and Reselection ->Meas urement Quantity for Cell S election and Reselection
99
Configuration Description: If the parameter is set to 1, select CPICH Ec/No for measurement; if the parameter is set to 2, select CPICH RS CP for measurem ent.
4.1.6.4
SIntraSearchPre
Manage -> Cell Selection and Res election ->Sintrasearch Configuration Tag Parameter Configuration
Configuration Description: Configure this parameter so that the UE conducts intra-frequency measurement when the quality of the c urrent cell is lower than the threshold.
4.1.6.5
SIntraSearch
Manage -> Cell Selection and Res election ->Sintrasearch Parameter Configuration
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
100
Selection
and
Parameter
Manage -> Cell Selection and Res election ->Sintersearch Configuration Tag Parameter Configuration
Configuration Description: Configure this parameter so that the UE conducts inter-frequency measurement when the quality of the c urrent cell is lower than the threshold.
4.1.6.7
SInterSearch
Manage -> Cell Selection and Res election ->Sintersearch Parameter Configuration
Configuration Description: The parameter specifies the inter-frequency measurement threshold of cell reselection. The lower the threshold, it is easier for the UE to conduct inter-frequency measurement.
4.1.6.8
SSearchHCS Pre
Manage -> Cell Selection and Res election ->SsearchHCS Configuration Tag Parameter Configuration
Configuration Description: 0: Do not configure the parameter SsearchHCS; 1:configure the paramet er 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.
101
4.1.6.9
SSearchHCS
Manage -> Cell Selection and Res election ->SsearchHCS Parameter Configuration
Configuration Description: The parameter specifies the HCS adjacent cell measurement threshold of cell reselection. The lower the threshold, it is easier for the UE to conduct HCS adjacent cell measurement.
4.1.6.10
SSearchRat
Manage -> Cell Selection and Res election ->Ssearch,RAT Parameter Configuration
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 meas urement.
4.1.6.11
SHCSRatPre
Manage -> Cell Selection and Res election->SHCS, RAT Configuration Tag Parameter Configuration
102
Configuration Description: Configure this parameter so that the UE conducts inter-system adjacent cell measurement when the quality of the current cell is lower than the threshold.
4.1.6.12
SHCSRat
Manage -> Cell Selection and Res election ->S HCS,RAT Parameter Configuration
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
Manage -> Cell Selection and Res election ->Slimit,SearchRAT Parameter Configuration
Configuration Description: The parameter specifies the int er-system high HSC priority cell measurement threshold of cell res election. The lower the threshold, it is easier for the UE to conduct inter-system high HSC priority cell measurement.
4.1.6.14
QqualMinSib11
103
Manage -> Cell Selection and Res election ->Qqualmin Parameter Configuration
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
Manage -> Cell Selection and Res election ->Qrxlevmin Parameter Configuration
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
Manage -> Cell Selection and Res election -> DeltaQrxlevmin Configuration Tag
4.1.6.17
CellBarredInd
Manage -> Cell Selection and Res election -> Cell Barred Indicator
104
4.1.6.18
InFreqReselInd
Manage -> Cell Selection and Res election -> Intra-Frequency Cell Re-Selection Indicator.
4.1.6.19
TBarred
Manage -> Cell Selection and Res election -> Tbarred
4.1.6.20
OperatorUseInd
Reselection->Advanc ed
Manage -> Cell Selection and Res election -> Cell Reserved for Operator Use
4.1.6.21
CellRsvExt
Manage -> Cell Selection and Res election -> Cell Reservation Extension
4.1.6.22
ACBarredOmcr
105
Selection
and
Parameter
Manage -> Cell Selection and Res election ->Access Class N Barred Indicat or (N=09) Parameter Configuration
Configuration Description: The parameter specifies the barred access level and is configurable in the OMCR.
4.1.6.23
DltaQRxLevMin
Manage ->Cell Selection and Reselection -> Inc rement to the Minimum Required Received Level in the Cell (Delt aQrxlevmin) Parameter Configuration
Configuration Description: This parameter indicates the extension of Qrxlevmin, which means Qrxlevmin = Qrxlevmin + DeltaQrxlevmin.
4.1.7

Id 1 2 3 4 5 6 7 8 9 10 11 Abbreviated name SIB5orSIB 6 TfsIndex ChType TfNum TrBlkNum RlcSize TTI CodingRate RateMatchAttr CRCSize CPCId Parameter name Broadcast in either S IB5 or S IB6 TFS Index Channel Type Trans port Format Number Number of Trans port Blocks Trans port Block Size Transmission Time Int erval Coding Rate Rate Matching Attribute CRC Size MICH Common Physical Channel ID
106
Id 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42
Abbreviated name MichChCode NiNumPerFrame MichPwr SttdInd SttdInd AichTranTime AichPwr ChCode SCCP CHUsage SccpchOffset MplexPos PCHInd ChCode CPCId PichPwr SttdInd DlScraCode ChCode SttdInd Signature A vailSubChanNum A vailableSF PreamScraCode PcpichPwr PunctLimit DlScraCode DlChCodeNo SlotFmt SttdInd SignalFach TfcsIndex
Parameter name MICH Channelisation Code No. Number of NI per Frame MICH Power(dB ) MICH S TTD Indicator AICH S TTD Indicator AICH Transmission Timing AICH Power AICH Channelisation Code No. SCCP CH Usage S-CCPCH Frame Time Offset(chip) Multiplexing Position Indicator for S-CCPCH Carrying PCH PICH Channelisation Code No. Pich Common Physical Channel ID PICH Power PICH S TTD Indicator S-CP ICH Scrambling Code S-CP ICH Channelisation Code No S-CCPCH S TTD Indicator A vailable Signature PRACH A vailable Subchannel Number PRACH A vailable SF PRACH Preamble Scrambling Code P-CP ICH Power(dBm) Puncturing Limit S-CCPCH Scrambling Code S-CCPCH Channelisation Code No. S-CCPCH Slot Format S-CCPCH S TTD Indicator FACH Usage Tfcs Index
107
Id 43 44 45 46 47 48 49 50 51 52
Abbreviated name CtfcNum Ctfc TfcsIndex CtfcNum Ctfc SttdInd SttdInd SIB6IND PccpchInfSib5P re PccpchInfSib6P re CTFC Number CTFC Id Tfcs Index CTFC Number CTFC Id
Parameter name
P-CP ICH S TTD Indicator PCCP CH S TTD Indicator SIB6 Indicator PCCP CH Information in SIB5 Configuration Tag PCCP CH Information in SIB6 Configuration Tag
4.1.8
4.1.8.1
SIB5/SIB6 Parameter Configuration

SIB5orSIB6
OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx-> Modify Advanced Parameter-> SCCP CH-> Broadcast in either SIB5 or SIB6
4.1.8.2
TFS Index
Configure the parameter for the RA CH, FACH, PCH, and FA CH carrying the MCCH. OMC Path
Path of the paramet er 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-> UTRA N Cell XXX-> Modify Advanced Parameter -> RACH-> TFS Index
108
Path of the paramet er 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 FA CH carrying the MCCH: View->Configuration Management-> RNC NE->RNC Radio Resourc e 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
109
4.1.8.7
TTI
OMC Path
4.1.8.8
Coding Rate
OMC Path
Path:View-> Configuration Management -> RNC Radio Resource Management-> Modify Advanced Parameter->Transmission Format Composition Set ->Coding Rate
4.1.8.9
RateMatchAttr
OMC Path
Path:View-> Configuration Management -> RNC Radio Resource Management-> Modify Advanced Parameter->Transmission Format Composition Set-> Rate Matching Attribut e
4.1.8.10
CRC Size
OMC Path
Path:View-> Configuration Management -> RNC Radio Resource Management-> Modify Advanced Parameter->Transmission Format Composition Set-> CRC Size
4.1.8.11
MICH Common Physical Channel ID

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter-> MICH
110
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
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter-> MICH
4.1.8.14
MichPwr
OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter-> MICH -> MICH Power(dB)
4.1.8.15
MICH STTD Indicator

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter-> MICH-> MICH S TTD Indicator
4.1.8.16
AICH STTD Indicator

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter->AICH->AICH STTD Indicat or
111
4.1.8.17
AichTranTime
OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran 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 Relat ed to Service->A ICH Power
4.1.8.19
AICH Channelisation Code No.

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter->AICH-> AICH Channelisation Code No.
4.1.8.20
SccpchUsage
OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx-> Modify Advanced Parameter-> SCCP CH -> SCCP CH Usage
4.1.8.21
SccpchOffset
OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx-> Modify Advanced Parameter-> SCCPCH-> S-CCP CH Frame Time Offset(chip)
112
4.1.8.22
MplexPos
OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx-> Modify Advanced Parameter-> SCCP CH-> Multiplexing Position
4.1.8.23
PCHInd
OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx-> Modify Advanced Parameter-> SCCP CH-> Indicator for S-CCPCH Carrying P CH
4.1.8.24
PICH Channelisation Code No.

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter -> PICH-> PICH Channelisation Code No.
4.1.8.25
PICH Common Physical Channel ID

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced P arameter -> PICH -> P ICH Common Physical Channel ID
4.1.8.26
PICH Power
OMC Path
Path:View-> Configuration Management -> RNC Radio Resource Management->Modify Advanced Parameter->Power Control not Relat ed to Service->P ICH Power
113
4.1.8.27
PICH STTD Indicator

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Param eter -> PICH
4.1.8.28
S-CPICH Scrambling Code

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Paramet er->S CPICH-> S-CP ICH Scrambling code
4.1.8.29
S-CPICH Channelisation Code No.

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanc ed Parameter->SCP ICH-> S-CPICH Channelisation Code No.
4.1.8.30
S-CCPCH STTD Indicator

OMC Path View-> Configuration Management-> RNC NE->RNC Radio Resource
Path:
Management-> UtranCell->Advanced Parameter Manage -> S-CCP CH -> S-CCPCH STTD Indicator
4.1.8.31
Signature
OMC Path View-> Configuration Management-> RNC Parameter NE->RNC Manage Radio Resource
Path:
Management-> UtranCell->Advanced Signature
->PRACH->A vailable
114
4.1.8.32
AvailSubChanNum
Path:
Management-> UtranCell->Advanced Parameter Manage ->PRA CH ->PRACH A vailable Subchannel Number
4.1.8.33
AvailableSF
Path:
Management-> UtranCell->Advanced Parameter Manage ->PRA CH ->PRACH A vailable SF
4.1.8.34
PreamScraCode
OMC Path View-> Configuration Management-> RNC Parameter NE->RNC Manage Radio Resource ->PRACH
Path:
Management-> UtranCell->Advanced Preamble Scrambling Code
->PRA CH
4.1.8.35
PcpichPwr
OMC Path
Path: View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx-> CellSetupP arameters
4.1.8.36
PunctLimit
Management-> UtranCell->Advanced Parameter Manage ->P RACH ->Puncturing Limit
115
4.1.8.37
S-CCPCH Scrambling code

OMC Path Management-> RNC NE->RNC Manage Radio Resource ->S-CCPCH
Management-> UtranCell->Advanced P arameter Scrambling Code
->SCCP CH
4.1.8.38
S-CCPCH Channelisation Code No.

OMC Path Management-> RNC NE->RNC Manage Radio Resource ->S-CCPCH
Management-> UtranCell->Advanced P arameter Channelisation Code No
->SCCP CH
4.1.8.39
SlotFmt
Management-> UtranCell->Advanced Parameter Manage ->S CCP CH ->S-CCP CH Slot Format
4.1.8.40
S-CCPCH STTD Indicator

Management-> UtranCell->Advanced Parameter Manage ->SCCP CH ->S-CCPCH STTD Indicator
4.1.8.41
SignalFach
OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran
116
cell->Utran cell xx->Modify Advanced Parameter-> FACH-> SignalFach
4.1.8.42
TfcsIndex
OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter-> PRACH-> TFCS Index
4.1.8.43
CtfcNum
OMC Path
Path:View-> Configuration Management -> RNC Radio Resource Management->Modify Advanced Parameter->Transmission Format Composition Set of PRA CH
4.1.8.44
Ctfc
OMC Path
Path:View-> Configuration Management -> RNC Radio Resource Management->Modify Advanced Parameter->Transmission Format Composition Set of PRA CH
4.1.8.45
TfcsIndex
OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx-> Modify Advanced Parameter-> SCCP CH
4.1.8.46
CtfcNum
OMC Path
Path:View-> Configuration Management -> RNC Radio Resource Management->Modify Advanced P arameter-> Transmission Format Composition Set of SCCP CH -> CTFC Number
117
4.1.8.47
Ctfc
OMC Path
Path:View-> Configuration Management -> RNC Radio Resource Management->Modify Advanced Parameter->Transmission Format Composition Set of SCCPCH-> CTFC Id
4.1.8.48
P-CPICH STTD Indicator

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter->PCP ICH
4.1.8.49
P-CCPCH STTD Indicator

OMC Path
Path:View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter-> PCCPCH
4.1.8.50
SIB6 Indicator
OMC Path Management-> RNC NE->RNC Radio Resource -> S IB6
Management-> UtranCell->Advanced P arameter Manage Indicator
-> UtranCell
4.1.8.51
PCCPCH Information in SIB5 Configuration Tag

OMC Path Management-> RNC NE->RNC Radio Resource -> PCCPCH
Management-> UtranCell->Advanced Paramet er Manage ->UtranCell Information in SIB5 Configuration Tag
118
4.1.8.52
PCCPCH Information in SIB6 Configuration Tag

OMC Path Management-> RNC NE->RNC Radio Resource -> PCCPCH
Management-> UtranCell->Advanced P arameter Manage Information in SIB6 Configuration Tag
->UtranCell
4.1.9
SIB7 Parameter List

Id 1 2 3 4 Abbreviated name DynPstLevelInit SIB7Originator E XP TIMFACTOR PRACHSIB 6PRE Parameter name Initial Dy namic Persistence Level SIB7 Originator Expiration Time Factor Dynamic Persistence Level Information of SIB 6 PRACH in SIB7 Configuration Tag
4.1.10
4.1.10.1

DynPstLevelInit
Management-> UtranCell->Advanced P arameter Manage -> UtranCell -> Initial Dynamic Persistence Level
4.1.10.2
SIB7Originator
Management-> UtranCell->Advanced Parameter Manage -> UtranCell ->SIB 7 Originator
4.1.10.3
EXPTIMFACTOR
OMC Path
119
Management-> RNC
NE->RNC
Radio
Resource -> Expiration
Management-> UtranCell->Advanced Parameter Manage Time Factor
->Ut ranCell
4.1.10.4
PrachSib6Pre
OMC Path Management-> RNC NE->RNC Radio Resource -> Dynamic
Management-> UtranCell->Advanced Parameter Manage
-> UtranCell
Persistence Level Information of SIB6 PRA CH in SIB7 Configuration Tag
4.1.11
4.1.11.1

SIB11orSIB12
OMC Path
Path: View-> Configuration Management-> RNC Radio Resource Management->Utran cell->Utran cell xx->Modify Advanced Parameter->UE Measurement Configuration In System Information -> Broadcast in either SIB11 or S IB12
4.1.12
4.1.12.1
SIB11bis Parameter Configuration

SIB11orSIB11bis
Management-> UtranCell-> Neighbouring Cell->Sib11orSib11bis
120
4.2
Parameters related to Connection Setup and Release
4.2.1
Parameter List
Id 1 2 3 4 5 6 7 8 9 10 11 Abbreviated name NReTran Twait N308 FDDFreqRngNum GsmBARangeNum GsmLRange[32] GsmURange[32] Luarfcn [32] Uuarfcn[32] InitRrcLBSw InitRrcOnDch Parameter name Maximum number of retransmission of the RRC CONNE CTION RELEASE Wait Time for RRC Connection Reestablis hment (s) maximum number of retransmissions of the RRC CONNE CTION RELEASE COMPLE TE Number of FDD UMTS Frequency Range Number of GSM BA Range GSM Lower Range GSM Upper Range UARFCN(Nlow) UARFCN(Nupper) Load Balance Switch of Initial RRC Procedure Type of Transport Channel for Initial RRC Connection Setup Wait Time for RADIO BEARE R RE CONFIGURA TION COMPLE TE when CE LL_DCH to CELL_FACH
12
TRbRec fgCmpDtoF
4.2.2
For more details on the T3212CS description, refer to the section 4. 1.2.2611.
4.2.2.1
NReTran
Management->Advanced Parameter Manage ->RNC Radio Resource Management ->Maximum Number of Retransmissions of the RRC CONNECTION RE LEASE Message
121
Parameter Configuration Description: The parameter specifies the number of the RRC
Configuration
CONNE CTION RELEASE messages retransmitted by the RNC after the UE does not return the RRC CONNECTION RELEASE COMPLE TE message. If the value of this parameter decreases, the possibility of process failed will increase.
4.2.2.2
Twait
Management->Advanced Parameter Manage ->RNC Radio Resource Management ->Wait Time for RRC Connection Reestablis hment Parameter Configuration
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
Management->Advanced Parameter Manage ->RNC Radio Resource Management ->N308 Parameter Configuration
Configuration Description: The smaller the parameter, the higher the chanc e of judging flow failure.
4.2.2.4
FDDFreqRngNum
122
Management-> RPLMN Range Information -> Number of FDD UMTS Frequency Range
4.2.2.5
GsmBARangeNum
Management-> RPLMN Range Information -> Number of GSM BA Range
4.2.2.6
GsmLRange[32]
Management-> RPLMN Range Information -> GSM Lower Range Parameter Configuration
Configuration Description: The value range of GSM Lower Range must be consistent with that of GSM Upper Range.
4.2.2.7
GsmURange[32]
Management-> RPLMN Range Information -> GSM Upper Range Parameter Configuration
Configuration Description: The value range of GSM Upper Range must be consistent with that of GSM Lower Range.
4.2.2.8
Luarfcn [8]
123
Management-> RPLMN Range Information -> UARFCN (Nlow)
4.2.2.9
Uuarfcn[8]
Management-> RPLMN Range Information -> UARFCN(Nupper)
4.2.2.10
InitRrcLBSw
Management-> UtranCell->Advanced Parameter Manage ->Balance Information ->Load Balance Switch of Initial RRC P rocedure
4.2.2.11
InitRrcOnDch
Management->Advanced Parameter Manage ->RNC Radio Resource Management -> Type of Transport Channel for Initial RRC Connection Set up Parameter Configuration
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 t he FA CH 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.
124
4.2.2.12
TRbRecfgCmpDtoF
OMC Path
Path:View-> Configuration Management->RNC NE-> RNC Radio Res ource Management-> Advanced Parameter Manage->RNC Configuration Supplement Information -> Wait Time for RA DIO BEARE R RE CONFIGURATION COMP LE TE when CELL_DCH to CELL_FA CH(s) Parameter Configuration
Configuration Description: This parameter specify the time interval the RNC has to wait before receiving the RA DIO BEARER RE CONFIGURATION COMPLE TE when the RNC orders the UE Leaving CELL_DCH to CE LL_FACH.
4.3
4.3.1
DSAR Parameters
Parameter List
Id 1 2 3 4 5 6 7 8 9 10 11 12 13 Abbreviate CsDsarS wh PsDsarSwh CSDsarPollingSwh PSDsarPollingS wh CSBarAcNum PSBarAcNum BarInterval PagingLocaB arS wh CellBarAcSwh CellBarAcNum CellBarPollingSwh CsACBarredOmcr PsACBarredOmcr Parameter name Switch of CS Domain DSA R Switch of PS Domain DSAR Switch of Polling in CS Domain DSA R Switch of Polling in PS Domain DSA R Number of Barred AC in CS Domain Number of Barred AC in PS Domain Time Int erval of Barred AC Switch of Paging and Location/ Registration Restriction CellBarPollingSwh
Number of Cell Barred AC
Switch of Polling in Cell Restriction CS Domain Specific Access Class N Barred Indicator PS Domain Specific Access Class N Barred
125
Id
Abbreviate Indicator
Parameter name
14 15
UpdaSIB 3CelNum UpdS IB3Celnt
Number of Cells Updating SIB3 Time Int erval Updating S IB3 among Cells
4.3.2
4.3.2.1
CsDsarSwh
OMC Path View->Configuration Management-> RNC NE-> RNC Radio Resource
Path:
Management-> UTRAN Cell DSAR Parameter Configuration
->-UTRA N Cell Global Infomation >Switch of CS Domain
Configuration Description: The parameter value is: 0: Switch Off CS Domain DSAR by OMCR, DSA R 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
Path:
Management-> UTRAN Cell DSAR Parameter Configuration
->-UTRA N Cell Global Infomation >Switch of PS Domain
126
Configuration Description: The parameter value is: 0: Switch Off PS Domain DSAR by OMCR, DSAR function is closed 1: Switch On PS Domain DSA R 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
Path:
Management-> UTRAN Cell Domain DSA R Parameter Configuration
->-UTRA N Cell Global Infomation >S witch of P olling in CS
Configuration Description: The paramet er 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
Path:
Management-> UTRAN Cell Domain DSA R Parameter Configuration
->-UTRA N Cell Global Infomation >Switch of Polling in PS
Configuration Description: The parameter value is 0 when access restriction in PS domain is not by polling met hod., and 1 when access restriction in PS domain is by
127
polling method.
4.3.2.5
CSBarAcNum
Path:
Management-> UTRAN Cell in CS domain Parameter Configuration
->-UTRA N Cell Global Infomation >Number of Barred AC
Configuration Description: For polling method, if the value of this parameter increases, the amount of AC restricted in CS domain will increase.
4.3.2.6
PSBarAcNum
Path:
Management-> UTRAN Cell in PS domain Parameter Configuration
->-UTRA N Cell Global Infomation >Number of Barred AC
Configuration Description: For polling method, if the value of this parameter increases, the amount of AC restricted in PS domain will increase.
4.3.2.7
BarInterval
Path:
Management-> UTRAN Cell ->Advanced Parameter Manage ->Time Int erval of Barred AC(s) Parameter Configuration
128
Configuration Description: For polling method, if the value of this parameter increases, the restriction interval for the restricted users will increase, i.e. these users cant 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 SIB 3 update times will increase which increases system load.
4.3.2.8
PagingLocaBarSwh
Path:
Management-> UTRAN Cell
->-UTRAN Cell Global Infomation > Switch of Paging and
Location/ Registration Restriction Parameter Configuration
Configuration Description: When t he 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
Path:
Management-> UTRAN Cell ->Advanced Parameter Manage -> Switch of Cell Restriction Parameter Configuration
Configuration Description: The parameter value is: 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.
129
4.3.2.10
CellBarAcNum
Path:
Management-> UtranCell->Advanced Parameter Manage Cell Barred AC Parameter Configuration
->Utran Cell
->Number of
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
Path:
Management-> UTRAN Cell ->Advanced Paramet er Manage -> Switch of Polling in Cell Restriction Parameter Configuration
Configuration Description: The parameter value is 0 when cell restriction is not by polling method., and 1 when cell restriction is by polling met hod.
4.3.2.12
CsACBarredOmcr
Path:
Management-> UTRAN Cell -> UTRAN Cell Global Infomation -> CS Domain Specific Access Class N Barred Indicat or Parameter Configuration
130
Configuration Description: Bit0~9 correspond AC0~ 9, bit value = 0 means barred, 1 means not barred, Bit10~15 is res erved and should always set to 1. Default value of this parament is 65535(All AC is not barred).
4.3.2.13
PsACBarredOmcr
Path:
Management-> UTRAN Cell -> UTRAN Cell Global Infomation -> PS Domain Specific Access Class N Barred Indicat or Parameter Configuration
Configuration Description: Bit0~9 correspond AC0~ 9, bit value = 0 means barred, 1 means not barred, Bit10~15 is res erved and should always set to 1. Default value of this parament is 65535(All AC is not barred).
4.3.2.14
UpdaSIB3CelNum
Path:
Management->Advanced Parameter Manage -> UpdaSIB 3CelNum Parameter Configuration
-> RNC Radio Resource Management
Configuration Description: This parameter indicates the number of cells updating S IB3 when Iu overloads or is not accessible. The value of this parameter is larger, more c ells need to updat e 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 SIB 3,the load of Iu change more slowly, but Ping-P ong of the load of Iu happens more difficultly, the signaling connection of Uu will increase smoothly.
131
4.3.2.15
UpdSIB3Celnt
Path:
Management->Advanced Parameter Manage -> UpdS IB3Celnt Parameter Configuration
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
4.4.1
Paging Parameters
Parameter List
Id 1 2 3 4 5 6 7 8 9 Abbreviated name KUtran PagingSendTimes Kcs Kps Np PichPwr VirtualLac VLacPaingInd RNCFEA TSWITCH21 Parameter name UTRA N DRX Cycle Length Coefficient Sending Times of Paging Message CS Domain DRX Cycle Length Coefficient PS Domain DRX Length Coefficient Number of Paging Indicators per PICH Frame PICH Power Vitrual Location Aera Code Vitrual LAC Paging Support Indication Vitrual LAC Paging Support Indication
132
4.4.2
For details on configuring the PichP wr parameter, refer to the section SIB5/S IB6 Parameter Configuration .
4.4.2.1
KUtran
Management->Advanced Parameter Manage ->RNC Radio Resource Management ->UTRAN DRX Cycle Lengt h Coefficient
4.4.2.2
PagingSendTimes
Management-> UtranCell->Advanced Parameter Manage -> UtranCell ->Sending Times of Paging Message Parameter Configuration
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 int erface messages, the Uu interface becomes more time consuming.
4.4.2.3
Kcs
Management->Advanced P arameter Manage ->CN NAS Information ->CS Domain DRX Cycle Length Coefficient
133
4.4.2.4
Kps
Management->Advanced P arameter Manage -> CN NAS Information ->PS Domain DRX Cycle Length Coefficient
4.4.2.5
Np
Management-> UtranCell->Advanced P arameter Manage ->PICH ->Number of Paging Indicators per PICH Frame Parameter Configuration
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 18 36 72 144 Number of repeated bits in the PICH 16 8 4 2 Transmit power of the PICH in comparison with that of the CPICH -7 -7 -5 -2
4.4.2.6
DltaQRxLevMin
Management->Advanced Paramet er Manage Service -> PICH Power
-> Power Control
not Related to
134
Configuration Description: This parameter indicates the extension of Qrxlevmin, which means Qrxlevmin = Qrxlevmin + DeltaQrxlevmin.
4.4.2.7
VirtualLac
Management-> UtranCell->Advanced Parameter Manage->Utran Cell->VirtualLac Parameter Configuration
Configuration Description: This parameter indicates the Virtual LA C of the CELL. if the CELL is at the boundary of LAC, the Virtual LA C is set as the neighbour LA C.
4.4.2.8
VLacPaingInd
Management->Advanced Parameter Manage Parameter Configuration
-> 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 View-> Configuration Management-> RNC NE->RNC Ground Resource
Path:
Management-> Network Element Information->A djacent RNC Office->Adjacent RNC Office-3-> RNCFEATSW ITCH21 Parameter Configuration
Configuration Description: This parameter indicates the adjacent RNC support Virtual
135
LAC Paging or not. If adjacent RNC support, set it as 1.otherwise 0
4.5
4.5.1
Ciphering Parameters
EncryAlg
Management->Advanced Parameter Manage ->RNC Radio Resource Management ->Encryption Algorithm
4.6
4.6.1
Integrity Protection Parameters

IntegrityAlg
Management->Advanced Parameter Manage ->RNC Radio Resource Management ->Integrity Protection Algorithm
4.7
4.7.1
AMR Service Forced Queue Parameters

Parameter List
Id 1 2 Abbreviate ForcQueSwiAMR TTrueQForc ed Parameter name Forced Queue S witch for AMR Service Maximum Time in the True Queue when Service be Forced into Queue
136
4.7.2
4.7.2.1
ForcQueSwiAMR
OMC Path View-> Configuration Management-> RNC NE->RNC Radio Resource -> Forced
Path:
Management->Advanced P arameter Manage Queue Switch for AMR Service Parameter Configuration
->Global Access Control
Configuration Description: If t he switch is set to open, the AMR supports queue function even though queue isnt supported in the relevant RAB assignment message.
4.7.2.2
TTrueQForced
OMC Path View-> Configuration Management-> RNC NE->RNC Radio Resource -> Maximum
Path:
Management->Advanced Parameter Manage
->Global Access Control
Time in the True Queue when Service be Forced into Queue Parameter Configuration
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.
137
4.9
4.9.1
RRC Connection Redirection Parameters

Parameter List
Id 1 2 3 4 Abbreviate EmgCallRdtS witch PriRedirectRat RrcRdtSwch EutranCellTy pe Parameter name Emergency Call Redirect Switch Prior Redirect RA T Indicator Switch of RRC Redirection Triggered by Radio Resource Congestion EUTRA N Cell Type
4.9.2
4.9.2.1
EmgCallRdtSwitch
OMC Path Management-> RNC NE-> RNC Radio Resource
View-> Configuration
Management->Advanced Parameter Manage Parameter Configuration
Configuration Description: 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 Parameter Configuration
Configuration Description:
138
0: system wont provide the information of redirection 1: Prior to Inter-Frequency, secondly to Int er-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 (P rior to GSM), Secondly to Inter-Frequency 4: Prior to Int er-RAT (PS prior to E-UTRA, CS Prior to GSM), Secondly to Inter-Frequency
4.9.2.3
RrcRdtSwch
OMC Path
Path:View-> Configuration Management->RNC NE-> RNC Radio Res ource Management-> Utran Cell -> Advanced Parameter Manage -> Ut ranCell > RrcRdtSwch
Configuration Description: 0: RRC Redirection will not be Triggered by R adio Resource Congestion 0: RRC Redirection will be Triggered by Radio Resource Congestion
4.9.2.4
EutranCellType
OMC Path Management-> RNC NE-> RNC Radio Resource
View-> Configuration
Management->External Eutran Cell->External Eutran Cell XXX->E utran Cell Type Parameter Configuration
Configuration Description: 0:EUTRA N FDD
139
1:EUTRA N TDD
4.10
4.10.1
Iu Overload Control
TigOR
Management->Advanced P arameter Manage
-> Iu Interface Timers and Constants
Information-> Timer for Ignoring all OVERLOA D Message or Signalling Point Congested Information (TigOR) (s)
4.10.2
TinTR
Management->Advanced P arameter Manage
-> Iu Interface Timers and Constants
Information-> Timer for Not Allowing to Increase Traffic (TinTR) (s)
4.11
4.11.1
Deferred SIB11/12
Parameter List
Id 1 2 Abbreviate DefSibSuptSwch IntraRptQSib3 Parameter name Switch of Deferred SIB11/11bis/12 Support Intra-frequency reporting quantity SIB3 when
SIB11/11bis/12 deferred reading
4.11.2
4.11.2.1
DefSibSuptSwch
OMC Path
140
Management->RNC
NE-> RNC
Radio
Resource
Management-> UtranCell-> Cell Setup Parameters -> Switch of Deferred SIB11/11bis/12 Support Parameter Configuration
Configuration Description: 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->RNC NE-> RNC Radio Resource -> UTRA N
Management-> UtranCell->Advanced
Parameter
Manage
Cell-> Intra-frequency reporting quantity SIB3 when SIB 11/11bis/12 deferred reading Parameter Configuration
Configuration Description: This parameter indicates when S IB11/11bis/12 are deferred reading, the intra -frequency reporting quantity for RA CH report in RRC connection request message.0: CP ICH Ec/No,1: CPICH RSCP
4.12
4.12.1
Direct Tunnel
Parameter List
Id 1 Abbreviate SupportDTS witch
Support DT Switch
Parameter name
141
4.12.2
4.12.2.1
SupportDTSwitch
OMC Path View-> Configuration Management->RNC NE ->RNC Ground Resource
Path:
Management-> Transmission Configuration-> NE Information Configuration->S GSN -> Support DT Switch Parameter Configuration
Configuration Description: Value=0, the function Direct Tunnel is forbidden Value=1, the function Direct Tunnel is permitted
4.13
4.13.1
Call Re-establishment
Parameter List
Id 1 Abbreviate TWaitRlRestore Parameter name Time of Waiting for INDICATION Waiting time length for A CTIVE SE T UP DATE COMPLE TE Time 3 WaitRbCompTimer Interface Switch of CS Call Re-establishment Triggered by 4 CsReestSwitch0 Receiving the CELL UPDATE Message from UE when SRNC is in Stable Status Switch of CS Call Re-establishment Triggered by 5 CsReestSwitch1 Receiving the CELL UPDATE Message from UE when SRNC is in Handover Flow 6 CsReestSwitch2 witch of CS Call Re-establishment Triggered by Receiving the CELL UPDATE Message from UE of Waiting for RB RADIO LINK RES TORE
TWaitActSetUpCmp
Setup/Reconfiguration/Release Response over Uu
142
when SRNC is in RAB Setup Flow 7 CsReestSwitch3 Switch of CS Call Re-establishment Triggered by RAN Network when S RNC is in Stable Status Switch of CS Call Re-establishment Triggered by RAN network when SRNC is in Handover Flow Switch of CS Call Re-establishment Triggered by RAN network when SRNC is in RAB Setup Flow Switch of PS Call Re-establishment Triggered by 10 PsReestSwitch0 Receiving the CELL UPDATE Message from UE when SRNC is in Stable Status Switch of PS Call Re-establishment Triggered by 11 PsReestSwitch1 Receiving the CELL UPDATE Message from UE when SRNC is in Handover Flow witch of PS Call Re-establishment Triggered by 12 PsReestSwitch2 Receiving the CELL UPDATE Message from UE when SRNC is in RAB Setup Flow 13 PsReestSwitch3 Switch of PS Call Re-establishment Triggered by RAN Network when S RNC is in Stable Status Switch of PS Call Re-establishment Triggered by RAN network when SRNC is in Handover Flow Switch of PS Call Re-establishment Triggered by RAN network when SRNC is in RAB Setup Flow
CsReestSwitch4
CsReestSwitch5
14
PsReestSwitch4
15
PsReestSwitch5
4.13.2
4.13.2.1
TWaitRlRestore OMC Path View-> Configuration Management->RNC NE-> RNC Radio Resource
Path:
Management->Advanced Paramet er Manage
-> Time of Waiting for RA DIO LINK RES TORE INDICATION Parameter Configuration
143
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 View-> Configuration Management-> RNC NE->RNC Radio Resource
Path:
-> Waiting time length for A CTIVE SET UP DATE COMP LE TE Parameter Configuration
Configuration Description: The value is smaller, the probability of receiving the ACTIVE SE T UP DATE COMPLE TE may be decreases, and the probability of call drop may be increased. The value is bigger, the probability of receiving the ACTIVE SET UPDATE COMPLE TE may be increased, however, when the radio environment is bad, the RNC may wait too long time to unnec essary wait and increase the wait time to Re-establishment the service
4.13.2.3
WaitRbCompTimer OMC Path View-> Configuration Management-> RNC NE->RNC Radio Resource
Path:
-> Time of Waiting for RB Setup/ Reconfiguration/Release Response over Uu Interface Parameter Configuration
144
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 S etup/ Reconfiguration/ Release Response may be increased; however, when the radio environment is bad, the RNC may wait too long time to unnecessary wait and increas e the wait time to Re -establishment the servic e.
4.13.2.4
CsReestSwitch0 OMC Path View-> Configuration Management-> RNC NE->RNC Radio Resource
Path:
Management-> UtranCell->Advanced Parameter Manage->Utran Cell-> Cs ReestSwitch0 Parameter Configuration
Configuration Description: When RNC is in STAB LE 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.
4.13.2.5
Path:
Configuration Description: When RNC is in Handover procedure and receive CELL UP DATE from UE, and UE have CS service, if Call Re-esstabilishment is allowed, set the value is 1; if not allowed, set it 0.
145
4.13.2.6
Path:
Configuration Description: When RNC is in RAB setup procedure and receive CELL UP DATE from UE, and UE have CS service, if Call Re-esstabilishment is allowed, set the value is 1; if not allowed, set it 0.
4.13.2.7
Path:
Configuration Description: 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.
4.13.2.8
Path:
146
Configuration Description: When RNC is in Handover procedure and t he 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.
4.13.2.9
Path:
Configuration Description: 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 allowed, set the value is 1; if not allowed, set it 0.
4.13.2.10
PsReestSwitch0 OMC Path View-> Configuration Management-> RNC NE->RNC Radio Resource
Path:
Management-> UtranCell->Advanced Parameter Manage->Utran Cell-> PsReestSwitch0 Parameter Configuration
Configuration Description: 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; if not allowed, set it 0.
147
4.13.2.11
Path:
Configuration Description: When RNC is in Handover procedure and receive CELL UP DATE 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.
4.13.2.12
Path:
Configuration Description: When RNC is in RAB setup procedure and receive CELL UP DATE 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.
4.13.2.13
Path:
148
Configuration Description: 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.
4.13.2.14
Path:
Configuration Description: When RNC is in Handover procedure and t he 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.
4.13.2.15
Path:
Configuration Description: 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 allowed, set the value is 1; if not allowed, set it 0.
149
5
5.1
Counter and Alarm

Counter List
Table 5-1 Connection Management Counter Description
Counter No. C310080001 C310080002 C310080003 C310080004 C310080005 C310080006 C310080007 C310080008 C310080009 C310080010 C310080011 C310080012 C310080013 C310080014 C310080015 C310080016 C310080017 C310080018 C310080019 C310080020 C310080021 C310080022 C310080023 C310080024
Number of attempted RRC connection establishment,by cause
150
C310080025 C310080026 C310080027 C310080028 C310080029 C310080030 C310080031 C310080032 C310080033 C310080034 C310080035 C310080036 C310080037 C310080038 C310080039 C310080040 C310080041 C310080042 C310080043 C310080044 C310080045 C310080046 C310080047 C310080048 C310080049 C310080050 C310080051 C310080052 C310080053 C310080054 C310080055 C310080056 Number of attempted RRC connection establishment,by UE Capability Number of attempted RRC connection establishment,by Domain Number of attempted RRC connection establishment,by CallType
151
C310080057 C310080058 C310080059 C310080060 C310080061 C310080062 C310080063 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 Number of RRC connection preparation failure,by establishment cause Number of RRC connection preparation failure,by fail cause Number of attempted RRC connection establishment,by UE AS Release
152
C310080089 C310080090 C310080091 C310080092 C310080093 C310080094 C310080095 C310080096 C310080097 C310080098 C310080099 C310080100 C310080101 C310080102 C310080103 C310080104 C310080105 C310080106 C310080107 C310080108 C310080109 C310080110 C310080111 C310080112 C310080113 C310080114 C310080115 C310080116 C310080117 C310080118 C310080119 C310080120 Number of RRC connection preparation Number of RRC connection preparation Number of RRC connection preparation failure,by call type
failure,by domain Number of RRC connection Refus e for Conversational Call Number of RRC connection Refus e for Voice Number of RRC connection preparation
success,by Channel type
success,by Direct
153
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
154
C310080153 C310080154 C310080155 C310080156 C310080157 C310080158 C310080159 C310080160 C310080161 C310080162 C310080163 C310080164 C310080165 C310080166 C310080167 C310080168 C310080169 C310080170 C310080171 C310080172 C310080173 C310080174 C310080175 C310080176 C310080177 C310080178 C310080179 C310080180 C310080181 C310080182 C310080183 C310080184 Number of RRC access establishment cause Success,by Number of RRC access fail,by fail cause
155
C310080185 C310080186 C310080187 C310080188 C310080189 C310080190 C310080191 C310080192 C310080193 C310080194 C310080195 C310080196 C310080197 C310080198 C310080199 C310080200 C310080201 C310080202 C310080203 C310080204 C310080205 C310080206 C310080207 C310080208 C310080209 C310080210 C310080211 C310080212 C310080213 C310080214 C310080215 C310080216 Number of RRC access Success,by UE Phy Capability Category Number of RRC access Success,by RRC establish time Number of RRC access Success,by UE AS Release Number of RRC access domian Number of RRC access Success,by UE Capablity Success,by Number of RRC access Success,by call type
156
C310080217 C310080218 C310080219 C310080220 C310080221 C310080222 C310080223 C310080224 C310080225 C310080226 C310080227 C310080228 C310080229 C310080230 C310080231 C310080232 C310080233 C310080234 C310080235 C310080236 C310080237 C310080238 C310080239 C310080240 C310080241 C310080242 C310080243 C310080244 C310080245 C310080246 C310080247 C310080248 Number of failed RRC connection Number of failed RRC connection re-establishment Number of failed RRC connection re-establishment Number of attempted RRC connection re-establishment Number of Triggered RRC connection re-establishment
157
re-establishment,by traffic
RRC
Connection
Establishment
Procedures
RRC Connection Release Procedures
158
C310555151 C310555152 C310555153 C310555154 C310555155 C310555156 Cell Paging Procedures C310555157 C310555158 C310555159 C310555160 C310555161 C310555165 C310555166 C310555167 Cell Security Procedures C310555168 C310555169 C310555170 C310565185 C310565186 C310565187 C310565188 C310565189 C310565190 C310565191 C310565192 C310565193 C310565194 C310565195 C310565196 C310595406 C310595407 C310595408 Radio Link Setup Procedures Radio Bearer Reconfiguration Procedures Signaling Statistic
159
C310595409 C310595410 C310595411 C310595412 C310595413 C310595414 C310595415 C310595416 C310595417 C310595418 C310595419 C310595420
Counter No. C301861019 C301861020 C301861021 C301861022 C301861023 C301861024 C301861025 C301861026 C301861027 C301861028 C301861029 C301861030 C301861031 C301861032 C301861033 C301861034 C301861035
Description
Number of attempted RRC connection establishment
160
161
C310080053 C310080054 C310080056 C310080057 C310080058 C310080059 C310080060 C310080061 C310080062 C310080063 C310080064 C310080065 C310080066 C310080067 C310080068 C310080069 C310080070 C310080071 C310080072 C310220073 C310220074 C310220075 C310080076 C310080077 C310080078 C310080079 C310080080 C310080081 C310080082 C310080083 C310080084 C310080085 Number of success RRC connection preparation
162
163
164
C310080154 C310080155 C310080156 C310080157 C310080158 C310080159 C310080160 C310080161 C310080162 C310080163 C310080164 C310080165 C310080166 C310080167 C310080168 C310080169 C310080170 C310080171 C310080172 C310080173 C310080174 C310080175 C310080176 C310080177 Number of RRC access Success C310080178 C310080179 C310080180 C310080181 C310080182 C310080183 C310080184 C310080185 Number of RRC access fail
165
166
C310080222 C310080223 C310080224 C310080225 C310080226 C310080227 C310080228 C310080229 C310080230 C310080235 C310080236 C310080237 C310080238 C310080248 C310080249 C310080250 C310080226 C301861039 C301240926 C301240927 C301240928 C301240929 C301240930 C301240931 C301240932 C301240933 C301240934 C301240935 C301240936 C301240937 C301240938 Number of RRC connection release on CCCH,by cause Number of RRC connection release on DCCH,by cause Number of attempted RRC connection establishment for UE supported HS DPA Number of failed RRC connection Number of attempted RRC connection re-establishment Number of Triggered RRC connection re-establishment
re-establishment
167
C301240939 C301480445 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 C301480466 C301480467 C301480468 C301480469 C301480470 Number of successful RRC connection establishment,by cause( in a certain cell) Number of attempted RRC connection establishment,by cause( in a certain cell)
168
C301480471 C301480472 C301480473 C301480474 C301480475 C301480476 C301480477 C301480478 C301480479 C301480480 C301480481 C301480482 C301480483 C301480484 C301481553 C301481554 C301481405 C301481406 C301481498 C301480488 C301480489 C301480490 C301480491 C301481288 Total time of RRC connection Number of failed RRC connection re-establishment( in a certain cell) Number of attempted RRC connection re-establishment( in a certain cell)
establishment( in a certain cell) Max time of RRC connection
C301481289
establishment( in a certain cell) Number of RRC connection Release for abnormal Cause( in a certain cell) Number of RRC connection Refuse for Conversational Call( in a certain cell) Number of RRC connection Request for
C301481337 C301481338 C301481339 C301481340
169
HSDPA UE( in a certain cell) C301481407 C301481408 C301240940 C301480485 C301480486 C301480487 Number of failed RRC connection establishment,by cause Number of RRC connection Refuse for Voice( in a certain cell) Number complete of RRC connection release
5.2
Alarm List
This feat ure has no related alarm.
Glossary
D DRX DSAR F FD FP I IuUP M MIB N Master Information Block Iu Interface User Plane Feature Description Frame Protocol Discontinuous Reception Domain Specific Access Restriction
170
NAS Np O OMCR P PI PO R RAB RAT RL RRC S SB SIB T TFC
Non Access Stratum Number of P I
OMC of the RNC
Page Indicat or Page Occasion
Radio access bearer Radio Access Technology Radio Link Radio Resource Control
Schedule Block system information block
Transport Format Combination
Reference
ZTE UMTS Load Balance Feature Guide ZTE UMTS IU Flex Feature Guide
171

ZTE UMTS Connection Management Feature Guide V6!1!201204

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

ZTE UMTS Connection Management Feature Guide V6!1!201204

Загружено:

Авторское право:

Доступные форматы

Connection Feature Guide

Connection Management Feature Guide

Connection Management Feature Guide

2.1.1 System Information Broadcasting: add SIB19 3.1.2.10 SIB19: add

ZTE Confidential Proprietary

Connection Management Feature Guide

add description of switch 3.10.2 Call Re-establishment Triggered By

ZTE Confidential Proprietary

Connection Management Feature Guide

ZTE Confidential Proprietary

Connection Management Feature Guide

ZTE Confidential Proprietary

Connection Management Feature Guide

ZTE Confidential Proprietary

Connection Management Feature Guide

ZTE Confidential Proprietary

Connection Management Feature Guide

ZTE Confidential Proprietary

Connection Management Feature Guide

ZTE Confidential Proprietary

Connection Management Feature Guide

Connection Setup and Release

ZTE Confidential Proprietary

Connection Management Feature Guide

ZTE Confidential Proprietary

Connection Management Feature Guide

NAS Message Transfer

ZTE Confidential Proprietary

Connection Management Feature Guide

Ciphering Algorithm UEA0 and UEA1

ZTE Confidential Proprietary

Connection Management Feature Guide

Integrity Protection Algorithm UIA1

ZTE Confidential Proprietary

Connection Management Feature Guide

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

Radio Connection Monitor

Radio Connection Re-establishment

ZTE Confidential Proprietary

Connection Management Feature Guide

27.2Kbps High Speed Signaling RB

RRC Connection Redirect

ZTE Confidential Proprietary

Connection Management Feature Guide

Domain Specific Access Restriction (DSAR)

Ciphering Algorithm UEA2

ZTE Confidential Proprietary

Connection Management Feature Guide

in 3GPP TS 33. 102 TS 35.215~ 218 TS 35.919.

Integrity Protection Algorithm UIA2

ZTE Confidential Proprietary

Connection Management Feature Guide

Iu Interface Interruption Protection

ZTE Confidential Proprietary

Connection Management Feature Guide

ZTE Confidential Proprietary

Connection Management Feature Guide

System Information Broadcasting, Scheduling, and Transmission

System broadc asting

system information broadcast scheduler

Conditioninforming UE of idle, CELL_PCHURA_PCH that system information changed PagingPAGING TYPE1

Conditioninforming UE of CELL_FACH that system information changed