Professional Documents
Culture Documents
Feature Guide
WB-AMR Rate Control
TABLE OF CONTENTS
2 Overview ............................................................................................................ 6
2.1 Feature Introduction ............................................................................................. 6
2.1.1 ZWF21-02-020 WB-AMR Speech Support ........................................................... 8
2.1.2 ZWF21-04-005 AMR Rate Controlling.................................................................. 8
2.1.3 ZWF21-06-002 TrFO ........................................................................................... 9
2.2 License Control .................................................................................................. 10
2.3 Correlation With Other Features ........................................................................ 10
4 Parameters....................................................................................................... 30
4.1 ZWF21-02-020 WB-AMR Speech Support ......................................................... 30
4.2 ZWF21-04-005 AMR Rate Controlling................................................................ 34
4.2.1 Uplink Rate Adjustment Based on the UE Transmit Power ................................ 34
4.2.2 Downlink Rate Adjustment Based on the Dedicated Measurement of Node B
Transmit Power .................................................................................................. 37
4.2.3 Dynamic Adjustment Triggered by Load and Resource Congestion ................... 44
4.3 ZWF21-06-002 TrFO ......................................................................................... 45
7 Abbreviations .................................................................................................. 67
8 Reference Documents..................................................................................... 68
FIGURES
TABLES
1 Feature Attribute
RNC version: [ZXUR 9000 UMTS V4.15.10.20/ZXWR RNC V3.15.10.20]
Attribute: [Optional]
Node B √ None.
iTC - None.
MSC - None.
MGW - None.
SGSN - None.
GGSN - None.
2 Overview
The Adaptive Multi-Rate (AMR) codec provides a high-quality voice service with flexible
multi-rate to reach a balance between voice quality and system capability (network load).
Currently, 3GPP uses two formats: Narrowband Adaptive Multi-Rate (NB-AMR) and
Wideband Adaptive Multi-Rate (WB-AMR), and both of them use the same frame length
of 20 ms. For NB-AMR, the voice channel bandwidth is limited to 3.7 kHz and the
sampling frequency is 8,000 Hz. For WB-AMR, the voice channel bandwidth is 7 kHz and
the sampling frequency is 16,000 Hz. The voice quality of WB-AMR is higher than that of
NB-AMR. If WB-AMR is required, the UE must support it, and whether a UE supports
WB-AMR is indicated in the SETUP uplink direct transfer message from the UE.
AMR Control (AMRC) indicates adjusting AMR between different rates in WCDMA
systems. Through AMRC, voice rate can be reduced to improve voice quality and reduce
system load. AMRC can be used in the following scenarios:
Uplink coverage is limited and the AMR rate can be reduced to widen uplink
coverage.
When system load is light, AMRC can be used to increase the AMR rate. In this way,
QoS is greatly improved.
The WB-AMR service was introduced in 1999 to provide higher voice quality. The
WB-AMR service is applicable to both the 3G system and GSM systems.
The WB-AMR service has two service RAB sub-flows and can provide nine voice rates
and the Silence Descriptor. The WB-AMR codec modes related to UMTS_AMR are
shown in the following table.
WB-AMR_6.60 132 54 78 0
WB-AMR_SID 40 40(including 0 0
35 comfort
noise bits)
WB-AMR sub-flow 1 contains the most important information of voice information and
12-bit CRC protection must be added on the air interface. Sub-flow 2 contains less
important voice information and CRC protection is not added on the air interface.
Sub-flow 3 does not contain any bit and is designed to be compatible with the structure of
NB-AMR.
ZTE's RAN supports all the nine WB-AMR rates defined in 3GPP 26.201, including 23.85
kbps, 23.05 kbps, 19.85 kbps, 18.25 kbps, 15.85 kbps, 14.25 kbps, 12.65 kbps, 8.85
kbps, and 6.6 kbps. The WB-AMR SID 1.75 kbps is also supported.
When the CN delivers an RAB assignment request for WB-AMR establishment, ZTE's
RAN does not support the RAB negotiation between NB-AMR and WB-AMR. This
indicates that if WB-AMR cannot be established, the RNC does not initiate the RAB
modification process to establish NB-AMR.
The RAB parameters of ZTE's RAN, used to bear WB-AMR services, are configured in
accordance with 3GPP TS 34.108.
In a WCDMA system, the radio conditions between a UE and the base station always
change. When the UE is far from the base station or the radio conditions are poor, the
base station or the UE must have greater transmit power under the closed-loop power
control to guarantee the QoS of the AMR service. The increase of the power may result
in further deterioration of radio conditions. As a result, system capacity decreases and
the QoS requirements of the service cannot be met even when the power is increased to
the maximum value.
ZTE's RNC can monitor the uplink transmit power contained in the UE internal
measurement report or the downlink transmit power contained in the NodeB-dedicated
measurement report. When the uplink or downlink transmit power rises to a threshold,
the RNC automatically adjusts the UE's AMR rate to reduce the power required for the
service. This indicates that voice quality is reduced to retain calls. When the radio
conditions between a UE and the base station are good and the transmit power of the
base station or the UE decreases to a threshold, the AMR rate can be increased to
provide the UE with higher voice quality when the system is neither overloaded nor
congested.
In addition, when the downlink and uplink load of a cell is high in accordance with its
downlink transmit power and uplink interference, ZTE's RNC can lighten the cell load by
reducing the AMR rate of some UEs with low priorities so that more UEs can be
supported.
The RNC can only adjust the AMR rates belonging to the AMR code set configured by
the CN for UEs during call establishment. The voice quality when low-rate AMR coding is
used is lower than that when high-rate AMR coding is used but the capacity (number of
UEs) is higher and the coverage is wider.
WCDMA systems use AMR compressed voice coding. In the R99 phase, a TDM bearer
is used between CS core network devices, and 64 kbit/s PCM coding must be used for
voice. Voice Transcoder (TC) is an important function of the R99 MSC, converting the
AMR voice codes of mobile terminals into PCM codes and transmits them over the
network. The calls between mobile users require two voice code conversions
(AMR-PCM-AMR). Frequent encoding and decoding reduce voice quality.
Therefore, 3GPP introduced Tandem Free Operation (TFO) and Transcoder Free
Operation (TrFO) in the R4 protocol to avoid voice encoding and decoding. With these
two technologies, the transmission network bandwidth between core networks can be
saved. The differences between the technologies are as follows: TFO needs TC
resources. After a call is established, a direct connection is established between the TCs
of the calling and called MSCs through in-band signaling negotiation to bypass encoding
and decoding. TrFO does not need TC resources. This indicates that Out of Band
The TFO technology is used on core network devices without the RAN. The TrFO
technology requires that the RAN should support out-band voice encoding negotiation
and the processing related to the user plane.
ZTE's RAN supports the TrFO function and complies with 3GPP TS 23.153 and TS
25.415.
License Configured
Feature ID Feature Name Unit
Control Item NE
WB-AMR
WB-AMR Speech
ZWF21-02-020 Speech RNC RNC
Support
Support
1. Required Features
None.
None.
3. Affected Features
None.
3 Technical Description
The 3GPP specifications define nine voice rates and one SID for UMTS WB-AMR, and
the highest voice rate supported is 23.85 kbps.
ZTE's RNC determines the WB-AMR rate set according to the value of UP Mode
Versions in the RAB ASSIGNMENT REQUEST message.
In Iu UP Mode version 1 mode, ZTE's RNC uses the following parameters to indicate
whether the rates are supported on the RNC: ULogicalRnc.amrWbMode0UseTag (6.6
kbps), ULogicalRnc.amrWbMode1UseTag (8.85 kbps),
ULogicalRnc.amrWbMode2UseTag (12.65 kbps), ULogicalRnc.amrWbMode3UseTag
(14.25 kbps), ULogicalRnc.amrWbMode4UseTag (15.85 kbps),
ULogicalRnc.amrWbMode5UseTag (18.25 kbps), ULogicalRnc.amrWbMode6UseTag
(19.85 kbps), ULogicalRnc.amrNbMode7UseTag (23.05 kbps), and
ULogicalRnc.amrNbMode8UseTag (23.85 kbps). The RNC determines the available
rates for the voice service in accordance with the intersection of the configured rate set
and the MBR and GBR of AMR-WB in the assignment message of the CN.
WB-AMR supports the voice bandwidth 50 Hz-7 kHz (NB-AMR supports the voice
bandwidth 200 Hz-3.4 kHz). Therefore, WB-AMR provides higher voice quality than
NB-AMR. Among the nine rates supported by WB-AMR, 12.65 kbps is the lowest rate
that can achieve high-quality sound effect. The MOS values of 6.6 kbps, 8.85 kbps, and
12.65 kbps are apparently increased when the rates are improved. The MOS values of
12.65 kbps, 14.25 kbps, 15.85 kbps, 18.25 kbps, and 19.85 kbps are not apparently
increased when the rates are improved. Therefore, the rates of 12.65 kbps, 8.85 kbps,
and 6.6 kbps are recommended by the 3GPP.
ZTE's RNC can be used to determine whether the GBR should be contained in the
WB-AMR rate set.
When the value of UP Mode Versions in the RAB ASSIGNMENT REQUEST message
is 1 or the value of UP Mode Versions is 3 and ULogicalRnc.IntraRatV1V2AmrCut is set
to cut, the WB-AMR rates configured by the RNC may be different from the WB-AMR
rate set assigned by the CN in the RAB ASSIGNMENT REQUEST message. To avoid
the problem that the RNC does not support the GBR in the RAB ASSIGNMENT
REQUEST message, you can set ULogicalRnc.amrGbrResInd to determine that the
GBR in the RAB ASSIGNMENT REQUEST message must be contained in the
supported rate set.
If ULogicalRnc.amrGbrResInd is set to 1: True, the actual WB-AMR rate set contains the
intersection of the above two AMR rate sets and the GBR in the RAB ASSIGNMENT
REQUEST message.
ZTE's RNC supports the WB-AMR service and the combination of the WB-AMR and PS
services.
ZTE's RNC supports the soft handover, hard handover, and relocation of the WB-AMR
service, and the handover between the 2G and 3G systems.
The RNC supports the directed retry of the WB-AMR service during RAB assignment. If
the load of the cell where the UE resides is too heavy during RAB assignment, the UE is
directed to a 2G system. For details, refer to the ZTE UMTS Directed Retry to GSM
Feature Guide.
Due to UE compatibility problems, some UEs become mute if the WB-AMR service rate
is changed after inter-RNC soft handover or hard handover relocation. Therefore,
URncInfo.intraRlocAmrRtCtrl is used to control whether the WB-AMR service rate can be
changed after the relocation.
relocation, and the actual WB-AMR service rates before and after relocation are the
same.
The RNC supports RAB modification for the WB-AMR service that the CN initiates by
sending the RAB ASSIGNMENT REQUEST message. The CN initiates RAB
modification for the WB-AMR service when the TFO or TrFO conditions are satisfied after
handover, call forwarding, and intelligent services.
The following figure shows the establishment flow of the WB-AMR service in
synchronous mode.
UE Node B Serving CN
Serving RNS RNC
1. RAB Assignment
Request
RANAP RANAP
[Establishment]
2. ALCAP Iu Data
Transport Bearer Setup
Not required towards PS
domain
6. Downlink Synchronisation
DCH-FP DCH-FP
7. Uplink Synchronisation
DCH-FP DCH-FP
1 The CN initiates the establishment of a radio access bearer by sending the RANAP
message Radio Access Bearer Assignment Request. The important parameters
for the CS service are as follows:
Delivery Order, value: provide in-sequence SDU delivery (for the AMR
service)
SDU parameters, describing the three RAB sub-flows of the AMR service
Allocation/Retention Priority
User Plane Mode, value: support mode for predefined SDU sizes (for the
AMR service).
UP Mode Versions indicates the user plane version supported by the CN,
containing 16 bits. Each bit indicates a user plane version, and a maximum of
16 user plane versions can be displayed. The highest bit indicates version 16
and the lowest bit indicates version 1. For support mode for predefined SDU
sizes, version 1 and version 2 are defined in the current version (release 99).
2 The SRNC initiates the establishment of the Iu data transport bearer by sending the
ALCAP message. This message contains the AAL2 binding identity, which is used
to bind the Iu data transport bearer to the radio access bearer.
3 The SRNC requests its NodeB to prepare the establishment of DCH to support the
radio access bearer (Radio Link Reconfiguration Prepare). The parameters include
Transport Format Set, Transport Format Combination Set, and power control
information parameters.
4 The NodeB allocates resources and notifies the 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 the Iub data transport bearer.
5 The SRNC initiates the establishment of the Iub data transport bearer by sending
the ALCAP message. This message contains the AAL2 binding identity, which is
used to bind the Iub data transport bearer to DCH.
6 The NodeB and the SRNC use the Iub or Iur data transport bearer to exchange the
DCH frame protocol message Downlink Synchronization to synchronize the Iub or
Iur interface.
7 The NodeB and the SRNC use the Iub or Iur data transport bearer to exchange the
DCH frame protocol message Uplink Synchronization to synchronize the Iub or Iur
interface.
8 The NBAP message Radio Link Reconfiguration Commit is sent from the SRNC
to the NodeB.
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 The UE sends the RRC message Radio Access Bearer Setup Complete to the
SRNC.
11 The SRNC sends the RANAP message Radio Access Bearer Assignment
Response to the CN.
The RNC supports dynamic rate adjustment for the AMR service triggered by link-level
transmit power, resource congestion, and load control during calls. If the rate adjustment
threshold is reached, the uplink rate is controlled by the RNC through the TFC control
command, and the downlink rate is controlled by the RNC through the Iu UP reverse rate
control frame.
There are three types of AMR dynamic rate adjustment depending on the trigger
mechanisms:
Due to inner-loop power control, the uplink/downlink link-level transmit power vary with
the change of the radio conditions of the transmitting antennas of the UE and the NodeB.
When the radio conditions degrade, the RNC should reduce the WB-AMR rate to reduce
transmit power to avoid heavy uplink/downlink load of the cell. When the transmit power
of the WB-AMR link is low and the system load is light, the RNC can increase the
WB-AMR rate to maximize the utilization of system resources to provide users with better
voice quality.
Reduce the rate of the uplink/downlink AMR service to reduce uplink/downlink resource
congestion.
Initial WB-AMR rate adjustment triggered when the cell is overloaded or the UE is a
poorly covered area
When the cell is overloaded or the UE is in a poorly covered area, the initial and the
highest AMR service rates should be reduced to lighten cell load and improve link
performance. For details, refer to the ZTE UMTS Adaptive Radio Bearer Feature Guide.
For these three trigger mechanisms, ZTE's RNC can only adjust the rate of the WB-AMR
service in the range of WB-AMR rates.
The AMR rate adjustment in uplink is base on the UE internal measurement reports of
UE TxP (Transmit Power). There are two kinds of event, Event 6a and Event 6b.
UAmrEvtTPUeInt.meaEvtId defines the UE internal event identity.
Event 6a: when the UE TxP measurement value is greater than a certain absolute
threshold and this condition lasts for the duration TriggerTime6A, the Event 6a is
reported by the UE. TriggerTime6A is defined by the parameter
UAmrEvtTPUeInt.trigTime [0].
Event 6b: when the UE TxP measurement value is smaller than a certain absolute
threshold and this condition lasts for the duration TriggerTime6B, the Event 6b is
reported by the UE. TriggerTime6B is defined by the parameter
UAmrEvtTPUeInt.trigTime [1].
The parameters for 6a and 6b can be configured at cell level. The number of internal
measurement events is configured by UAmrEvtTPUeInt.measEvtNum. It can be set to
“2”, for Event 6a and 6b. To facilitate the description, it is assumed that 0 represents 6a
and 1 represents 6b.
If the uplink transmit power reported by the UE exceeds the threshold (AMR_6a)
and the current uplink WB-AMR rate is not the lowest rate, the WB-AMR rate level
must be reduced by one. After the uplink WB-AMR rate level is reduced, a new
measurement control command is sent to the UE.
If the uplink transmit power reported by the UE is lower than the threshold
(AMR_6b), the current uplink WB-AMR rate is not the highest rate, and the system
is neither overloaded nor congested with uplink load, the WB-AMR rate level must
be increased by one. After the uplink WB-AMR rate level is increased, a new
measurement control command is sent to the UE.
For TrFO connection mode, the following operations must be also performed:
If the target WB-AMR rate is smaller than or equal to the highest uplink rate of the Iu
interface, the rate can be increased. Otherwise, the uplink rate cannot be increased.
When the RNC receives the rate control command from the CN, the highest rate is the
uplink target rate required by the CN. The RNC determines whether the target rate can
be adjusted by the current RNC according to cell uplink load and the UE transmit power
measurement report. If the target rate can be adjusted by the RNC, the RNC returns the
rate control response command containing the rate to the peer end. At the same time,
the RNC sends the TFC control command to the UE, requiring that the UE uplink rate
should be adjusted to the target rate. If the target rate cannot be adjusted by the RNC,
the RNC sends a Rate Control NACK message to the CN.
The downlink WB-AMR rate adjustment is based on the D-TCP (Dedicated Transmitted
Code Power) measurement report from Node B. It indicates that the downlink Transmit
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 WB-AMR rate control is reported periodically and the period is
configured by UNbDedMeas.RptPrd. Whether the criterion for Event A or Event B is met
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 AMR_A for the duration TriggertimeA, the Event A is triggered.
When the criterion of Event A is met, the downlink Transmit Power for a certain UE
is considered to be in a high power status, and the downlink rate could be
decreased.
Event B: when the Node B D-TCP measurement value is smaller than a specific
absolute threshold AMR_B for the duration TriggertimeB , the Event B is triggered.
When the criterion of Event B is satisfied, the downlink Transmit Power for a certain
UE is considered to be in a low power status, and the downlink rate could be
increased.
Where
When the special downlink transmit power reported by the NodeB exceeds the
threshold (AMR_A) UDrbc.dtcpEaThd times consecutively and the current downlink
WB-AMR rate is not the lowest rate, the downlink WB-AMR rate level must be
reduced by one.
When the special downlink transmit power reported by the NodeB is lower than the
threshold (AMR_B) UDrbc.dtcpEbThd times consecutively, the current downlink
WB-AMR rate is not the highest rate, and the system is neither overloaded nor
congested with downlink load, the downlink WB-AMR rate level must be increased
by one.
For TrFO connection mode, the downlink rate depends on the downlink rate of the Iu
interface. In a mobile-to-mobile call, the downlink rate depends on the uplink rate of the
peer end. Therefore, the downlink WB-AMR rate adjustment algorithm is changed as
follows in comparison with the non-TrFO connection mode:
When the local end needs to adjust the downlink WB-AMR rate, the RNC sends the
adjusted target rate through the rate control command to the CN, and the CN sends
this rate through the rate control command to the peer RNC. The returned rate
control response command contains the highest uplink rate supported by the peer
end. The peer UE sends data at the smaller rate between the highest uplink rate
supported by the peer end and the target rate required by the local end. In this way,
the downlink rate of the local end is adjusted.
When the uplink rate of the peer end is reduced, the downlink rate of the local end is
reduced accordingly.
When the uplink rate of the peer end is increased, the downlink rate of the local end
is increased accordingly, resulting in the change of the downlink load of the cell and
the downlink D-TCP of the link. The RNC should determine whether to reduce the
increasing downlink rate according to the downlink load of the cell and the downlink
D-TCP measurement report. If the downlink rate must be reduced, the RNC sends
the rate control command to the CN, containing the highest rate supported by the
local end. In this way, the downlink rate of the Iu interface is controlled.
In case of uplink or downlink overload in a cell, the RNC must reduce the rates of AMR
services in accordance with their priorities.
When the cell is not overloaded and the WB-AMR services whose rates are reduced
meet the conditions described in section 3.3.2, the RNC increases their rates level by
level.
In case of uplink or downlink resource congestion, the RNC must reduce the rates of
AMR services in accordance with their priorities.
When uplink or downlink resources are not congested and the WB-AMR services whose
rates are reduced meet the conditions described in section 3.3.2, the RNC increases
their rates level by level.
In the R99 phase, 64 kbit/s PCM coding is used based on the TDM bearer in the CN CS
domain. Therefore, the R99 MSC must have the voice TC function. However, voice
quality may be reduced after encoding or decoding. The calls between mobile users
need dual voice encoding and decoding. If no codec is used, voice quality can be
improved and network bandwidth can be saved.
In the R4 phase, a TrFO connection can reduce the number of times that voice encoding
and decoding are performed. The TrFO connection can be established throughout the
end-to-end process or between the nodes of a call connection. For example, for a call
between a UMTS UE and a fixed telephone, the TrFO connection only exists between
the UMTS UE and the core network. The core network and the RNC in the TrFO
The nodes connected with a TrFO connection use the same common compressed voice
encoding type negotiated in the OoBTC phase. A codec must be inserted between a
TrFO connection and a non-TrFO connection to convert encoding types. The
implementation strategy of the core network ensures that the insertion position can meet
the following requirements:
The insertion position should reduce the number of times that TC (transcoder) is
used and improve voice quality;
The insertion position should save transmission bandwidth. This indicates that it
should prolong the connection that uses compressed voice encoding data for
transmission.
When a call is initiated, both call parties negotiate the codec to establish a TrFO
operation. The O-MSC sends an IAM message containing the supported codec type list
to a transmission network. The transmission network deletes the codec types that are not
supported from the list and sends it to a T-MSC. The T-MSC also deletes the codec
types that are not supported from the list and then selects an optimal common codec
type. The T-MSC returns the codec type to the transmission network and the O-MSC,
and notifies them of the selected codec type. In the meantime, the T-MSC returns the
codec type that the Terminating UE supports to the O-MSC and begins to establish a
bearer based on this codec. This flow is shown in the following figure.
Selected Codec = v
Selected Codec = v
Selected Codec = v, Available
List (v, x, z, )
Selected Codec = v
The encoding type that the UE supports is transparently transmitted to the RNC as
follows: Uplink Direct Transfer -> NAS Message -> Bearer Capacity, and then the RNC
transparently transmits the encoding type to the MSC server as follows: 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.3.2 Iu UP Initialization
The purpose of Iu UP initialization is to define the mapping relationship (used in the data
transmission phase) between the RNC and the CN on both sides of Iu UP, including RAB
sub-flow combination, RFCIs, and SDU size of the related RAB sub-flow.
In the R99 version, this initialization process can only be performed when the RNC
receives an RAB assignment, modification, or RNC relocation request. In the R4 version,
the CN can also perform this initialization process, which is called Iu UP reverse
initialization. The following figure shows Iu UP initialization.
RNC/ CN/
CN RNC
INITIALISATION
2)
* ((RFCI, SDU sizes[, IPTIs ])m)
INITIALISATION ACK
In the RFCI set determined during Iu UP initialization, the rate that corresponds to the
first RAB sub-flow combination is the highest rate in the initialization response direction
permitted by the local end when data transmission begins. The highest rate must be
higher than the guaranteed rate and SID rate. The highest rate can be modified during Iu
UP rate control after Iu UP initialization. The rates higher than the guaranteed rate are
called controllable rates, and the rates lower than the guaranteed rate cannot be
modified.
The purpose of Iu UP rate control is to notify the peer Iu UP protocol layer of the highest
rate at the Iu interface in the reverse direction of the rate control frame. In the R4 version,
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 when the SID rate and the RFC
are lower than the guaranteed rate because they cannot be prohibited.
RNC/ CN/
CN RNC
RATE CONTROL
(RFCI indicators)
Note: The rate control frame describes the limits of an RFC set, hereinafter called the
"RFC limit set".
In downlink direction, the RNC triggers the rate control frame, records the "RFC limit set"
(downlink direction), and monitors the operations of the CN. If the CN 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 through
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 the call to limit or open the
other party's uplink AMR level, or the CN initiates a rate adjustment flow according to the
TrFO. For example, during SRNS relocation, the CN performs reverse initialization first
after a new RNC sends relocation detection to the CN, and then the new RNC initiates a
process called immediate initialization. This aims at negotiating the highest rate for data
transmission between two Iu UP entities supporting TrFO.
The rate control initiated by the RNC is as follows: During the 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 rate control.
Compared with the encoding and decoding type negotiation before initialization, Iu UP
rate control is in-band rate control.
4 Parameters
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
0:Not
WB-AMR This parameter
upporte 0: Not
ULogicalRnc.w Speech indicates if RNC 1:Supp
d N/A Support
AmrSupInd Support supports WB-AMR orted
1:Supp ed
Indicator Speech
orted
This parameter
indicates whether the
RNC supports AMR-WB
ULogicalRnc.a 6.60 kbps in Iu UP 0:Not
AMR_WB
mrWbMode0U version 1. It is used in Used N/A Used 1: Used
6.60k Use Tag
seTag the user plane 1: Used
initialization process of
RAB establishment or
SRNS relocation.
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
8.85 kbps in Iu UP
version 1. It is used in
the user plane
initialization process of
RAB establishment or
SRNS relocation.
This parameter
indicates whether the
RNC supports AMR-WB
ULogicalRnc.a AMR_WB 12.65 kbps in Iu UP 0: Not
mrWbMode2U 12.65k Use version 1. It is used in Used N/A Used 1: Used
seTag Tag the user plane 1: Used
initialization process of
RAB establishment or
SRNS relocation.
This parameter
indicates whether the
RNC supports AMR-WB
ULogicalRnc.a AMR_WB 14.25 kbps in Iu UP 0:Not
Not 0:Not
mrWbMode3U 14.25k Use version 1. It is used in Used N/A
Used Used
seTag Tag the user plane 1: Used
initialization process of
RAB establishment or
SRNS relocation.
This parameter
indicates whether the
RNC supports AMR-WB
ULogicalRnc.a AMR_WB 15.85 kbps in Iu UP 0: Not
Not 0:Not
mrWbMode4U 15.85k Use version 1. It is used in Used N/A
Used Used
seTag Tag the user plane 1: Used
initialization process of
RAB establishment or
SRNS relocation.
This parameter
ULogicalRnc.a AMR_WB 0: Not
indicates whether the Not 0:Not
mrWbMode5U 18.25k Use Used N/A
RNC supports AMR-WB Used Used
seTag Tag 1: Used
18.25 kbps in Iu UP
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
version 1. It is used in
the user plane
initialization process of
RAB establishment or
SRNS relocation.
This parameter
indicates whether the
RNC supports AMR-WB
ULogicalRnc.a AMR_WB 19.85 kbps in Iu UP 0: Not
Not 0:Not
mrWbMode6U 19.85k Use version 1. It is used in Used N/A
Used Used
seTag Tag the user plane 1: Used
initialization process of
RAB establishment or
SRNS relocation.
This parameter
indicates whether the
RNC supports AMR-WB
ULogicalRnc.a AMR_WB 23.05 kbps in Iu UP 0: Not
Not 0:Not
mrWbMode7U 23.05k Use version 1. It is used in Used N/A
Used Used
seTag Tag the user plane 1: Used
initialization process of
RAB establishment or
SRNS relocation.
This parameter
indicates whether the
RNC supports AMR-WB
ULogicalRnc.a AMR_WB 23.85 kbps in Iu UP 0: Not
Not 0:Not
mrWbMode8U 23.85k Use version 1. It is used in Used N/A
Used Used
seTag Tag the user plane 1: Used
initialization process of
RAB establishment or
SRNS relocation.
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
mode, when the GBR
rate assigned by the CN
does not match the
AMR rate configured by
RNC.
0: AMR
Rate
The parameter is used Changi
to indicates whether ng is
narrowband or Allowed
0: AMR 0: AMR
wideband AMR service after
Rate Rate
rate is allowed to be Relocati
AMR Rate Changi Changi
changed after the on
URncInfo.intra Control Switch ng is ng is
relocation or not. "0" 1: AMR N/A
RlocAmrRtCtrl after Allowed Allowed
indicates rate changing Rate
Relocation after after
after relocation is not Changi
Relocat Relocat
allowed. while "1" ng is
ion ion
indicates rate changing Not
after relocation is Allowed
allowed. after
Relocati
on
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
Used UE
UUtranCellFD This parameter is the 0..6553
Internal
D.refUUeIntMe DN (Distinguish Name) 5, step N/A N/A N/A
Measurement
asProfile of UUeIntMeasProfile. 1
Profile
This parameter
0:
indicates the RLC mode
Acknow
of the UE internal
ledged
measurement report. If
Mode 0:Ackn 0:Ackn
the value is AM RLC,
UAmrEvtTPUe Measurement RLC owledg owledg
RNC can request UE for
Int.measRptTr Report 1: N/A ed ed
retransmission after
Mod Transfer Mode Unackn Mode Mode
receiving the error SDU
owledg RLC RLC
label (not continuous). If
ed
the value is UM RLC,
Mode
the retransmission is
RLC
not required. Usually,
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
report the results of the
important
measurements in AM
mode and those less
important in UM mode
(to reduce the traffic
volume of the
measurement report
and increase the
system capacity).
This parameter
(0, 1,
indicates the filtering
2, 3, 4,
factor that UE performs
UAmrEvtTPUe Filter 5, 6, 7,
the L3 filtering on the N/A 3 3
Int.filterCoeff Coefficient 8, 9, 11,
measurement results of
13, 15,
the internal
17, 19)
measurement.
This parameter
UE Internal
UAmrEvtTPUe indicates the UE [6a, 6b,
Measurement N/A [6a, 6b] [6a, 6b]
Int.meaEvtId internal measurement 6f, 6g]
Event Identity
event identity.
(0, 10,
20, 40,
60, 80,
This parameter
100,
indicates the period of
120,
time during which the
UAmrEvtTPUe 160, [1280, [1280,
Time to Trigger event condition has to ms
Int.trigTime 200, 1280] 1280]
be satisfied before
240,
sending a measurement
320,
report.
640,
1280,
2560,
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
5000)m
s
This parameter
(-50,
UAmrEvtTPUe UE Transmit indicates the UE
0)dB,
Int.txPowerThr Power Transmit Power dB [-1, -2] [-1, -2]
step1
es Threshold threshold in event
dB
6a/6b.
This parameter
indicates the maximum
DPCH uplink transmit
power allowed for a UE.
When uplink inner loop
power control is
performed, the transmit
power newly calculated
by a UE may be larger
than this parameter. In
this case, the UE can
only use this parameter
for transmitting signals.
Maximum This parameter is a
[33,33, [33,33,
Allowed Uplink nine-element array. (-50..33
USrvDivPc.ma 33,33,3 33,33,3
DPCH These elements are )dBm, dBm
xUlDpchPwr 3,33,33 3,33,33
Transmission used in different load step
,33,33] ,33,33]
Power conditions and user 1dBm
priorities. The
corresponding
relationships of the
elements and load
levels and user
priorities are as follows:
Element 1: low load,
gold medal user
Element 2: low load,
silver medal user
Element 3: low load,
bronze medal user
Element 4: medium
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
load, gold medal user
Element 5: medium
load, silver medal user
Element 6: medium
load, bronze user
Element 7: high load,
gold medal user
Element 8: high load,
silver medal user
Element 9: high load,
bronze medal user
Reco
Parameter Default mmen
GUI Name Parameter Description Value Range Unit
Name Value ded
Value
Reco
Parameter Default mmen
GUI Name Parameter Description Value Range Unit
Name Value ded
Value
0: Period
Report
Parameters for
TCP in Power
Balance
1: Period
Report
Parameters for
TCP in AMR or
DASF-PS or
7:
Handover
Event
Control
A
2: Event A
7: Event Report
Report
A Report Param
Parameters for
Paramet eters
TCP in
This parameter indicates ers for for
DASF-PS
the function, purpose TCP in TCP in
UNbDedM Function of 3: Event B
etc. of the dedicated AMR AMR
eas.nbDM Configuration Report N/A
measurement 8: Event 8:
CfgNote Parameters Parameters for
parameters indicated by B Report Event
TCP in
the configuration index. Paramet B
DASF-PS
ers for Report
4: Period
TCP in Param
Report
AMR eters
Parameters for
for
RTT in LCS
TCP in
5: Event E
AMR
Report
Parameters for
SIR Error in
Outer Loop
Power Control
6: Event F
Report
Parameters for
SIR Error in
Outer Loop
Reco
Parameter Default mmen
GUI Name Parameter Description Value Range Unit
Name Value ded
Value
Power Control
7: Event A
Report
Parameters for
TCP in AMR
8: Event B
Report
Parameters for
TCP in AMR
9: Event A
Report
Parameters for
TCP in
Handover
Control
10: Event B
Report
Parameters for
TCP in
Handover
Control
1: SIR Error 2:
This parameter indicates 2:
UNbDedM Dedicated 2: Transmitted Trans
the type of dedicated Transmit
eas.dedM Measurement Code Power N/A mitted
measurement to be ted Code
easType Type 5: Round Trip Code
executed by Node B Power
Time Power
Reco
Parameter Default mmen
GUI Name Parameter Description Value Range Unit
Name Value ded
Value
a*M(n)
The variables in the
formula are defined as
follows:
F(n) is the updated
filtered measurement
result
F(n-1) is the old filtered
measurement result
Mn is the latest received
measurement result from
physical layer
measurements
a = (1/2)^ (k/2) , where k
is the Measurement
Filter Coefficient. If k=1
there’s no filtering)
In order to initialise the
averaging filter, F(0) is
set to M(1) when the first
measurement result from
the physical layer
measurement is
received.
1: On Demand
This parameter indicates
2: Periodic
the report characteristics
3: Event A
UNbDedM Report of measurement results, 2:
4: Event B 2:
eas.rptTyp Characteristic which can be on N/A Period
5: Event C Periodic
e s demand, periodic or by ic
6: Event D
triggering all kinds of:
7: Event E
events.
8: Event F
Reco
Parameter Default mmen
GUI Name Parameter Description Value Range Unit
Name Value ded
Value
Code Power shall trigger event A, B
for transmitted carrier
power measurement.
In PS DRBC, this
threshold is related to
the service rate as
following:
Rate Level PS Service
Rate (R) Threshold of
Event A/B
Level 1 R<=
DlRateLevel[0]
EvtAbTcpThrd [0]
Level 2
DlRateLevel[0]<R<=
DlRateLevel[1]
EvtAbTcpThrd [1]
Level 3
R>DlRateLevel[1]
EvtAbTcpThrd [2]
Other case, the
threshold and service
rate independent, and
the threshold is
EvtAbTcpThrd [0].
Reco
Parameter Default mmen
GUI Name Parameter Description Value Range Unit
Name Value ded
Value
triggered.
For event C/D, this
parameter is change
time. and the change
time is the time the
measurement entity shall
rise on (in ms), in order
to trigger a measurement
report.
RptPrdUnit =1:
This parameter indicates (10..60000)ms,
UNbDedM the frequency of step 10ms
Report Period ms 1000 1000
eas.rptPrd measurement report RptPrdUnit =2:
transmitted by Node B. (1..60)min step
min
Reco
Parameter Default mmen
GUI Name Parameter Description Value Range Unit
Name Value ded
Value
Maximum DL Power.
This parameter is a
nine-element array.
These elements are
used in different load
conditions and user
priorities. The
corresponding
relationships of the
elements and load levels
and user priorities are as
follows:
Element 1: low load, gold
medal user
Element 2: low load,
silver medal user
Element 3: low load,
bronze medal user
Element 4: medium load,
gold medal user
Element 5: medium load,
silver medal user
Element 6: medium load,
bronze user
Element 7: high load,
gold medal user
Element 8: high load,
silver medal user
Element 9: high load,
bronze medal user
Reco
Parameter Default mmen
GUI Name Parameter Description Value Range Unit
Name Value ded
Value
Rate Based threshold, the speed of
on D-TCP downlink PS or AMR will
be reduced.
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
Recom
Parameter Value Default
GUI Name Parameter Description Unit mende
Name Range Value
d Value
Specifies the Amr cut
URncFunction. Inter-RAT decision when IuUP 1: cut
interRatV1V2A V1+V2 Amr version including 2: not N/A 1: cut 1: cut
mrCut Cut Decision V1+V2 in the inter-RAT cut
case
Counter ID Name
6 Engineering Guide
With this feature, users can make WB-AMR voice calls in the ZTE UMTS network.
Compared with NB-AMR, WB-AMR provides higher voice quality without using more
resources.
With this feature, ZTE's RNC can adjust the uplink and downlink WB-AMR rates based
on the UE uplink transmit power and NodeB downlink transmit power respectively, or
adjust AMR rates during resource congestion. This feature improves cell capacity and
user experience when radio link quality is reduced.
With this feature, Out of Band Transcoder Control (OoBTC) can be used during WB-AMR
service establishment to implement consistent voice encoding and decoding negotiation
between the UE and the network. In this way, the TC (Transcoder) is not necessary and
coded voice data is transmitted transparently between users. This improves voice quality
and saves transmission bandwidth between core networks.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > PLMN Relating Configuration > Logic RNC
Configuration and set WB-AMR Speech Support Indicator, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > PLMN Relating Configuration > Logic RNC
Configuration and set AMR_WB 6.60k Use Tag, AMR_WB 8.85k Use Tag, AMR_WB
12.65k Use Tag, AMR_WB 14.25k Use Tag, AMR_WB 15.85k Use Tag, AMR_WB
18.25.60k Use Tag, AMR_WB 19.85k Use Tag, AMR_WB 23.05k Use Tag, and
AMR_WB 23.85k Use Tag, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Extended Info of RNC and set AMR Rate Control
Switch after Relocation, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration and set Inter-RAT V1+V2 Amr Cut Decision and
Intra-RAT V1+V2 Amr Cut Decision, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > PLMN Relating Configuration > Logic RNC
Configuration and set AMR Rate Adjustment Switch for RNC, see the following
figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > UTRAN Cell and set Used UE Internal
Measurement Profile to default, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Measurement
Configuration > UE Internal Measurement Profile and set Profile ID to default, see
the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Measurement
Configuration > UE Internal Measurement Profile > UE Transmitted Power Event
Measurement Configuration for AMR and set Measurement Report Transfer Mode,
Filter Coefficient, Maximum Event Number of UE Internal Measurement, UE
Internal Measurement Event Identity, Time to Trigger, and UE Transmitted Power
Threshold, see the following figure.
In the configuration resource tree, select Modify Area > 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 and set Maximum Allowed
Uplink DPCH Transmission Power, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > PLMN Relating Configuration > Logic RNC
Configuration and set AMR Rate Adjustment Switch for RNC, see the following
figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Measurement
Configuration > NodeB Dedicated Measurement Profile and set Profile Id to default,
see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Measurement
Configuration > NodeB Dedicated Measurement Configuration and set Function of
Configuration Parameters, Dedicated Measurement Type, Measurement Filter
Coefficient, Report Characteristics, Measurement Threshold of Event A/B for
Transmitted Code Power, Measurement Change Time/Measurement Hysteresis
Time, Choice Report Periodicity Scale, and Report Period, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Service Configuration > Measurement
Configuration > NodeB Dedicated Measurement Configuration and set DPCH
Maximum DL Power to default, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Global Information Configuration > Dynamic
Radio Bearer Control Information Profile > Dynamic Radio Bearer Control
Information and set Event A Counter Threshold for PS on DL DCH or DL AMR
Decreasing Rate Based on D-TCP and Event B Counter Threshold for Restriction
PS Increasing Rate on DL DCH or Triggering DL AMR Increasing Rate Based on
D-TCP to default, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration > Global Information Configuration > Dynamic
Radio Bearer Control Information Profile > Dynamic Radio Bearer Control
Information and set Switch of Forbidding AMR Deceleration Triggered by
Congestion Control and Switch of Forbidding AMR Deceleration Triggered by
Overload Control to default, see the following figure.
In the configuration resource tree, select Modify Area > Managed Element > UMTS
Logical Function Configuration and set S Intra-RAT V1+V2 Amr Cut Decision and
Inter-RAT V1+V2 Amr Cut Decision, see the following figure.
Expected
The service is normal in the whole procedure.
Result
1. The initial and highest bit rate of the AMR voice service is 12.2
Expected
kbps.
Result
2. The AMR rate adaptation procedure is normal.
The same data can be found from the logs of UE1 and UE2. This
Expected
indicates that the data that UE1 has sent is transferred transparently to
Result
UE2 without being re-coded by the CN.
WB-AMR Speech
1 0:Off 0:Off
Support Indicator
None.
With this feature, users can make WB-AMR voice calls in the ZTE UMTS network.
Compared with NB-AMR, WB-AMR provides higher voice quality without using more
resources.
None.
None.
With this feature, ZTE's RNC can adjust the uplink and downlink WB-AMR rates based
on the UE uplink transmit power and NodeB downlink transmit power respectively, or
adjust AMR rates during resource congestion. This feature improves cell capacity and
user experience when radio link quality is reduced.
None.
With this feature, Out of Band Transcoder Control (OoBTC) can be used during WB-AMR
service establishment to implement consistent voice encoding and decoding negotiation
between the UE and the network. In this way, the TC (Transcoder) is not necessary and
coded voice data is transmitted transparently between users. This improves voice quality
and saves transmission bandwidth between core networks.
None.
7 Abbreviations
Abbreviation Full Name
UE User Equipment
TC Transcoder
8 Reference Documents
[1]ZXUR 9000 UMTS(V4.15.10.20)Radio Network Controller Radio Parameter
Reference