Feature Deployment and Testing Guide

Connection Setup and Release

Feature ID: ZWF21-01-002

Version: V3.11.10

ZTE CORPORATION
NO. 55, Hi-tech Road South, ShenZhen, P.R.China
Postcode: 518057
Tel: +86-755-26771900
Fax: +86-755-26770801
URL: http://ensupport.zte.com.cn
E-mail: support@zte.com.cn
LEGAL INFORMATION
Copyright © 2012 ZTE CORPORATION.
The contents of this document are protected by copyright laws and international treaties. Any reproduction or
distribution of this document or any portion of this document, in any form by any means, without the prior written
consent of ZTE CORPORATION is prohibited. Additionally, the contents of this document are protected by
contractual confidentiality obligations.
All company, brand and product names are trade or service marks, or registered trade or service marks, of ZTE
CORPORATION or of their respective owners.
This document is provided “as is”, and all express, implied, or statutory warranties, representations or conditions
are disclaimed, including without limitation any implied warranty of merchantability, fitness for a particular purpose,
title or non-infringement. ZTE CORPORATION and its licensors shall not be liable for damages resulting from the
use of or reliance on the information contained herein.
ZTE CORPORATION or its licensors may have current or pending intellectual property rights or applications
covering the subject matter of this document. Except as expressly provided in any written license between ZTE
CORPORATION and its licensee, the user of this document shall not acquire any license to the subject matter
herein.
ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice.
Users may visit ZTE technical support website http://ensupport.zte.com.cn to inquire related information.
The ultimate right to interpret this product resides in ZTE CORPORATION.

Revision History

Revision No. Revision Date Revision Reason

R1.0 2012-08-09 First edition

Serial Number: SJ-20120802112720-003

Publishing Date: 2012-08-09 (R1.0)

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Contents
Chapter 1 Functional Description ............................................................. 1-1
Chapter 2 Preparations .............................................................................. 2-1
Chapter 3 Data Configuration.................................................................... 3-1
Chapter 4 Testing ....................................................................................... 4-1
4.1 Test Purpose...................................................................................................... 4-1
4.2 Steps for Test..................................................................................................... 4-1
4.3 Expected Results ............................................................................................... 4-3

Chapter 5 Counter List............................................................................... 5-1

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 II

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 1
Functional Description
The RRC connection can be established over:
l A dedicated channel
l A common channel
The RRC connection establishment flow is shown in Figure 1-1.

1-1

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-002

Figure 1-1 RRC Connection Establishment Flow

l Establishing an RRC Connection over a Dedicated Transport channel

When receiving the RRC CONNECTION REQUEST message from a UE, the RNC
specifies the channel over which the RRC connection is to be established according
to the parameter InitRrcOnDch (Type of Transport Channel for Initial RRC Connection
Setup) in the OMCR.
If the parameter InitRrcOnDch is set to 0 (Forced to DCH and Using Normal Speed
Signaling) or 1 (Forced to DCH and Using 13.6Kbps signaling), or 5 (Forced to
DCH and using 27.2Kbps), the RNC establishes the RRC connection over the DCH
channel.

1-2

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 1 Functional Description

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

Cell-DCH State) or 4 (Not Forced, Using 13.6kbps Signaling on Cell-DCH State),
or 6(Not Forced, Using 27.2Kbps Signaling on Cell-DCH State), the RNC selects to
establish the RRC connection over the DCH according to the Establishment_cause
(for example, the UE initiates a call) in the RRC CONNECTION REQUEST message.
The RNC obtains the cell where the radio link is to be set up using the inter-frequency
load balance algorithm. For details on the inter-frequency load balance algorithm,
refer to ZTE UMTS Load Balance Feature Description.
The RNC establishes a radio link at the Iub interface.
After the radio link is established successfully, the RNC sends the RRC
CONNECTION SETUP message to the UE.
If the parameter InitRrcOnDch is set to a value that indicates using high speed
signaling, the RNC fills in 13.6k high speed SRB for the parameter Dynamic Transport
Format Information in the RRC CONNECTION SETUP message. Otherwise, the
RNC fills in 3.4k common SRB. If the 13.6K SRB has been established, the RNC fills
in 3.4K SRB when RAB assignment starts.
RNC will retransmit RRC CONNECTION SETUP message once again if RNC
haven’t received RRC CONNECTION SETUP COMPLETE message from UE after
0.7 seconds.
The RNC receives the RRC CONNECTION SETUP COMPLETE message from the
UE, indicating that the RRC connection is established successfully. The process ends.

l Establishing an RRC Connection over a Common Transport channel

When receiving the RRC CONNECTION REQUEST message from a UE, the RNC
specifies the channel over which the RRC connection is to be established according
to the parameter InitRrcOnDch in the OMCR.
If the parameter InitRrcOnDch is set to 2 (Forced to FACH), the RNC establishes the
RRC connection over the FACH channel.
If the parameter InitRrcOnDch is set to 3 , 4, or 6, the RNC establishes the
RRC connection according to the Establishment_cause: if services are initiated
immediately after the setup of RRC connection (for example, the value of
Establishment cause is Originating Conversational Call), RNC will select DCH
channel; if there is only a signaling process, instead of setting up services, that
should be completed after RRC connection (for example, the value of Establishment
cause is registration ), RNC will select common channel to bear signaling.
The RNC selects the SCCPCH channel according to the Initial UE Identify of
the UE. Index of selected SCCPCH = Initial UE Identity” mod K. K represents
the number of FACH SCCPCH channels of the cell. The RNC sends the RRC
CONNECTION SETUP message over the SCCPCH channel to the UE and sends
the SRB configuration.

1-3

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-002

RNC will retransmit RRC CONNECTION SETUP message once again if RNC
haven’t received RRC CONNECTION SETUP COMPLETE message from UE after
0.7 seconds.
The RNC receives the RRC CONNECTION SETUP COMPLETE message from the
UE, indicating that the RRC connection is established successfully. The process ends.

1-4

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 2
Preparations
License
N/A

Hardware Requirement
NE Requirement

RNC √

NodeB √

Software Requirement
NE Involved Version Requirement

UE YES UMTS FDD Number: 1

Category: Any
Release: R5

NodeB YES V4.11.10.14

RNC YES V3.11.10.11

MSCS NO ZTE equipment

MGW NO ZTE equipment

SGSN YES ZTE equipment

GGSN YES

HLR NO

Topology
Topology is shown in Figure 2-1.

2-1

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-002

Figure 2-1 Topology

2-2

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 3
Data Configuration
SGSN/GGSN - ZTE
N/A

MSC/MGW - ZTE
N/A

HLR - ZTE
N/A

RNC
Parameters setting in RNC

Figure 3-1 Type of Transport Channel for Initial RRC Connection: Forced to CELL_FACH

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > RNC Configuration > Type of Transport Channel for initial
RRC Connection

Figure 3-2 Cell Ability and Cell Reselection: Support HSUPA, HSDPA and DCH

Path: View > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > UTRAN Cell > UTRAN Cell xx > Cell Ability and Cell
Reselection

3-1

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-002

NodeB
N/A

3-2

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 4
Testing
Table of Contents
Test Purpose ..............................................................................................................4-1
Steps for Test .............................................................................................................4-1
Expected Results .......................................................................................................4-3

4.1 Test Purpose

The purpose of this test case is to verify if the procedure of RRC Setup on Common
Channels is normal.
Related documents:
ZTE UMTS Connection Management Feature Guide.doc

4.2 Steps for Test

1. UE1 dials-up in cell1. RrcConnection is set up successfully on FACH. For common
channels, radio link setup and deletion are not needed. As the PS service has
not been activated, we can see the rrcConnection establishment cause from the
“rrcConnectionRequest” message. This establishment cause may be different among
different UEs.

Then rrcConnection is successfully set up on FACH.

2. After RRC procedure, authentication and security mode procedure are done. UE1
sends active PDP context request to RNC.

4-1

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-002

Service RAB is established. We can see from “RAB_AssignmentRequestMsg” that

trafficClass is background and the MBR is 2048kbps.

3. The “RadioLink SetupRequest FDDMsg” after “RAB_AssignmentRequestMsg”

indicates that the traffic is set up on DCH/HSDSCH.

UE1’s active PDP context request is accepted, this signaling message also shows that
the UE capability is R5.

UE1 starts FTP downloading. The “RadioBearerSetup” message shows that the radio
bearer and UL/DL transport channel are set up on DCH.

4. UE1 stops FTP downloading. Then deactivating the PS service. The PDP is
deactivated.

IuRelease cause is normal_release. Then both the rrcConnection and radio resource
are released.

4-2

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 4 Testing

4.3 Expected Results

The signaling is established on the RACH/FACH channel in the RRC connection setup
stage. Then the PS service is expected to be established on DCH/HSDSCH successfully.
While deactivating the PDP, all radio resources are released normally.

4-3

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

Feature Deployment and Testing Guide Feature ID: ZWF21-01-002

This page intentionally left blank.

4-4

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential

 Chapter 5
Counter List
Counter No. Description

C310170870 Number of Successful HSDPA RAB establishment

for PS domain, Background Class

C310170872 Number of Successful HSDPA RAB establishment

for PS domain, Background Class, UE hsdpa
category 7-8

C310210953 Total RAB PS connection set-up time

C310210960 Total PS HSDPA RAB connection set-up time

C310251478 Number Of RAB normal release for UTRAN for

HSDPA:UE HSDPA categories 7 - 8, background

C310312120 RAB release number for Iu connection release

request by UTRAN for PS domain in cell, Ue
Request

5-1

SJ-20120802112720-003|2012-08-09 (R1.0) ZTE Proprietary and Confidential