Feature Deployment and Testing Guide

TrFO
Feature ID: ZWF21-06-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-067

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

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

 Contents
Chapter 1 Functional Description ............................................................. 1-1
Chapter 2 Deployment in commercial network and user benefit........... 2-1
2.1 Benefits ............................................................................................................. 2-1
2.2 Deployment in commercial network ..................................................................... 2-1

Chapter 3 Preparations .............................................................................. 3-1

Chapter 4 Data configuration .................................................................... 4-1
Chapter 5 Testing ....................................................................................... 5-1
5.1 Test Purpose...................................................................................................... 5-1
5.2 Steps for Test..................................................................................................... 5-1
5.3 Expected Results ............................................................................................... 5-2

Chapter 6 Counter List............................................................................... 6-1

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

 II

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

 Chapter 1
Functional Description
At the R99 stage, voice at the CN CS employs 64kbit/s PCM encoding based on
TDM bearer. Therefore, the R99 MSC must have the voice TC function. But voice
encoding/decoding is apt to r educe voice quality. The calls between mobile users, in
particular, need dual voice encoding/decoding. If a codec is not used, voice quality will
be improved with network bandwidth saved.
At the R4 stage, voice encoding/decoding times can be reduced by establishing a TrFO
connection. The TrFO connection can be established throughout end-to-end process or
between some node of a call connection. For example, for a call between UMTS UE and a
fixed telephone, the TrFO connection only exists between UMTS UE and a core network.
The core network and RNC in the TrFO connection must support the IuUP V2. Otherwise,
no TrFO connection can be established. ZTE supports the IuUP V1 and IuUP V2. The
RNC will make a choice according to CN RAB assignment parameters.
The TrFO is implemented by employing the outband signaling encoding/decoding control
function (OoBTC). It is applicable to the calls between mobile networks and those between
a mobile network and an external network. When the same voice encoding/decoding
type is used between both call parties or between one call party and a node in the call
connection, the TrFO can transparently transmit compressed voice, which improves voice
quality and saves transmission bandwidth.
The node on both sides with a TrFO connection successfully established will use
completely the same common compressed voice encoding type negotiated at the OoBTC
stage. A codec must be inserted between a TrFO connection and a non-TrFO connection
to convert one encoding type into another. The implementation strategy of the core
network will, to the greatest extent, ensure that the insertion position can meet the
following requirements:

l The insertion position should reduce the use of a transcoder and improve voice quality;
l The insertion position should save transmission bandwidth, that is, it should prolong
the connection which uses compressed voice encoding data for transmission.

For a UTRAN, its IuUP initialization, reverse initialization, IuUP rate control, and IuUP
reverse rate control are related to the TrFO process.

1-1

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

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

This page intentionally left blank.

1-2

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

 Chapter 2
Deployment in commercial
network and user benefit
Table of Contents
Benefits ......................................................................................................................2-1
Deployment in commercial network ............................................................................2-1

2.1 Benefits
This feature can realize the transparent transfer of voice stream among mobile subscribers,
prevent voice quality from being reduced as a result of voice decoding for several times,
and save network transmission resource.

2.2 Deployment in commercial network

Switch on RNC
When UP Mode Versions in RAB ASSIGNMENT REQUEST is 1 from CN, RNC and CN
will negotiate to use Iu UP V1.
When UP Mode Versions in RAB ASSIGNMENT REQUEST is 2 from CN, RNC and CN
will negotiate to use Iu UP V2.
When UP Mode Versions in RAB ASSIGNMENT REQUEST is 3 from CN, RNC will
response CN with Iu UP V1 and indicate both Iu UP V1 and Iu UP V2 are supported in
initialization ack message. Which version will be choosed is controlled by CN.
When UP mode version in RAB ASSIGNMENT REQUEST is 3, RNC has 2 switches,
IntraRatUpVer and InterRatUpVer:
IntraRatUpVer
It works when service is set up in RNC or relocated from other RNC.
l Set to IuUP V1
Actual NB-AMR or WB-AMR rates that are implemented should be the intersection of
the rates assigned by CN and OMC configuration.
l Set to IuUP V2
Actual NB-AMR or WB-AMR rates that are implemented is the rates assigned by CN.
InterRatUpVer

2-1

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

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

It works when service is relocated from 2G.

l Set to IuUP V1
Actual NB-AMR or WB-AMR rates that are implemented should be the intersection of
the rates assigned by CN and OMC configuration.
l Set to IuUP V2
Actual NB-AMR or WB-AMR rates that are implemented is the rates assigned by CN.
If IntraRatUpVer set to IuUPV1, after relocation between RNCs, RNC and CN will
not negotiate the AMR rates again and Trfo will not be applied. So its recommended
IntraRatUpVerset to IuUPV2.
For speech service, there is some restriction on AMR rate after relocation from 2G to 3G.
Only the following combinations of rate are acceptable.
12.2 kbps speech +3.4 kbps signalling

12.2/7.95/5.9/4.75 kbps speech + 3.4 kbps signalling

7.95 kbps speech + 3.4 kbps signalling
12.65/8.85/6.6 kbps speech + 3.4 kbps signalling
If the AMR rate is not the combination above, speech call will drop after relocation from
2G to 3G. So its recommended InterRatUpVer set to IuUPV1.

Criteria for end to end Trfo

1. Caller and callee in same CN and in same RNC or different RNC
l RNC supports Iuup V2, CN supports IuupV2.
l CN and RNC supports UMTS codec (UMTS-AMR2, UMTS-AMR or WAMR)
2. Caller and callee in different CN and RNC
l RNC supports Iuup V2, CN supports IuupV2.
l CN and RNC supports UMTS codec (UMTS-AMR2, UMTS-AMR or WAMR)
l BICC must be used between CN. The bearer between CN must be IP not TDM.
3. Caller in CN1/RNC1 and callee in CN2/BSC, or Caller in CN2/BSC and callee in
CN1/RNC1
l RNC supports Iuup V2, CN supports IuupV2.
l BICC must be used between CN. The bearer between CN must be IP not TDM
l The bearer of A interface between CN and BSC must be IP not TDM.
l CN and RNC supports UMTS codec (UMTS-AMR2, UMTS-AMR or WAMR)
l CN and BSC supports GSM-AMR codec (FR-AMR, HR-AMR or WAMR)
l Terminals in 2G must support GSM-AMR codec (FR-AMR, HR-AMR or WAMR)

2-2

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

 Chapter 3
Preparations
License
N/A

Hardware Requirement
Hardware requirement is shown in Table 3-1.

Table 3-1 Hardware Requirement

NE Requirement

RNC None

NodeB None

Software Requirement
Software requirement is shown in Table 3-2.

Table 3-2 Software Requirement

NE Involved Version Requirement

UE YES UMTS FDD Number: 2

Category: Any
Release : R99 or above

NodeB YES V4.11.10.14

RNC YES V3.11.10.11

MSCS YES ZTE equipment

MGW YES ZTE equipment

SGSN YES ZTE equipment

GGSN NO

HLR NO

Topology
Topology is shown in Figure 3-1.

3-1

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

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

Figure 3-1 Topology

3-2

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

 Chapter 4
Data configuration
SGSN/GGSN - ZTE
N/A

MSC/MGW - ZTE
CN support TrFO.

TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.userPlaneInformation.uP_ModeVersions.numbits = 16
TRANAP_Message.RAB_AssignmentRequestMsg.rAB_SetupOrModifyList.elem[0].rAB_
SetupOrModifyItemFirst.userPlaneInformation.uP_ModeVersions.data = 00 02

HLR ZTE
N/A

RNC
l Intra-RAT IuUP VersionVersion 2 Prefer

PathView > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > Modify Advanced Parameter > RNC Radio Resource
Management > Intra-RAT IuUP Version Selection

l Inter-RAT IuUP VersionVersion1 Prefer

4-1

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

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

PathView > Configuration Management > RNC Managed Element > RNC Radio
Resource Management > Modify Advanced Parameter > RNC Radio Resource
Management > Inter-RAT IuUP Version Selection.

NodeB
N/A

4-2

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

 Chapter 5
Testing
Table of Contents
Test Purpose ..............................................................................................................5-1
Steps for Test .............................................................................................................5-1
Expected Results .......................................................................................................5-2

5.1 Test Purpose

The purpose of this test case is to verify the function of TrFO is working normal.
Related documents:

l ZTE UMTS AMR-NB & AMR-WB Feature Guide.doc

5.2 Steps for Test

1. UE1 makes a voice call to UE2. Uplink and downlink radio signal quality is good
enough for no error data. Meanwhile open the QXDM and captures the Uu log of UE1
and UE2

2. Maintain the call for 3 minutes. Keep Capturing the Uu log of UE1 and UE2.
3. Release the voice call.

5-1

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

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

5.3 Expected Results

The same data can be found from the Uu log of UE1 and UE2. That means the data which
UE1 has sent is transferred transparently to UE2 without being re-coded by CN.

Open the two Uu logs of UE1 and UE2 using QCAT. Compare the data of UMTS
DL(Rx/Tx) Vocoder Packet Characteristics v2 from UE1 with UMTS DL(Tx/Rx) Vocoder
Packet Characteristics v2 from UE2,we will find that the data are totally the same.

5-2

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

 Chapter 6
Counter List
Number of attempted RRC connection establishment, Originating
C310080001 Conversational Call

Number of attempted RRC connection establishment, Terminating

C310080008 Conversational Call

C310080170 Number of successful RRC connection access, MO Conversational Call

C310080177 Number of successful RRC connection access, MT Conversational Call

C310090254 Number of attempted RAB assignment setup in cell for CS domain, AMR 12.2K

6-1

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