ZWF21!03!014 Enhanced Iur-G

Feature Deployment and Testing Guide
Enhanced Iur-g
Feature ID: ZWF21-03-014
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-040
Publishing Date: 2012-08-09 (R1.0)
SJ-20120802112720-040|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-6
Chapter 5 Counter List............................................................................... 5-1

II

Chapter 1
Functional Description
The feature supports the enhaced Iur-g interface between GERAN BSC and 3G RNC. It
enables RNC to get capability and load of 2G cell. By employing the interface, inter-RAT
load balance can be achieved, inter-RAT handover success ratio is improved and handover
delay is decreased.
Figure 1-1 IUR-G Protocol Stack
Note:
1. The protocol stack of IUR-G interface is the same with IUR interface.
2. There is no user plane of IUR-G interface.
1-1

Feature Deployment and Testing Guide Feature ID: ZWF21-03-014
Figure 1-2 3G to 2G CS service handover procedure via IUR-G
1-2

Chapter 2
Preparations
License
This Feature is controlled by license, the license parameters is:
rncIurgOff.BscFeatSwitch0
Hardware Requirement
NE Requirement
RNC None
NodeB None
BSC None
Software Requirement
NE Involved Version Requirement
UE YES UMTS FDD Number: 2

Category: None
Release: R99
Node B YES V4.11.10.14 None
RNC YES V3.11.10.11 ZTE equipment
BSC YES ZTE equipment
MSCS YES ZTE equipment
MGW YES ZTE equipment
SGSN YES ZTE equipment
GGSN NO
HLR NO
2-1

Topology
Topology is shown in Figure 2-1.
Figure 2-1 Topology
2-2

Chapter 3
Data Configuration
SGSN/GGSN - ZTE
N/A
MSC/MGW - ZTE
N/A
HLR - ZTE
N/A
GSM
Open the IUR-G switch and config all the negotiated data with RNC side.
RNC
Add interface IP, it is the IP address of IP layer in protocol stack.
Path: View > Configuration Management > RNC Managed Element > RNC Ground
Resource Management > Transmission Configuration > IP Protocol Configuration >
Interface Configuration > Local Port No
Parameter Configuration: This parameter indicates the port which connects to BSC by the
cable.
Interface Configuration > IP address
Parameter Configuration: This parameter indicates the interface IP which is used to
connect to BSC.
3-1

3-2

Chapter 3 Data Configuration
ADD RPU IP, it is the IP address of SCTP layer in protocol stack.

Interface Configuration > IP address
Parameter Configuration: This parameter indicates the SCTP IP on RNC side, and is used
to connect to BSC.
3-3

Add BSC NE Information in RNC side. Notice that MNC,MCC,NetElementID should be

the same with BSC side.
Path: View > Configuration Management > RNC Managed Element > RNC
Ground Resource Management > Transmission Configuration > Network Element
Information > BSC xxx > Iurg Office > Basic Configuration
Parameter Configuration: These parameters indicate the PLMN of BSC, and the NE ID
configured on RNC.
Information > BSC xxx > Iurg Office > Iurg Office2
Parameter Configuration: This parameter indicates whether the Iurg interface is ON of

OFF.
3-4

3-5

Add Signalling Point, it should be negotiated with BSC side.

Information > BSC xxx > Adjacent Office Signalling Point Configuration
Parameter Configuration: These parameters indicates the signalling point of BSC.
3-6

Add subsystem, the Subsystem of IUR-G interface is the same with IUR interface, it is
RANSAP.
Information > BSC xxx > Office system No
Parameter Configuration: These parameters indicates the office system No ,which is uesd
by RNC and BSC.
No1 is used for SCCP protocol;
No142 is used for RANAP protocol.

No143 is used for RNSAP protocol.
3-7

3-8

Add SCTP link

Resource Management > Sigtran Configuration > SCTP Association Configuration
Parameter Configuration
Parameter Name Parameter Description
SCTP association ID this parameter is a mark used only by RNC.
Moudle No this parameter indicates the CMP moudle No

used by SCTP link.
Protocol type of SCTP association this parameter indicates the protocol type used
between RNC and BSC.
Peer-end Office No. of SCTP association this parameter is the BSC No. which configs in
the NE info .
Application property of SCTP association this parameter is Application property of SCTP

association on RNC side .
Local-end port No. this parameter is the SCTP port on RNC.
Peer-end port No. this parameter is the SCTP port on BSC.
Local-end IP address this parameter is the SCTP IP on RNC ,and is

configed on RPU.
Peer-end IP address this parameter is the SCTP IP on BSC.
3-9

Add ASP Configuration
Path: View > Configuration Management > RNC Managed NE > RNC Ground
Resource Management > Sigtran Configuration > ASP Configuration Information
3-10

Parameter Configuration: This parameter is a mark of ASP, which is used by RNC only.
Add AS information
Resource Management > Sigtran Configuration > AS Static Information
Parameter Configuration:
AS ID this parameter is a mark used only by RNC
whether routing context exists or not this parameter indicates the routing context state
on RNC.
3-11

APP server AS usage ID this parameter indicates the type of AS used by

RNC
Traffic mode Type this parameter indicates the transmiss type of AS

on RNC.
ASP ID this parameter is the ASP ID which configs in

ASP information
3-12

Add static route information of M3UA
3-13

Resource Management > SIgtran Configuration > Static Route Information of M3UA
Parameter Configuration
Route ID this parameter is a mark used only by RNC
AS ID this parameter is the AS ID which configs in AS

static information
Add route info of M3UA multi-RK
3-14

Resource Management > Sigtran Configuration > Static Route Information of M3UA
Parameter Configuration:
DPC this parameter is the signalling point of BSC.
Primary Route ID this parameter is the route ID which configs in

Static Route Information of M3UA.
Add external GSM cell
3-15

Add GSM neighboring cell
Open the switch of IUR-G interface
Information > BSC xxx > Iurg Office > Iurg Office2
Parameter Configuration: This parameter indicates whether the Iurg interface is ON or

OFF.
3-16

Node B
N/A
3-17

This page intentionally left blank.
3-18

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

The purpose of this test case is to verify if the enhanced iur-g is working normally.
Related document:
ZTE UMTS Handover Control Feature Guide
4.2 Steps for Test

1. UE works on dual model, and starts a CS call. The call establishes successful.
a. Rab assignment response
b. Measurement control for 2D/2F
4-1

2. Moves UE from RNC cell1 to GSM cell2. Handover will be happened, and messages
will be sent / received on IUR-G interface .
a. Measurement report for 2D.
b. Measurement control for 3A and active the compressed mode.
4-2

Chapter 4 Testing
c. Active the compressed mode to NodeB.
4-3

d. Measurement report for 3A.
e. EnhancedRelocationResourceRequest is sended on the IUR-G interface.
4-4

Chapter 4 Testing
f. EnhancedRelocationResourceResponse is received on the IUR-G interface.
g. Relocation to 2G happens.
4-5

4.3 Expected Results

Due to enhanced IUR-G function:
Open the switch of IUR-G interface,messages will be sended/received on the IUR-G
interface.
4-6

Chapter 5
Counter List
There is no any counter related to this feature.
5-1

ZWF21!03!014 Enhanced Iur-G

Загружено:

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

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

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

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

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

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

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

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

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

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

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

ZWF21!03!014 Enhanced Iur-G

Загружено:

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

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

Feature Deployment and Testing Guide

Revision No. Revision Date Revision Reason

R1.0 2012-08-09 First edition

Serial Number: SJ-20120802112720-040

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

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

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

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

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

Figure 1-1 IUR-G Protocol Stack

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

Figure 1-2 3G to 2G CS service handover procedure via IUR-G

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

NE Involved Version Requirement

UE YES UMTS FDD Number: 2

Node B YES V4.11.10.14 None

RNC YES V3.11.10.11 ZTE equipment

BSC YES ZTE equipment

MSCS YES ZTE equipment

MGW YES ZTE equipment

SGSN YES ZTE equipment

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

Figure 2-1 Topology

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

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

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

ADD RPU IP, it is the IP address of SCTP layer in protocol stack.

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

Add BSC NE Information in RNC side. Notice that MNC,MCC,NetElementID should be

Parameter Configuration: This parameter indicates whether the Iurg interface is ON of

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

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

Add Signalling Point, it should be negotiated with BSC side.

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

No142 is used for RANAP protocol.

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

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

Add SCTP link

Parameter Name Parameter Description

SCTP association ID this parameter is a mark used only by RNC.

Moudle No this parameter indicates the CMP moudle No

Application property of SCTP association this parameter is Application property of SCTP

Local-end port No. this parameter is the SCTP port on RNC.

Peer-end port No. this parameter is the SCTP port on BSC.

Local-end IP address this parameter is the SCTP IP on RNC ,and is

Peer-end IP address this parameter is the SCTP IP on BSC.

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

Add ASP Configuration

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

Parameter Name Parameter Description

AS ID this parameter is a mark used only by RNC

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

Parameter Name Parameter Description

APP server AS usage ID this parameter indicates the type of AS used by

Traffic mode Type this parameter indicates the transmiss type of AS

ASP ID this parameter is the ASP ID which configs in

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

Add static route information of M3UA

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

Parameter Name Parameter Description

Route ID this parameter is a mark used only by RNC

AS ID this parameter is the AS ID which configs in AS

Add route info of M3UA multi-RK