zte umts amr-nb & amr-wb feature guide_v8.5_201312.pdf

AMR-NB&AMR-WB Feature

Guide

WCDMA RAN

AMR-NB&AMR-WB Feature Guide

ZTE Confidential Proprietary 1


Version Date Author Reviewer Revision History

V7.0 2012-5-11 Huang He Lu Li Modified the name and path of the

parameters.

V8.0 2012-11-23 Huang He Xia Lei

Added the new feature of Initial AMR Rate

Selection Based on Coverage and AMR Rate

Control after Relocation

V8.5 2013-11-26 Huang He

Cai Yaofang Xia Lei Added feature ID and check parameters

2014 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 Feature Attributes ............................................................................................. 5

2 Overview ............................................................................................................ 5

2.1 ZWF21-02-001 CS Conversational RAB for AMR-NB Speech ............................. 8

2.2 ZWF21-02-020 WB-AMR Speech Support ........................................................... 8

2.3 ZWF21-04-005 AMR Rate Controlling.................................................................. 8

2.4 ZWF21-04-014 Adaptive Radio Bearer Control .................................................... 9

2.5 ZWF21-06-002 TrFO ......................................................................................... 10

3 Technical Descriptions ................................................................................... 11

3.1 Signaling Flow of the AMR Service .................................................................... 11

3.2 Conversational RAB for AMR-NB ....................................................................... 14

3.2.1 AMR-NB Rates Selection ................................................................................... 14

3.2.2 Combination of AMR-NB Service and PS Service .............................................. 15

3.2.3 AMR-NB Mobility ............................................................................................... 15

3.2.4 Directed Retry of the AMR-NB Service In the Process of RAB Assignment ....... 16

3.2.5 Default Configuration of AMR-NB rates: 12.2k, 12.2/7.95/5.9/4.75k and

7.95kbps ............................................................................................................ 16

3.2.6 RAB Modification of the AMR-NB ....................................................................... 16

3.3 AMR-WB Speech Support ................................................................................. 16

3.3.1 AMR-WB Rates Selection .................................................................................. 16

3.3.2 Combination of AMR-WB Service and PS Service ............................................. 18

3.3.3 AMR-WB Mobility ............................................................................................... 18

3.3.4 Directed Retry of the AMR-WB Service In the Process of RAB Assignment ...... 18

3.3.5 RAB Modification of the AMR-WB ...................................................................... 18

3.4 AMR Dynamic Rate Controlling.......................................................................... 18

3.4.1 Classification of AMR Dynamic Rate Adjustment ............................................... 18

3.4.2 AMR Dynamic Rate Adjustment Based on Transmitted Power at Link Level...... 20

3.4.3 Dynamic Adjustment Triggered by Load ............................................................ 25

3.4.4 Dynamic Adjustment Triggered by Resource Congestion .................................. 25

3.5 AMR Adaptive Radio Bearer Control .................................................................. 25

3.5.1 AMR-NB Adaptive Radio Bearer Control ............................................................ 27

3.5.2 AMR-WB Adaptive Radio Bearer Control ........................................................... 28

3.5.3 AMR Rate Control after Relocation .................................................................... 28

3.6 TrFO Support ..................................................................................................... 29

3.6.1 OoBTC Outband Codec Control......................................................................... 30

3.6.2 Iu UP Initialization .............................................................................................. 31

3.6.3 Iu UP Rate Control ............................................................................................. 32



4 Parameters and Configurations ..................................................................... 34

4.1 Parameters of AMR-NB Service ......................................................................... 34

4.1.1 Parameter List ................................................................................................... 34

4.1.2 Parameter Configurations .................................................................................. 34

4.2 Parameters of WB-AMR Service ........................................................................ 38

4.2.1 Parameter List ................................................................................................... 38


4.3 Parameters of Uplink AMR Dynamic Rate Adjustment Based on UE Transmitted

Power ................................................................................................................ 42

4.3.1 Parameter List ................................................................................................... 42


4.4 Parameters of Downlink AMR Dynamic Rate Adjustment Based on D-TCP ....... 46

4.4.1 Parameter List ................................................................................................... 46


4.5 Parameters of AMR Dynamic Rate Adjustment Based on Load/Resource

Congestion ........................................................................................................ 52

4.5.1 Parameter List ................................................................................................... 52


4.6 Parameters of AMR Adaptive Radio Bearer Control ........................................... 52

4.6.1 Parameter List ................................................................................................... 52


5 Counter and Alarm .......................................................................................... 57

5.1 Counter List ....................................................................................................... 57

5.2 Alarm List ........................................................................................................... 64

6 Glossary ........................................................................................................... 64



FIGURES

Figure 3-1 Signaling Flow of AMR Service .........................................................................11

Figure 3-2 Flow of OoBTC Out-band Codec Control ..........................................................31

Figure 3-3 Iu UP Initialization .............................................................................................32

Figure 3-4 Flow of Iu UP Rate Control ...............................................................................33

TABLES

Table 2-1 AMR-NB Rate Classification ............................................................................... 6

Table 2-2 AMR-WB Rate Classification .............................................................................. 7



1 Feature Attributes

System version: [RNC V3.12.10/V4.12.10, OMMR V12.12.41, Node B V4.12.10, OMMB

V12.12.40]

Attribute: [Optional]

Involved NEs:

UE Node B RNC MSCS MGW SGSN GGSN HLR

- - -

Note:

*-: Not involved

*: Involved

Dependency: [None]

Mutual exclusion: [None]

Note: [None]

2 Overview

AMR (Adaptive Multi-Rate) codec provides a high quality of voice service with flexible

multi-rate to reach a tradeoff between voice quality and system capability (network load).

The present 3GPP employs Adaptive Multi-Rate Narrowband (AMR-NB) and Adaptive

Multi-Rate Narrowband (AMR-WB). For the AMR-NB, the speech channel bandwidth is

limited to 3.7 kHz, and the sampling frequency is 8,000 Hz. For the AMR-WB, the speech

channel bandwidth is up to 7 kHz, and the sampling frequency is up to 16,000 Hz. The

AMR-WB has better speech quality than that of the AMR-NB for the high sampling rate,

although the two modes have the same frame length of 20ms. The use of AMR-WB

needs UE to support this attribute which will be indicated in the SETUP uplink direct

transfer message from UE.



By means of the AMR Control (AMRC), voice rate can be reduced to improve voice

quality. In addition, system load can be effectively lightened. The scenarios that can

apply AMRC are as follows:

The load in downlink exceeds a certain threshold.

The load in uplink exceeds a certain threshold.

When uplink coverage is limited, AMR can be reduced to effectively widen uplink

coverage.

The AMRC can increase the AMR rate when the load is light. In this way, QoS is greatly

improved.

AMR-NB service has three service RBs, and can provide eight speech rates and several

Silence Descriptors (Comfort Noise Frame). The AMR-NB codec modes related to

UMTS_AMR are shown in the table:

Table 2-1 AMR-NB Rate Classification

AMR

Codec Mode

Total Number

of Bits

Sub-flow 1 Sub-flow 2 Sub-flow 3

AMR 4.75 kbps 95 42 53 0

AMR 5.15 kbps 103 49 54 0

AMR 5.9 kbps 118 55 63 0

AMR 6.7 kbps

(PDC EFR) 134 58 76 0

AMR 7.4 kbps

(TDMA EFR) 148 61 87 0

AMR 7.95 kbps 159 75 84 0

AMR 10.2 kbps 204 65 99 40

AMR 12.2 kbps

(GSM EFR) 244 81 103 60

AMR SID

(Comfort Noise

Frame)

39 39 0 0



AMR-NB voice coding is divided into three sub-flows in consideration of the importance

of information and error tolerance in voice coding. Each sub-flow requires its own QoS

assurance. Sub-flow 1 is the most important. Sub-flow 2 comes next. Sub-flow 3 is the

least important. Sub-flow 1 needs better channel coding at the air interface to guarantee

its accuracy. No data rate is coded in the case of mute. SID is used to indicate that voice

is not activated currently.

AMR-WB service was introduced in 1999 in order to provide better speech quality and

speech reproducibility. It can be applied to both 3G system and GSM system.

Unlike AMR-NB, the AMR-WB has only two service RBs and provides nine speech rates

and one Silence Descriptor, as shown in the table:

Table 2-2 AMR-WB Rate Classification

AMR-WB Codec

Mode

Total Number

of Bits Sub-flow 1 Sub-flow 2 Sub-flow 3

AMR-WB_6.60 132 54 78 0

AMR-WB_8.85 177 64 113 0

AMR-WB_12.65 253 72 181 0

AMR-WB_14.25 285 72 213 0

AMR-WB_15.85 317 72 245 0

AMR-WB_18.25 365 72 293 0

AMR-WB_19.85 397 72 325 0

AMR-WB_23.05 461 72 389 0

AMR-WB_23.85 477 72 405 0

AMR-WB_SID 40 40(including

35 comfort

noise bits)

0 0

Like the AMR-NB, the AMR-WB sub-flow 1 contains the most important information of

speech, with 12-bit CRC protection added on the air interface. The sub-flow 2 contains

less important speech information, without CRC protection on the air interface.



2.1 ZWF21-02-001 CS Conversational RAB for AMR-NB

Speech

ZTE equipment supports all the eight AMR-NBs: 12.2kbps, 10.2kbps, 7.95kbps, 7.4kbps,

6.7kbps, 5.9kbps, 5.15kbps, and 4.75kbps. ZTE equipment also supports DTX and SID.

The RAB parameters of ZTE RAN equipment, used to bear session AMR services, follow

the definitions in the 3GPP TS 34.108.

2.2 ZWF21-02-020 WB-AMR Speech Support

ZTE RAN equipment supports all the nine speech rates of AMR-WB session defined in

the 3GPP 26.201. They are, 23.85kbps, 23.05kbps, 19.85kbps, 18.25kbps, 15.85kbps,

14.25kbps, 12.65kbps, 8.85kbps, and 6.6kbps, together with the AMR-WB SID 1.75 kbps.

ZTE RNC enables and disables the function of WAMR by the parameter wAmrSupInd.

ZTE RNC does not support the RAB negotiation between AMR-NB and AMR-WB. If the

AMR-WB cannot be established, RNC does not initiate the RAB modification process to

establish the AMR-NB.

The RAB parameters of ZTE RAN equipment used to bear session AMR-WB services

follow the definition in the 3GPP TS 34.108.

2.3 ZWF21-04-005 AMR Rate Controlling

In WCDMA system, the radio environment always changes. When a UE is far away from

the base station or the radio environment degrades, the base station or UE is bound to

transmit with greater power under the action of closed-loop power control in order to

guarantee the QoS of AMR service. The power change and power increase at this time

may result in sharp increase in power and further deterioration of the radio environment.

As a result, the system capacity decreases, and even when the power is increased to a

certain limit value, the QoS requirements of service cannot be satisfied.



ZTE RNC equipment can monitor the uplink transmitted power from the UE internal

measurement report or the downlink transmitted power from the Node B dedicated

measurement report. When the uplink or downlink transmitted power rises to a certain

threshold, the RNC will automatically adjust this user's AMR rate to reduce the power

need for service. That is, a conversation is most probably kept going by reducing voice

quality. When the radio environment between UE and the base station is good and the

transmitted power of the base station or UE decreases to a certain threshold, AMR can

be increased to provide users with better voice quality as long as the system is neither

overloaded nor congested.

In addition, when a cell evaluated by means of downlink transmitted power and uplink

interference has high load of downlink or uplink, ZTE RNC equipment can lighten the cell

load by reducing the AMR rate of some low-priority users, so as to accommodate more

users.

The actual AMR rate which can be adjusted by the RNC must belong to the AMR code

set configured for users by the CN during call establishment. The voice quality when

low-rate AMR coding is used is not as good as that when high-rate AMR coding is used,

but low-rate AMR coding has higher capacity (number of users) and wider coverage than

high-rate AMR coding. Analysis of simulation result shows that there is about 30%

coverage radius gain when the lowest AMR-NB (4.75kbps) is used instead of the highest

AMR-NB (12.2kbps). When the lowest AMR-NB is used, a cell will accommodate twice

as many users as those when the highest AMR-NB is used.

2.4 ZWF21-04-014 Adaptive Radio Bearer Control

In order to improve the user experience, ZTE RAN sets up the AMR services, including

AMR-NB and AMR-WB, by using the maximum AMR rate among the rates assigned by

CN in the area of good coverage and light load. But in the area of poor coverage or high

load, AMR service setup success rate and the system capacity of the area are more

important. So ZTE RAN supports to set up AMR services by using lower AMR rates in

such area which needs lower transmitted power and consumes fewer resources.



2.5 ZWF21-06-002 TrFO

WCDMA employs AMR compressed voice encoding. At the R99 stage, TDM bearer is

used between CS core network devices, and voice must employ 64 kbit/s PCM encoding.

One very important function of the R99 MSC is voice Transcoder (TC), which converts

the AMR voice codes of a mobile terminal into the PCM codes and transmits them over a

network. The calls between mobile users require two voice encoding/decoding

conversions, AMR-PCM-AMR. Frequent encoding/decoding, which reduces voice

quality.

In view of this, the 3GPP organization has introduced the Tandem Free Operation (TFO)

and Transcoder Free Operation (TrFO) in the R4 protocol to avoid voice

encoding/decoding. In the meantime, the TFO and TrFO help save the transmission

network bandwidth between core networks. The differences between both technologies

are as follows: The TFO still needs TC resource. After the call is established, a direct

connection is established between the TCs of the calling and called MSCs by means of

in-band signaling negotiation to bypass encoding/decoding. The TrFO does not need any

TC resource at all. It means that out-band signaling encoding/decoding function (OoBTC)

is used during call establishment to implement consistent voice encoding/decoding

negotiation between UE and network.

The TFO technology is implemented in the core network equipment without the RAN

equipment. The TrFO technology requires that RAN equipment should support out-band

voice encoding negotiation and the processing related to a user plane. Both the TFO and

TrFO can also be used for AMR-WB encoding.

ZTE RAN equipment supports the TrFO function and complies with the 3GPP TS 23.153

and TS 25.415.



3 Technical Descriptions

3.1 Signaling Flow of the AMR Service

The setup flow of the AMR-WB and AMR-NB services is practically identical to that of

common services. The following example describes the setup flow of the DCH service in

the synchronous mode.

Figure 3-1 Signaling Flow of AMR Service

6. Downlink Synchronisation

7. Uplink Synchronisation

UE Node B

Serving RNS

Serving

RNC

CN

RRC RRC

10. DCCH : Radio Bearer Setup Complete

NBAP NBAP 4. Radio Link Reconfiguration Ready

DCH-FP

NBAP NBAP 8. Radio Link Reconfiguration Commit

RRC RRC

9. DCCH : Radio Bearer Setup

Apply new transport format set

Select L1, L2 and Iu Data

Transport Bearer parameters

RANAP RANAP

11. RAB Assignment

Response

5. ALCAP Iub Data Transport Bearer Setup

2. ALCAP Iu Data

Transport Bearer Setup

Not required towards PS

domain

RANAP RANAP

1. RAB Assignment

Request

[Establishment]

NBAP NBAP 3. Radio Link Reconfiguration Prepare

[DCH Addition]

DCH-FP DCH-FP

DCH-FP

1 CN initiates the establishment of the radio access bearer with the RANAP message

Radio Access Bearer Assignment Request. The important parameters for CS are as

follows:



NAS Synchronization Indicator (optional) indicates the speech codec type selected

by CN, and RNC will pass it to the UE through radio interface. The codec types

related to UMTS are listed as follows. For details, refer to 3GPP 26.103. If UE does

not receive this IE during the setup of a voice call or the inter-system handover of a

voice call to the UTRAN, the UMTS_AMR_2 speech codec is adopted by default.

UMTS_AMR_2 is compatible with GSM FR AMR.

Bit 8Bit 1

CoID (Codec

Identification)

Codec_Type Name

0000.0101 UMTS Adaptive

Multi-Rate

UMTS AMR


Multi-Rate 2

UMTS AMR 2


Multi-Rate Wide Band

UMTS AMR-WB

RAB parameters including QoS, such as

Traffic Class is conversational.

MBR (Maximum Bit Rate) in the unit of bit/s

GBR (Guaranteed Bit Rate) in the unit of bit/s

Delivery Order, set to provide in-sequence SDU delivery for the CS

SDU parameters, which characterizes the sub-flows of the CS.

Source Statistics Descriptor, which is set to speech for the CS

Allocation/Retention Priority

User Plane Information, such as

User Plane Mode, set to support mode for predefined SDU sizes for AMR

services

UP Mode Versions, which means the Iu UP Mode Versions supported by CN.

Each bit, in the two octet field, indicates a Iu UP Protocol version. The most



significant bit indicates version 16 and the least significant bit indicates version

1. (e.g. version 1 supported is coded "0001" = 1, version 2 supported is coded

"0010" = 2, and both version 1 and 2 supported is coded 0011" = 3.). For

support mode for predefined SDU sizes, version 1 and version 2 are defined

currently.

Transport Layer Information, such as Transport Address, Iu Transport Association,

etc.

2 SRNC initiates the setup of Iu Data Transport bearer by using the ALCAP protocol.

This request contains the AAL2 Binding Identity to bind the Iu Data Transport Bearer

to the Radio Access Bearer (this step is not required for PS domain, for it uses AAL5

in user plane).

3 SRNC requests its Node B to prepare the establishment of DCH to carry the radio

access bearer (Radio Link Reconfiguration Prepare). The parameters include

Transport Format Set, Transport Format Combination Set, and power control

information.

4 Node B allocates resources and notifies SRNC that the radio link reconfiguration is

ready (Radio Link Reconfiguration Ready). The parameters include the transport

layer addressing information (AAL2 address and AAL2 Binding ID) for Iub Data

Transport Bearer.

5 SRNC initiates the setup of Iub Data Transport Bearer by using the ALCAP protocol.

This request contains the AAL2 Binding Identity to bind the Iub Data Transport

Bearer to DCH.

6 The Node B and SRNC establish the synchronization for the Iub or Iur Data

Transport Bearer by means of exchange of the appropriate DCH Frame Protocol

frames Downlink Synchronization.

7 The Node B and SRNC establish the synchronization for the Iub or Iur Data

Transport Bearer by means of exchange of the appropriate DCH Frame Protocol

frames Uplink Synchronization.

8 The NBAP message Radio Link Reconfiguration Commit is sent from the SRNC to

the Node B.



9 The RRC message Radio Bearer Setup is sent from the SRNC to the UE. The

parameters include Transport Format Set and Transport Format Combination Set.

10 UE sends the RRC message Radio Access Bearer Setup Complete to the SRNC.

11 SRNC sends the RANAP message Radio Access Bearer Assignment Response to

the CN.

3.2 Conversational RAB for AMR-NB

3.2.1 AMR-NB Rates Selection

The 3GPP protocol defines eight speech rates and one SID for UMTS AMR-NB, which

supports the speech rate up to 12.2 kbps. Here, the feature of AMR Adaptive Radio

Bearer Control is not involved.

3.2.1.1 RAB Assignment

If the value of UP Mode Versions in the RAB ASSIGNMENT REQUEST message is set

to 1, which means the CN only supports Iu UP Mode version 1, the available rates for

the service are determined in the intersection operation between the configured rates on

the RNC and the received MBR and GBR from the CN, and sent to the CN through the

initialization procedure on user plane. The related parameters are amrNbMode0UseTag

(4.75 kbps), amrNbMode1UseTag (5.15 kbps), amrNbMode2UseTag (5.9 kbps),

amrNbMode3UseTag (6.7 kbps), amrNbMode4UseTag (7.4 kbps), amrNbMode5UseTag

(7.95 kbps), amrNbMode6UseTag (10.2 kbps) and amrNbMode7UseTag (12.2 kbps),

which can be set to be used or not used on the RNC.


to 2, which means the CN only supports Iu UP Mode version 2, RNC supports all the

requested compound RAB sub-Flow Combination assigned by the CN.


to 3, which means the CN supports Iu UP Mode version 1 and version 2, when

IntraRatV1V2AmrCut is set to cut, the action on the RNC side is the same as that of the



UP Mode Versions which is set to 1. When IntraRatV1V2AmrCut is set to not cut, the

action on the RNC side is the same as that of the UP Mode Versions which is set to 2.

The default value of IntraRatV1V2AmrCut is not cut.

3.2.1.2 GBR Reservation for the AMR Service

When the value of UP Mode Versions in the RAB ASSIGNMENT REQUEST is 1, or the

value of UP Mode Versions is 3 and IntraRatV1V2AmrCut is set to cut, the AMR-NB or

AMR-WB rates that are configured by the OMC may be different from the AMR rates in

the RAB ASSIGNMENT REQUEST, so the actual AMR-NB or AMR-WB rates that are

selected should be the intersection of the above two sets of AMR rates. And the GBR in

RAB ASSIGNMENT REQUEST may be not included in the rates configured by the RNC.

The parameter amrGbrResInd is used to determine whether the GBR in RAB

ASSIGNMENT REQUEST is included mandatorily.

If amrGbrResInd is set to 1: True, the actual AMR-NB or AMR-WB rates that are

selected should be the intersection of the above two sets of AMR rates, and the union set

of the GBR in RAB ASSIGNMENT REQUEST. GBR is the GBR rate in RAB

ASSIGNMENT REQUEST.

If amrGbrResInd is set to 0: False, the actual AMR-NB or AMR-WB rates that are

selected should be the intersection of the above two sets of AMR rates. And GBR is the

minimum rate in the intersection set, which are larger than or equal to the GBR in RAB

ASSIGNMENT REQUEST.

3.2.2 Combination of AMR-NB Service and PS Service

This function supports the combination of AMR-NB service and PS service.

3.2.3 AMR-NB Mobility

This function supports the soft handover, hard handover, and relocation of AMR-NB

service, and the handover between 2G and 3G.



3.2.4 Directed Retry of the AMR-NB Service In the Process of RAB

Assignment

This function supports the directed retry of AMR-NB service in the process of RAB

assignment. For example, if the load of the cell is too heavy, the UE will be directed to the

2G when the conditions are met. For details, refer to the ZTE UMTS Load Balance

Feature Guide.

3.2.5 Default Configuration of AMR-NB rates: 12.2k, 12.2/7.95/5.9/4.75k

and 7.95kbps

This function supports the default configuration of AMR-NB rates: 12.2 kbps,

(12.2/7.95/5.9/4.75 kbps) and 7.95 kbps. It is used for the handover from 2G to 3G. The

RNC determines the default configuration according to the MBR and GBR in the

Relocation Request message received from the CN, establishes the bearer according to

this default configuration, sets the default configuration in the HANDOVER TO UTRAN

COMMAND message, and sends this message to the UE through the 2G network.

3.2.6 RAB Modification of the AMR-NB

This function supports the RAB modification for AMR-NB service initiated by the CN

through RAB ASSIGNMENT REQUEST. At present, the main scenarios for the CN to

initiate the RAB modification for the AMR-WB include the TFO or TrFO conditions

satisfied after handover, call forwarding, and intelligent service.

3.3 AMR-WB Speech Support

3.3.1 AMR-WB Rates Selection

3.3.1.1 RAB Assignment

The principle of AMR-WB rate selection is the same as that of AMR-NB. The difference is

only the parameters for AMR-WB and AMR-NB to control rate configurations on the

RNC.



Through configuring the parameter wAmrSupInd, AMR-WB is enabled.


to 1, which means the CN only supports Iu UP Mode version 1, the available rates for

the service are determined in the intersection operation between the configured rates on

the RNC and the received MBR and GBR from the CN, and sent to the CN through the

initialization procedure on user plane. The related parameters are amrWbMode0UseTag

(6.6 kbps), amrWbMode1UseTag (8.85 kbps), amrWbMode2UseTag (12.65 kbps),

amrWbMode3UseTag (14.25 kbps), amrWbMode4UseTag (15.85 kbps),

amrWbMode5UseTag (18.25 kbps), amrWbMode6UseTag (19.85 kbps),

amrNbMode7UseTag (23.05 kbps) and amrNbMode8UseTag (23.85 kbps), which can

be set to be used or not used on the RNC.


to 2, which means the CN only supports Iu UP Mode version 2, the RNC supports all

the requested compound RAB sub-Flow Combination assigned by the CN.


to 3, which means the CN supports Iu UP Mode version 1 and version 2, when

IntraRatV1V2AmrCut is set to cut, the action on the RNC side is the same as that of the

UP Mode Versions which is set to 1. When IntraRatV1V2AmrCut is set to not cut, the

action on the RNC side is the same as that of the UP Mode Versions which is set to 2.

Note: The AMR-WB supports the voice bandwidth 50 Hz-7 kHz (the AMR-NB supports

the voice bandwidth 200 Hz-3.4 kHz). Therefore, it has better voice quality than the

AMR-NB. Among the rates supported by the AMR-WB, 12.65kbps is the minimum rate

that can achieve high-quality sound effects. The MOS values of 6.6 kbps, 8.85 kbps, and

12.65 kbps apparently increase as the rate rises. The MOS values of 12.65kbps,

14.25kbps, 15.85kbps, 18.25kbps, and 19.85kbps do not apparently increase as the rate

rises. So the rates of 12.65 kbps, 8.85 kbps, and 6.6 kbps are recommended by the

3GPP.

3.3.1.2 GBR Reservation for the AMR Service

The principle of GBR reservation for AMR-WB is the same as that of AMR-NB. Please

refer to 3.2.1.2.



3.3.2 Combination of AMR-WB Service and PS Service

The setup of a single AMR-WB service and the concurrency of the AMR-WB and PS

services are supported in the same way as the AMR-NB.

3.3.3 AMR-WB Mobility

Like the AMR-NB control policy, this function supports soft handover, hard handover,

relocation, and 2G-3G handover for the AMR-WB service. This function uses the present

parameters without new handover parameter added.

3.3.4 Directed Retry of the AMR-WB Service In the Process of RAB

Assignment

Like the AMR-NB control policy, this function supports directed retry of the AMR-WB

service in the process of RAB assignment. This function uses the present parameters

without new load balancing parameter added.

3.3.5 RAB Modification of the AMR-WB

The RNC does not support to initiate the RAB modification for the AMR-WB service, but

support the RAB modification initiated by the CN for the AMR-WB, which is performed in

a way similar to that of the AMR-NB. At present, the main scenarios for the CN to initiate

the RAB modification for the AMR-WB include the TFO or TrFO conditions satisfied after

handover, call forwarding, and intelligent service.

3.4 AMR Dynamic Rate Controlling

3.4.1 Classification of AMR Dynamic Rate Adjustment

This function supports dynamic rate adjustment for the AMR service triggered by link

level, resource congestion, and load control during the call holding procedure. If the rate

adjustment threshold is met, the uplink rate is controlled by the RNC through the TFC

Control, and the downlink rate is controlled by the RNC through the Iu UP reverse rate

control frame.



According to the types of AMR, AMR dynamic rate adjustment is classified into AMR-NB

dynamic rate adjustment and AMR-WB dynamic rate adjustment. The AMR-WB rate

adjustment principles and steps are the same as those of the AMR-NB.

The AMR-NB and AMR-WB dynamic rate adjustment is controlled by the configuration

parameter amrRncAdjust.

There are three types of AMR dynamic rate adjustment depending on the trigger

mechanisms:

AMR dynamic rate adjustment based on transmitted power at link level

Due to inner-loop power control, the uplink/downlink transmitted power at link level varies

with the change of the radio environment between the transmitting antennas of UE and

the Node B. When the radio environment degrades, the RNC should reduce the AMR

rate to decrease transmitted power. This serves to avoid heavy uplink/downlink load of a

cell resulting from the increase in transmitted power of AMR. When the transmitted

power of AMR is low and the system load is light, the RNC may increase the AMR to

provide users with better voice quality by making full use of system resources.

AMR rate adjustment triggered by the uplink/downlink resource congestion or cell

overload

Reduce the rate of uplink/downlink AMR service to lighten the uplink/downlink resource

congestion.

Initial AMR rate adjustment triggered if the cell is highly loaded or UE is in a bad

coverage area

When a cell is highly loaded or the UE is in a bad coverage area, the initial, also the

maximum, AMR service rate should be reduced to lighten the cell load and improve the

link performance. Please refer to the AMR Adaptive Radio Bearer Control.

For these three trigger mechanisms, ZTE RNC can only adjust the rate of AMR-NB and

AMR-WB services in the range of AMR-NB and AMR-WB rates respectively.

In terms of the currently implemented functions and AMR service running, ZTE considers

it unnecessary to control an uplink rate with the granularity as accurate as TTI. Therefore,



ZTE has not yet implemented SRB5-based uplink AMR-NB and AMR-WB rate

adjustment.

3.4.2 AMR Dynamic Rate Adjustment Based on Transmitted Power at Link

Level

AMR-WB dynamic rate adjustment and AMR-NB dynamic rate adjustment involve uplink

and downlink direction. They have the same principle and use the same threshold. In

view of this, they are unified as the AMR dynamic rate adjustment and described here.

3.4.2.1 Uplink Rate Adjustment Based on the UE Transmitted Power

3.4.2.1.1 Measurement Quantity

The AMR rate adjustment in uplink is base on the UE internal measurement reports of

UE TxP (Transmitted Power). There are two kinds of event, Event 6a and Event 6b.

Event 6a: when the UE TxP measurement value is greater than a certain absolute

threshold and this condition lasts for a moment (UAmrEvtTPUeInt.meaEvtId is the

corresponding UAmrEvtTPUeInt.trigTime of 6a), the Event 6a is reported by the UE.

Event 6b: when the UE TxP measurement value is smaller than a certain absolute

threshold and this condition lasts for a moment (UAmrEvtTPUeInt.meaEvtId is the

corresponding UAmrEvtTPUeInt.trigTime of 6b), the Event 6b is reported by the UE.

The parameters for 6a and 6b can be configured at cell level. Through configuring

UUtranCellFDD.refUUeIntMeasProfile in the cell, the UUeIntMeasProfile can be indexed.

And the detailed parameters for 6a and 6b are contained in UAmrEvtTPUeInt of

UUeIntMeasProfile.

The number of internal measurement events is configured by

UAmrEvtTPUeInt.measEvtNum. It can be set to 2, for there are 6a and 6b. To facilitate

the description, it is assumed that 0 represents 6a and 1 represents 6b.

The threshold parameter of Event 6a/6b (UAmrEvtTPUeInt.txPowerThres) is a delta

value relative to maximum UE TX power = min (UE maximum transmitted power

determined by UE power class, maxUlDpchPwr). maxUlDpchPwr is the maximum



transmitted power determined by the sub-service type of CS. The default value is usually

set to 33 dBm. And the UE maximum transmitted power determined by the UE power

class is listed as follows.

Power Class 3 4

maximum output power of

the UE (dBm)

+24 +21

The absolute thresholds are as follows.

AMR_6a = maximum UE TX power + UAmrEvtTPUeInt.txPowerThres[0]

AMR_6b = maximum UE TX power + UAmrEvtTPUeInt.txPowerThres[1]

The correspondence between other parameters that need to be filled in UE internal

measurement control message and OMCR configuration is described as follows.

Measurement Information Element in

MEASUREMENT CONTROL Parameter name

Measurement report transmission mode UAmrEvtTPUeInt.measRptTrMod

UE internal event identity UAmrEvtTPUeInt.meaEvtId

Time-to-trigger (Time in ms) UAmrEvtTPUeInt.trigTime

UE Transmitted Power Tx power threshold

(Power in dBm)

maximum UE TX power +

UAmrEvtTPUeInt.txPowerThres

Filter coefficient UAmrEvtTPUeInt.filterCoeff

3.4.2.1.2 Rate Control Principles

If AMR service exists,, amrRncAdjust is On, and the number of uplink AMR rates is

larger than 1, the UE TxP measurement is triggered. Otherwise, the UE TxP

measurement is switched off.

Its operating principles are as follows:

When the uplink transmitted power reported by the UE exceeds the threshold

AMR_6a, the AMR should be reduced by one level if the current uplink AMR is not

the minimum rate. After degrading the uplink AMR level, the new measurement

control will be sent to the UE.



When the uplink transmitted power reported by the UE is lower than the threshold

AMR_6b, the AMR rate should be increased by one level if the current uplink AMR

is not the maximum rate and the uplink load of the system is neither overloaded nor

congested. After upgrading the uplink AMR level, the new measurement control will

be sent to the UE.

In the TrFO connection mode, the following judgments must be added on the basis of the

steps above:

If the target value of the AMR uplink rate increase originated from the RNC is smaller

than or equal to the maximum uplink rate of the Iu port, it is allowed to originate the rate

increase, which then will be admitted by the admission control module. If the target value

of the rate increase originated from the RNC is greater than the maximum uplink rate of

the Iu port, it is rejected to originate the rate increase.

When the RNC receives the rate control command from the CN, the maximum rate is the

uplink target rate required by the CN. The admission control module determines whether

the target rate can be allowed by the current RNC side according to the uplink load state

of the current cell and the UE transmitted power measurement report. If the target rate is

allowed, RNC returns this rate in the rate control response command to the peer. At the

same time, the RNC sends the TFC control command to the UE, requiring adjustment of

the UE uplink rate to the target rate; otherwise, the RNC sends the Rate Control NACK to

the CN.

3.4.2.2 Downlink Rate Adjustment Based on the Dedicated Measurement of Node

B Transmitted Power

3.4.2.2.1 Measurement Quantity

The downlink AMR rate adjustment is based on the D-TCP (Dedicated Transmitted Code

Power) measurement report from Node B. The Node B dedicated TCP is related to the

UE. It indicates that the downlink transmitted power for the UE (the TCP on the given

carrier, given scramble, and given channelization code) is measured by the Node B. The

Node B dedicated TCP measurement for the AMR rate control is reported periodically

and the period length is configured by RptPrd, Because of the periodical report, whether



the criterion for Event A or Event B is satisfied is determined by the RNC. Event A and

Event B are defined as follows:

Event A: when the Node B D-TCP measurement value is greater than a specific

absolute threshold (conversion from the corresponding evtAbTcpThrd[0] of

nbDMCfgNote=7) for a period of time (the corresponding evtAbcdefTime of

nbDMCfgNote=7), the Event A is triggered. The Event A is used to trigger the

downlink rate decrease. When the criterion of Event A is satisfied, the downlink

transmitted power for a certain UE is considered to be in a high power status.

Event B: when the Node B D-TCP measurement value is smaller than a specific

absolute threshold (conversion from the corresponding evtAbTcpThrd[0] of

nbDMCfgNote=8) for a period of time (the corresponding evtAbcdefTime of

nbDMCfgNote=8), the Event B is triggered. The Event B is used to check whether

the downlink transmitted power is in a low status. When the criterion of Event B is

satisfied, the downlink transmitted power for a certain UE is considered to be in a

low power status.

Therein, evtAbTcpThrd[0] is the power offset to maxDlDpchPwr of the CS sub-service

type.

AMR_A = maxDlDpchPwr + evtAbTcpThrd[0] (nbDMCfgNote=7)

AMR_B = maxDlDpchPwr + evtAbTcpThrd[0] (nbDMCfgNote=8)

The correspondence between other parameters that need to be filled in dedicated

measurement initiation request message and OMCR configuration is described as

follows.

Measurement Information Element in

DEDICATED MEASUREMENT INITIATION

REQUEST

Parameter name

Dedicated Measurement Type dedMeasType taking the value

of Transmitted Code Power

Measurement Filter Coefficient measFilterCoeff

Report Characteristics rptType



3.4.2.2.2 Rate Control Principles

If AMR service exists, and amrRncAdjust is On, and the number of downlink AMR rates

is larger than 1, the measurement is triggered. Otherwise, the Node B dedicated TCP

measurement is switched off.

The basic principles are as follows:

When the special downlink transmitted power reported by Node B exceeds the

threshold AMR_A for dtcpEaThd consecutively, the downlink AMR should be

reduced by one level if the current downlink AMR is not the minimum rate.

When the special downlink transmitted power reported by Node B is lower than the

threshold AMR_B for dtcpEbThd consecutively, the downlink AMR should be

increased by one level if the current downlink AMR is not the maximum rate and the

downlink load of the system is neither overloaded nor congested.

In the TrFO connection mode, the downlink rate depends on the downlink rate of

the Iu port. In a Mobile to Mobile call, the downlink rate depends on the uplink rate

of the peer. Therefore, the downlink AMR-WB rate adjustment algorithm has the

following changes in comparison with the non-TrFO connection mode:

When the local side needs to adjust the downlink AMR, the RNC sends the

adjusted target rate through the rate control command to the CN, which then sends

this rate through the rate control command to the peer RNC. The returned rate

control response command contains the maximum uplink rate available with the

peer. The peer UE sends data at the smaller rate between the maximum uplink rate

supported by the peer and the target rate required by the local side, so as to

complete the downlink rate adjustment for the local side.

When the uplink rate of the peer is decreased, the downlink rate of the local side will

be decreased accordingly.

When the uplink rate of the peer is increased, the downlink rate of the local side will

be increased accordingly, resulting in the change of the cell downlink load and the

downlink D-TCP. The RNC should determine whether to decrease the increasing

downlink rate according to the cell downlink load and the downlink D-TCP

measurement report. If the downlink rate should be decreased, the RNC sends to



the CN the rate control command that contains the maximum rate supported by the

local side, so as to control the downlink rate of the Iu port.

3.4.3 Dynamic Adjustment Triggered by Load

In case of uplink or downlink overload on a cell, the RNC should decrease the rate of

some AMR services by priority. When the uplink or downlink is not overloaded, the RNC

should increase step by step the rate of any decreased AMR service that meets the rate

increase conditions described above for Event 6b or Event B. This dynamic adjustment

also applies to the AMR-WB.

When the switch of forbidding AMR downgrade is on (GresPara47:bit6 = 1), the AMR

downgrade command triggered by load control is not implemented until the switch is

turned off (GresPara47:bit6 = 0). For details, please refer to the ZTE UTMS Overload

Control Feature Guide.

3.4.4 Dynamic Adjustment Triggered by Resource Congestion

In case of uplink or downlink resource congestion, the RNC should decrease the rate of

some AMR services by priority. When the uplink or downlink resource congestion is

cleared, the RNC should increase step by step the rate of any decreased AMR service

that meets the rate increase conditions described above for Event 6b or Event B. This

dynamic adjustment also applies to the AMR-WB. When the switch of forbidding AMR

downgrade is set to on (GresPara47:bit6 = 1), the AMR downgrade command triggered

by congestion control is not implemented until the switch is set to off (GresPara47:bit6 =

0). For details, please refer to ZTE UMTS Congestion Control Feature Guide.

3.5 AMR Adaptive Radio Bearer Control

When the cell is highly loaded or the UE is in a bad coverage area, directly decreasing

the maximum AMR-NB and AMR-WB rate at call setup could be of higher capacity gain

and improve the admission success rate than decreasing the rate after the call is setup.



This feature is only applied to the situation that the value of UP Mode Versions in RAB

ASSIGNMENT REQUEST is 1 or 3. When the value is 2, the initial rate will take the

largest one in values smaller than or equal to the MBR that is not involved here.

When the AMR service is set up, and the value of UP Mode Versions in RAB

ASSIGNMENT REQUEST message is 1 or 3, if at least one of the following conditions is

met:

The best cell downlink load is larger than amrDlLdThrd ;

The best cell uplink load is larger than amrUlLdThrd;

AmrBadCovSwh is set to "Supported" and the best cell P-CPICH Ec/No reported is

smaller than or equal to BadCovEcN0 ;

AmrBadCovSwh is set to "Supported" and the best cell P-CPICH RSCP reported is

smaller than or equal to BadCovRscp;

a smaller initial AMR rate should be determined on the RNC which will be sent to the CN

in the initialization procedure on user plane. The initial AMR rate determined is also the

maximum AMR rate after the call is set up. The value of nAmrInitialRate or

wAmrInitialRate is usually set to the one smaller than the MBR in the RAB

ASSIGNMENT REQUEST.

If the conditions mentioned above are not met, the selection of rates is the same as

3.2.1 AMR-NB Rates or 3.3.1 AMR-WB Rates.

For the service handover from 2G to 3G, there is no smaller initial rate based on the load.

The flow chart to determine the initial AMR rate on the RNC is as follows.



3.5.1 AMR-NB Adaptive Radio Bearer Control

For the AMR-NB service, if the value of UP Mode Versions in the RAB ASSIGNMENT

REQUEST message is set to 1, or the value of UP Mode Versions is set to 3 and

intraRatV1V2AmrCut is set to cut, a rate set according to 3.2.1.1 RAB and 3.2.1.2

GBR Reservation for the AMR is generated.

If the value of UP Mode Versions is set to 3 and intraRatV1V2AmrCut is set to not cut,

a rate set according to RAB ASSIGNMENT REQUEST is generated.

If the cell is highly loaded or the UE is in a bad coverage area as mentioned above, the

initial AMR-NB rate should be determined according to the following principles:

If the GBR in the above set is larger than nAmrInitialRate, the initial AMR-NB rate

equals to the GBR.

If the GBR in the above set is less than or equal to nAmrInitialRate, the initial rate

should be the largest rate among the rates that are less than or equal to

nAmrInitialRate and larger than or equal to the GBR.



3.5.2 AMR-WB Adaptive Radio Bearer Control

For the AMR-WB service, if the value of UP Mode Versions in the RAB ASSIGNMENT

REQUEST message is set to 1, or the value of UP Mode Versions is set to 3 and

intraRatV1V2AmrCut is set to cut, a rate set according to 3.3.1.1 RAB and 3.3.1.2

GBR Reservation for the AMR is generated.

If the value of UP Mode Versions is set to 3 and intraRatV1V2AmrCut is set to not cut,

a rate set according to RAB ASSIGNMENT REQUEST is generated.

If the cell is highly loaded or the UE is in a bad coverage area as mentioned above, the

initial AMR-WB rate should be determined according to the following principle:

If the Guaranteed Bit Rate in the above set is larger than wAmrInitialRate, the initial

AMR-WB rate equals to the GBR.

If the GBR in the above set is less than or equal to wAmrInitialRate, the initial rate

should be the largest rate among the rates that are less than or equal to

wAmrInitialRate and larger than or equal to the GBR.

3.5.3 AMR Rate Control after Relocation

Due to the UE compatibility, it will become mute for some UEs if the AMR-NB or

AMR-WB service rate is changed after the inter-RNC soft handover or hard handover

relocation. So, bit7 of GresPara47 is used to control whether the AMR-NB or AMR-WB

service rate is allowed to be changed after the relocation.

If bit7 of GresPara47 is set to 0, or the AMR-NB or AMR-WB service rate before the

relocation is not contained in the Relocation Request message, or the Iu UP version is

V2, AMR-NB or AMR-WB service rate changing after the inter-RNC relocation is allowed.

The AMR-NB or AMR-WB service rates set and the actual AMR-NB or AMR-WB service

rate after relocation is determined according to the methods described in other sections.

If bit7 of GresPara47 is set to 1, and the AMR-NB or AMR-WB service rate before the

relocation is contained in the Relocation Request message, and the Iu UP version is V1,

the AMR-NB or AMR-WB service rate changing after the inter-RNC relocation is not

allowed. The AMR-NB or AMR-WB service rates set only includes the AMR-NB or

AMR-WB service rates which are smaller than or equal to the actual AMR-NB or



AMR-WB service rate before the relocation. And the actual AMR-NB or AMR-WB service

rate after the relocation equals to the actual AMR-NB or AMR-WB service rate before the

relocation.

3.6 TrFO Support

At the R99 stage, voice at the CN CS employs 64kbit/s PCM encoding based on the

TDM bearer. Therefore, the R99 MSC must have the voice TC function. But voice

encoding/decoding is apt to reduce 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 nodes of a call connection. For example, for a call between the UMTS UE

and a fixed telephone, the TrFO connection only exists between the UMTS UE and a

core network. The core network and RNC in the TrFO connection must support the Iu UP

V2. Otherwise, no TrFO connection can be established. ZTE supports the Iu UP V1 and

Iu UP V2. The RNC will make a choice according to the CN RAB assignment

parameters.

The TrFO is implemented by employing the out-band 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 the compressed voice,

which improves the voice quality and saves the 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:



The insertion position should reduce the use of a transcoder and improve the voice

quality;

The insertion position should save the transmission bandwidth. That is, it should

prolong the connection which uses the compressed voice encoding data for

transmission.

In the process of Iu UP initialization, the ZTE RNC controls whether to cut some of the

AMR rates according to the RNC capability between CN and RNC in the RAB

assignment procedure and inter-RNC Relocation procedure by the parameter

intraRatV1V2AmrCut if the CN supports both Iu UP version 1 and version 2. And the ZTE

RNC controls whether to cut some of the AMR rates according to the RNC capability

between CN and RNC in the inter-RAT relocation procedure by the parameter

interRatV1V2AmrCut if the CN supports both Iu UP version 1 and version 2.

For a UTRAN, its Iu UP initialization, reverse initialization, Iu UP rate control, and Iu UP

reverse rate control are related to the TrFO process.

3.6.1 OoBTC Outband Codec Control

When a call is initiated, both call parties will negotiate about the codec so as to attempt to

establish a TrFO operation. In an IAM, the O-MSC carries the supported codec type list

and sends it to a transmission network. From the list, the transmission network deletes

the types that are not supported and sends it to a T-MSC. From the list, the T-MSC also

deletes the encoding types that are not supported. Then, the T-MSC selects an optimal

common encoding/decoding type, returns it to the transmission network and the O-MSC,

and notifies them of the currently selected encoding/decoding type. In the meantime, the

T-MSC feeds back the encoding/decoding type that the Terminating UE supports to the

O-MSC, and begins to establish the bearer on the basis of this codec. This flow is shown

in the following figure.



Figure 3-2 Flow of OoBTC Out-band Codec Control

Codec List (v, w, x, y, z)

Codec List (v, w, x, z)

O-MSC Transit T-MSC

O-MGW T-MGWTransit

MGW

Selected Codec = v, Available List (v, x, z, )

Selected Codec = v

Selected Codec = v

Selected Codec = v, Available

List (v, x, z, )

Selected Codec = v

Bearer Established Bearer Established

The encoding type that the UE supports is transparently transmitted to the RNC by

means of Uplink Direct Transfer-> NAS Message-> Bearer Capacity. Then, the RNC

transparently transmits the encoding type to the MSC Server by means of Direct Transfer

-> NAS Indicator ->Bearer Capacity. During RAB assignment, the encoding/decoding

type lists of the calling and called parties are completely the same.

3.6.2 Iu UP Initialization

Iu UP initialization serves to define the mapping relationship (used at the data

transmission stage) between the RNC and CN on both sides of Iu UP, including RAB

sub-flow combination, RFCIs, and SDU size of the related RAB sub-flow.

If a bearer is successfully established, the CN will deliver an RAB assignment request

message to the RNC. The RNC in R4 version must support all the SDU sub-flow

combinations in the RAB assignment request message. That is, the content in the

initialization frame is a universal set of sub-flow combinations determined by RAB

assignment. Therefore, the initialization frame will only be used to negotiate about the Iu

UP version information and RFCI correspondence (each RFCI corresponds to a sub-flow



combination). In the R99 version, this initialization process can only be initiated when the

RNC receives RAB assignment/modification or RNC relocation. In the R4 version, the

CN can also start this initialization process, called Iu UP reverse initialization. Iu UP

initialization is shown in the following figure.

Figure 3-3 Iu UP Initialization

*

Transfer Of User Data

CN/ RNC

INITIALISATION

((RFCI, SDU sizes[, IPTIs 2) ]) m )

INITIALISATION ACK

* can be repeated N INIT times 2) optional

RNC/ CN

In the RFCI set determined during Iu UP initialization, the rate which corresponds to the

first RAB sub-flow combination is the maximum rate in the initialization answer direction

permitted by the local end when data transmission begins. The maximum rate must be

greater than the guaranteed rate and SID rate. It can be modified during Iu UP rate

control after Iu UP initialization. The rate greater than the guaranteed rate is called a

controllable rate. The rate lower than the guaranteed rate cannot be modified.

3.6.3 Iu UP Rate Control

Iu UP rate control serves to notify the peer Iu UP protocol layer of the maximum rate at

the Iu port in the reverse direction of the rate control frame. In the R4 version, the Iu UP

rate control can be initiated by the RNC or the CN. In the R99 version, Iu UP rate control

can only be initiated by the RNC.

As long as an Iu UP entity is not suspended by other control flows, it can initiate rate

control. The controlled rates are all included in the RFC set determined during Iu UP

initialization. These rates that correspond to the RFC should be higher than the

guaranteed rate. "Rate control" cannot be implemented in terms of the SID rate and the

RFC lower than the guaranteed rate because they themselves cannot be prohibited.



Figure 3-4 Flow of Iu UP Rate Control

CN/ RNC

RNC/ CN

RATE CONTROL

(RFCI indicators)

RATE CONTROL ACK

(RFCI indicators)

Note: The rate control frame describes the use limit of an "RFC set", which is called

"RFC limit set" in the following parts.

In downlink direction, the RNC triggers the rate control frame, records the "RFC limit set"

(downlink direction), and monitors the implementation behavior of the CN. If the CN still

sends the data frame of the limited RFCI, the rate control frame must be resent. In uplink

direction, the Iu UP module of the RNC receives the rate control frame and implements

the limit by means of TFC control.

The rate control initiated by the CN is as follows: After receiving a rate control message

from the RNC, the CN initiates rate control to the other party of a call to limit or open the

other party's uplink AMR level. Or the CN initiates a rate adjustment flow on its own

according to the TrFO. For example, in SRNS relocation, the CN first performs the

reverse initialization after a new RNC sends relocation detection to the CN. Then, the

new RNC initiates a process called immediate initialization. This serves to negotiate

about the maximum rate for data transmission between two Iu UP entities which support

TrFO.

The rate control initiated by the RNC is as follows: during dynamic AMR process, the

RNC adjusts the downlink AMR level according the downlink load of a cell or the

dedicated TCP measurement of an RL, and initiates the rate control.

Compared with the encoding/decoding type negotiation before initialization, the Iu UP

rate control is in-band rate control.



4 Parameters and Configurations

4.1 Parameters of AMR-NB Service

4.1.1 Parameter List

No. Abbreviate Parameter name

1 amrNbMode0UseT

ag

AMR_NB 4.75k Use Tag

2 amrNbMode1UseT

ag


3 amrNbMode2UseT

ag


4 amrNbMode3UseT

ag


5 amrNbMode4UseT

ag


6 amrNbMode5UseT

ag


7 amrNbMode6UseT

ag


8 amrNbMode7UseT

ag


9 interRatV1V2AmrC

ut

Inter-RAT V1+V2 Amr Cut Decision

10 intraRatV1V2AmrC

ut

Intra-RAT V1+V2 Amr Cut Decision

4.1.2 Parameter Configurations

4.1.2.1 AMR_NB 4.75k Use Tag

OMC Path

Path: Managed Element->UMTS Logical Function Configuration->Plmn Specific

Function->Logic RNC Configuration->AMR_NB 4.75k Use Tag



Parameter Configuration

The use of the label AMR_NB 4.75k 0: not used

1: used


OMC Path





1: used


OMC Path





1: used


OMC Path







1: used


OMC Path





1: used


OMC Path





1: used


OMC Path





1: used




OMC Path





1: used

4.1.2.9 Inter-RAT V1+V2 Amr Cut Decision

OMC Path

Path: Managed Element->UMTS Logical Function Configuration->Inter-RAT V1+V2 Amr

Cut Decision



AMR rates in the process of RAB assignment according to the AMR rates set supported

by the in the inter-RAT relocation procedure by the parameter if the CN supports both

IuUP Version1 and Version2.

4.1.2.10 Intra-RAT V1+V2 Amr Cut Decision

OMC Path

Path: Managed Element->UMTS Logical Function Configuration->Intra-RAT V1+V2 Amr

Cut Decision



AMR rates according to the AMR rates set supported by the RNC in the process of RAB

assignment and inter-RNC relocation by the parameter if the CN supports both Iu UP

version1 and version2.



4.2 Parameters of WB-AMR Service



1 wAmrSupInd WB-AMR Speech Support Indicator

2 amrWbMode0UseT

ag

AMR_WB 6.60k Use Tag

3 amrWbMode1UseT

ag


4 amrWbMode2UseT

ag


5 amrWbMode3UseT

ag


6 amrWbMode4UseT

ag


7 amrWbMode5UseT

ag


8 amrWbMode6UseT

ag


9 amrWbMode7UseT

ag


10 amrWbMode8UseT

ag


11 interRatV1V2AmrC

ut

Inter-RAT V1+V2 Amr Cut Decision

12 intraRatV1V2AmrC

ut

Intra-RAT V1+V2 Amr Cut Decision


4.2.2.1 WB-AMR Speech Support Indicator

OMC Path


Function->Logic RNC Configuration->WB-AMR Speech Support Indicator




This parameter indicates whether the RNC supports the AMR-WB voice services.

4.2.2.2 AMR_WB 6.60k Use Tag

OMC Path


Function->Logic RNC Configuration->AMR_WB 6.60k Use Tag


The use of the label AMR_WB 6.60k 0: not used

1: used


OMC Path





1: used


OMC Path





1: used




OMC Path





1: used


OMC Path





1: used


OMC Path





1: used


OMC Path







1: used


OMC Path





1: used


OMC Path





1: used

4.2.2.11 Inter-RAT V1+V2 Amr Cut Decision

Please refer to 4.1.2.9.



4.2.2.12 Intra-RAT V1+V2 Amr Cut Decision


4.3 Parameters of Uplink AMR Dynamic Rate

Adjustment Based on UE Transmitted Power



1 amrRncAdjust AMR Rate Adjustment Switch for RNC

2 refUUeIntMeasProf

ile

Used UE Internal Measurement Profile

3 profileId Profile Id

4 measRptTrMod Measurement Report Transfer Mode

5 filterCoeff Filter coefficient

6 measEvtNum Maximum Event Number of UE Internal

Measurement

7 meaEvtId UE Internal Measurement Event Identity

8 trigTime Time to Trigger

9 txPowerThres UE Transmitted Power Threshold

10 maxUlDpchPwr Maximum Allowed Uplink DPCH Transmission Power


4.3.2.1 AMR Rate Adjustment Switch for RNC

OMC Path


Function->Logic RNC Configuration->AMR Rate Adjustment Switch for RNC




When the value of this parameter is "Off", AMR dynamic rate adjustment will not be

triggered due to the UE internal measurement and Node B dedicated measurement;

when the value of this parameter is "On", AMR dynamic rate adjustment will be triggered

due to the above-mentioned measurement. When this parameter is set to be off, the

AMR voice quality remains unchanged in any case; when this parameter is set to be on,

the AMR voice quality may slightly degrade according to different scenarios, but the

system capacity can be increased accordingly.

4.3.2.2 Used UE Internal Measurement Profile

OMC Path

Path: Managed Element ->UMTS Logical Function Configuration->UTRAN Cell->Used

UE Internal Measurement Profile


This parameter indicates the UE internal measurement profile object ID.

4.3.2.3 Profile Id

OMC Path

GUI: Managed Element ->UMTS Logical Function Configuration->Service

Configuration->Measurement Configuration->UE Internal Measurement Profile->Profile

Id


This parameter indicates the index number of a UE internal measurement profile. The

RNC can be configured with different sets of UE internal measurement parameters.

Different cells can use this parameter to indicate different configuration information.

4.3.2.4 Measurement Report Transfer Mode

OMC Path

Path: Managed Element ->UMTS Logical Function Configuration->Service

Configuration->Measurement Configuration->UE Internal Measurement Profile->UE



Transmitted Power Event Measurement Configuration for AMR->Measurement Report

Transfer Mode


This parameter indicates the RLC mode of the UE internal measurement report.

4.3.2.5 Filter Coefficient

OMC Path



Transmitted Power Event Measurement Configuration for AMR->Filter Coefficient


This parameter indicates the filtering factor that UE performs the L3 filtering on the

measurement results of the internal measurement.

4.3.2.6 Maximum Event Number of UE Internal Measurement

OMC Path



Transmitted Power Event Measurement Configuration for AMR->Maximum Event

Number of UE Internal Measurement


This parameter indicates the maximum event number of UE internal measurement.

4.3.2.7 UE Internal Measurement Event Identity

OMC Path





Transmitted Power Event Measurement Configuration for AMR->UE Internal

Measurement Event Identity


This parameter indicates the UE internal measurement event identity.

4.3.2.8 Time to Trigger

OMC Path



Transmitted Power Event Measurement Configuration for AMR->Time to Trigger


This parameter indicates the period of time during which the event condition has to be

satisfied before sending a measurement report.

4.3.2.9 UE Transmitted Power Threshold

OMC Path



Transmitted Power Event Measurement Configuration for AMR->UE Transmitted Power

Threshold


This parameter indicates the UE transmitted power threshold in event 6a/6b.

4.3.2.10 Maximum Allowed Uplink DPCH Transmission Power

OMC Path

Path1: Managed Element ->UMTS Logical Function Configuration->Service

Configuration->Service Function->Power Control Profile Related to Service->Power



Control Related to Service->Power Control Related to Service and Diversity

Mode->Maximum Allowed Uplink DPCH Transmission Power


Configuration->Service Function->Power Control Related to Service for White List

->Maximum Allowed Uplink DPCH Transmission Power


It is a background configuration value. The greater this value is, the higher the maximum

permissible uplink transmitted power is. It is related to the service sub-class.

4.4 Parameters of Downlink AMR Dynamic Rate

Adjustment Based on D-TCP



1 amrRncAdjust AMR Rate Adjustment Switch for RNC

2 nbDMCfgNote Function of Configuration Parameters

3 dedMeasType Dedicated Measurement Type

4 measFilterCoeff Measurement Filter Coefficient

5 rptType Report Characteristics

6 evtAbTcpThrd Measurement Threshold of Event A/B for

Transmitted Code Power

7 evtAbcdefTime Measurement Change Time/Measurement

Hysteresis Time

8 rptPrdUnit Choice Report Periodicity Scale

9 rptPrd Report Period

10 maxDlDpchPwr DPCH Maximum DL Power

11 dtcpEaThd Event A Counter Threshold for PS on DL DCH or DL

AMR Decreasing Rate on D-TCP

12 dtcpEbThd Event B Counter Threshold for Restriction PS

Increasing Rate on DL DCH or Triggering DL AMR

Increasing Rate Based on D-TCP




4.4.2.1 AMR Rate Adjustment Switch for RNC


4.4.2.2 Function of Configuration Parameters

OMC Path


Configuration->Measurement Configuration->Node B Dedicated Measurement

Profile->Node B Dedicated Measurement Configuration->Function of configuration

Parameters


This parameter indicates the function and purpose of the dedicated measurement

parameters. For the downlink AMR dynamic rate adjustment based on D-TCP, it

should be set to 7: Event A Report Parameters for TCP in AMR or 8: Event B

Report Parameters for TCP in AMR.

4.4.2.3 Dedicated Measurement Type

OMC Path



Profile->Node B Dedicated Measurement Configuration->Dedicated Measurement Type


This parameter indicates the type of the dedicated measurement to be executed by the

Node B. For the downlink AMR dynamic rate adjustment based on D-TCP, it should be

set to 2: Transmitted Code Power.

4.4.2.4 Measurement Filter Coefficient

OMC Path





Profile->Node B Dedicated Measurement Configuration->Measurement Filter Coefficient


This parameter indicates that how to filter a measurement value before a measurement

event is evaluated and reported. Smooth filtration is performed in accordance with the

formula "F (n) = (1-a)* F (n-1) + a*M (n)".

The variables in the formula are defined as follows:

F (n): the latest measurement result filtered.

F( n-1): the previous measurement result filtered.

M (n): the latest measurement result received from physical layer measurements.

a = (1/2)^ (k/2), where k is the filtration factor. If k is set to 0, layer-3 filtration is not

performed.

During the initialization, when the measurement result is received from the physical layer

for the first time, F (0) is set to M (1).

4.4.2.5 Report Characteristics

OMC Path



Profile->Node B Dedicated Measurement Configuration->Report Characteristics


This parameter indicates the reporting characteristics of measurement results.

Measurement results can be reported on demand, periodically or by triggering various

events. For the downlink AMR dynamic rate adjustment based on D-TCP, it should be

set to 3: Event A or 4: Event B.



4.4.2.6 Measurement Threshold of Event A/B for Transmitted Code Power

OMC Path



Profile->Node B Dedicated Measurement Configuration->Measurement Threshold

of Event A/B for Transmitted Code Power


This parameter indicates the power offset of the DPCH maximum DL power, which

defines the threshold that shall trigger event A or B for transmitted carrier power

measurement.

4.4.2.7 Measurement Change Time/Measurement Hysteresis Time

OMC Path



Profile->Node B Dedicated Measurement Configuration->Measurement Change

Time/Measurement Hysteresis Time


For event A/B/E/F, this parameter is the measurement hysteresis time which means the

lasting time for triggering the measurement reporting when the reporting conditions are

met.

For event C/D, this parameter is the changing time which indicates the variable of

increase/decrease for the measurement entity within the specified time in event C/D.

4.4.2.8 Choice Report Periodicity Scale

OMC Path





Profile->Node B Dedicated Measurement Configuration->Choice Report Periodicity

Scale


This parameter indicates the time unit of the cycle during which the Node B reports

measurement results.

4.4.2.9 Report Period

OMC Path



Profile->Node B Dedicated Measurement Configuration->Report Periodicity Value


This parameter indicates the report period. It is used in conjunction with RptPrdUnit to

determine the interval at which the Node B sends measurement reports.

4.4.2.10 DPCH Maximum DL Power

OMC Path


Configuration->Service Function->Power Control Profile Related to Service->Power

Control Related to Service->Power Control Related to Service and Diversity

Mode->DPCH Maximum DL Power


Configuration->Service Function->Power Control Related to Service for White List

->DPCH Maximum DL Power


It represents the maximum permissible downlink DPCH transmitted power. The greater

this value is, the higher the maximum permissible downlink transmitted power is. It is

related to the service sub-class.



4.4.2.11 Event A Counter Threshold for PS on DL DCH or DL AMR Decreasing Rate

on D-TCP

OMC Path

Path: Managed Element ->UMTS Logical Function Configuration->Global Information

Configuration->Dynamic Radio Bearer Control Information Profi->Dynamic Radio Bearer

Control Information->Event A Counter Threshold for PS on DL DCH or DL AMR

Decreasing Rate on D-TCP


This parameter indicates the

zte umts amr-nb & amr-wb feature guide_v8.5_201312.pdf

Documents