Professional Documents
Culture Documents
WCDMA RAN
Feature Description
Date
Author
Approved By
V2.5
2009-1-20
Zhang jing
Guo tian
V3.0
2009-2-27
Zhang jing
Guo tian
V3.1
2009-5-14
Huang He
Guo tian
Remarks
TABLE OF CONTENTS
1
2
2.1
2.1.1
2.1.2
2.1.3
2.1.4
Overview ..................................................................................................................... 1
Function Introduction ................................................................................................... 1
ZWF21-02-001 CS AMR Voice and Session Service Bearer ..................................... 3
ZWF21-02-020 AMR-WB Voice Service ..................................................................... 3
ZWF21-04-005 Dynamic AMR Adaptation .................................................................. 3
ZWF21-06-002 TrFO Support ..................................................................................... 4
3
3.1
3.1.1
3.1.2
3.2
3.2.1
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.4
3.4.1
3.4.2
3.4.3
Technical Description................................................................................................ 5
CS AMR Voice and Session Service Bearer............................................................... 5
Implementation Mechanism of ZTE CS AMR Voice and Session Service Bearer
Function ....................................................................................................................... 5
Signaling Flow of AMR Service ................................................................................... 6
AMR-WB Voice Service............................................................................................... 7
Implementation Mechanism of ZTE AMR-WB Functions ............................................ 7
Dynamic AMR Adaptation ........................................................................................... 9
Classification of Dynamic AMR Adaptation ................................................................. 9
Dynamic AMR Adaptation Based on Single-Link Transmission Power .................... 10
Dynamic Adjustment Triggered by Resource Congestion ........................................ 13
Dynamic Adjustment Triggered by Load ................................................................... 13
TrFO Support............................................................................................................. 13
OoBTC Outband Codec Control................................................................................ 14
IuUP Initialization ....................................................................................................... 15
IuUP Rate Control...................................................................................................... 16
4
4.1
4.1.1
5
5.1
5.2
Glossary .................................................................................................................... 24
II
Table 1
Table 2
Table 3
III
Functional Attribute
System version: [RNC V3.07.310, OMMR V3.17.310, Node B V4.00.200, OMMB
V4.00.200]
Attribute: [Optional]
NEs involved:
UE
NodeB
RNC
MSCS
MGW
SGSN
GGSN
HLR
Note:
*-: No NE is involved.
*: An NE is involved.
Dependency: [None]
Mutual exclusion: [None]
Remarks: [None]
Overview
2.1
Function Introduction
The present 3GPP employs narrowband AMR (AMR-NB) and wideband AMR (AMRWB). For the AMR-NB, the speech channel bandwidth is limited to 3.7 MHz, and the
sampling frequency is 8,000 Hz. For the AMR-WB, the speech channel bandwidth is up
to 7 MHz, and the sampling frequency is up to 16,000 Hz. The AMR-WB has better
speech quality than the AMR-NB, although the two modes have the same frame length
of 20ms.
AMR is introduced into the 3G system based on the following considerations:
By means of the AMR Control (AMRC), voice rate can be reduced to improve voice
quality. In addition, system load can be effectively lightened. In the case of certain
radio load, if users want to obtain the optimal subjective feeling of voice quality, the
most suitable AMR is not the maximum rate, but a suitable medium rate. By
weighing load, the AMRC can achieve the following goals:
The AMRC can reduce an AMR when load is heavy. This lightens system load
and improves voice quality.
The AMRC can increase an AMR when load is light. In this way, QoS is greatly
improved.
When uplink coverage is limited, AMR can be reduced to effectively widen uplink
coverage. In initial WCDMA network construction, both uplink coverage and
downlink capacity are limited; therefore, it is especially important to widen uplink
coverage.
The Adaptive Multi-Rate (AMR) is also called the AMR-NB (Narrowband). This service
has three service RBs, and can provide eight speech rates and two mute rates, as
shown in Table 1 :
Table 1
AMR
Codec Mode
Total Number
of Bits
Subflow 1
Subflow 2
Subflow 3
Codec Mode
95
42
53
AMR_4.75
103
49
54
AMR_5.15
118
55
63
AMR_5.90
134
58
76
AMR_6.70
148
61
87
AMR_7.40
159
75
84
AMR_7.95
204
65
99
40
AMR_10.20
244
81
103
60
AMR_12.20
AMR SID
39
39
AMR_SID
GSM-EFR SID
43
43
GSM-EFR SID
AMR-WB
Codec Mode
Total Number
of Bits
Subflow 1
Subflow 2
Subflow 3
Codec Mode
1.75
40
40
AMR-WB_SID*
6.60
132
54
78
AMR-WB_6.60
8.85
177
64
113
AMR-WB_8.85
AMR-WB
Codec Mode
Total Number
of Bits
Subflow 1
Subflow 2
Subflow 3
Codec Mode
12.65
253
72
181
AMR-WB_12.65
14.25
285
72
213
AMR-WB_14.25
15.85
317
72
245
AMR-WB_15.85
18.25
365
72
293
AMR-WB_18.25
19.85
397
72
325
AMR-WB_19.85
23.05
461
72
389
AMR-WB_23.05
23.85
477
72
405
AMR-WB_23.85
2.1.1
2.1.2
2.1.3
decreases. Even when the power is increased to even a certain limit value, QoS
requirements of service can not be satisfied.
ZTE RNC equipment can monitor the uplink transmission power of UE in a UE internal
measurement report or the downlink transmission power of a Node B dedicated
measurement report base station. When the uplink or downlink transmission power rises
to a certain threshold, the RNC will automatically adjust this user's AMR to reduce the
power necessary 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 transmission 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
other users' feeling and system performance are not affected.
In addition, when a cell evaluated by means of downlink transmission power and uplink
interference has high downlink load and uplink load, ZTE RNC equipment can lighten
the cell load by reducing the AMR of some low-priority users, so as to accommodate
more users.
The actual AMR 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 lowrate 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 (4.75Kbps) instead of the highest AMR
(12.2Kbps) is used. When the lowest AMR is used, a cell will accommodate twice as
many users as those when the highest AMR is used.
2.1.4
Technical Description
3.1
3.1.1
3.1.1.1
Mobility of AMR-NB
Function description: This function supports soft handover, hard handover, and
relocation of AMR-NB service, and handover between 2G and 3G.
Modification of AMR-NB
Function description: This function does not support the modification of AMR-NB
service initiated by the RNC; it supports the modification of AMR-NB service
initiated by the CN. At present, the main scenarios for the CN to initiate modification
to the AMR-WB include the TFO or TrFO conditions satisfied after performance of
handover, call forwarding, and intelligent service. The CN initiates the modification
of AMR-NB.
3.1.2
N o de B
S e rv i ng R NS
S er vin g
R NC
CN
1 . R A B A s sig nme n t
Re q u e st
R AN A P
R ANAP
[E s ta blis h m ent]
S e le c t L1 , L2 and Iu D a ta
T ra n sp o rt Be a r e r p a ra me t er s
2 . A L C A P I u D a ta
T ran s po r t Be a r e r S etu p
N ot r e qu ir ed to wa rd s PS
d o m a in
NB AP
N B AP
[D C H A d d itio n ]
4 . R a d io L in k R e c o nf igu r a tio n R e a d y
N BA P
NB AP
5. A LC A P Iu b D a ta Tr a ns p or t B e are r S etu p
D C H- F P
6. D o w nl ink S yn ch r on is atio n
D C H -F P
7 . Up li nk S y nc h r on is a tio n
D C H- F P
NB AP
D C H- F P
8 . R ad io Li nk R e co n fi gu ra t ion C om mit
N B AP
9 . D C C H : R a d io B e ar e r S e tup
RR C
RRC
A pp ly n e w tr an s po r t fo r ma t se t
RR C
1 0. D C C H : R ad io B e ar e r S e tu p C o mp le te
RRC
R AN A P
1 1. R A B A ss ign me n t
R e s po n se
R ANAP
Figure 1
CN initiates establishment of the radio access bearer with RANAP message Radio
Access Bearer Assignment Request. Parameters: Radio Access Bearer
parameters, User Plane Mode, Transport Address, Iu Transport Association.
SRNC initiates set-up of Iu Data Transport bearer using 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 towards PS domain).
SRNC requests its Node B to prepare establishment of DCH to carry the radio
access bearer (Radio Link Reconfiguration Prepare). Parameters: Transport
Format Set, Transport Format Combination Set, Power control information.
Node B allocates resources and notifies SRNC that the preparation is ready (Radio
Link Reconfiguration Ready). Parameters: Transport layer addressing information
(AAL2 address, AAL2 Binding Id) for Iub Data Transport Bearer.
SRNC initiates the setup of Iub Data Transport Bearer using ALCAP protocol. This
request contains the AAL2 Binding Identity to bind the Iub Data Transport Bearer to
DCH.
The Node B and SRNC establish synchronism for the Iub and Iur Data Transport
Bearer by means of exchange of the appropriate DCH Frame Protocol frames
Downlink Synchronization.
The Node B and SRNC establish synchronism for the Iub and Iur Data Transport
Bearer by means of exchange of the appropriate DCH Frame Protocol frames
Uplink Synchronization.
NBAP message Radio Link Reconfiguration Commit is sent from SRNC to Node
B.
RRC message Radio Access Bearer Setup is sent by SRNC to UE. Parameters:
Transport Format Set, Transport Format Combination Set.
3.2
3.2.1
3.2.1.1
database, with the AMR-WB service added, needs to save all AMR-WB rate
configuration combinations. According to the maximum AMR-WB rate in the
message assigned by the CN, the RNC searches for corresponding configuration
information from the database.
Note: The AMR-WB supports the voice bandwidth 50Hz-7kHz (the AMR-NB
supports the voice bandwidth 200Hz-3.4kHz); therefore, it has better voice quality
than the AMR-NB. Among the rates (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) 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 3GPP.
Mobility of AMR-WB
Function description: 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.
Modification of AMR-WB
The RNC is not supported to initiate modification to the AMR-WB service, while the
CN is supported to initiate the modification to 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 modification to the AMR-WB include the TFO or TrFO conditions satisfied
after performance of handover, call forwarding, and intelligent service.
Function description: Like the AMR-NB control policy, this function supports the
dynamic rate adjustment for the AMR-WB service triggered by link level, resource
congestion, and load control. This function uses the present parameters without
new load control parameter added. If the rate adjustment threshold is met, the
uplink rate is controlled by the RNC through the TFC Control, and the CN downlink
rate is controlled by the RNC through the Iuup reverse rate control frame.
3.3
3.3.1
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-WB rate adjustment.
3.3.2
3.3.2.1
When the uplink transmission power reported by UE is lower than the threshold
AMR_6B2 (invariably configured as 60% of the maximum transmission power
MaxUlDpchPwr of uplink DPCH), the AMR 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. If UE does not report any measurement result or
the reported uplink transmission power is lower than the threshold AMR_6A2
(invariably configured as 70% of the maximum uplink transmission power of UE)
after AMR increase, we can concluded that the current transmission power is still
relatively low. If the current uplink AMR is not the maximum rate and the uplink load
of the system is neither overloaded nor congested, the AMR should be further
increased level by level until the uplink AMR is increased to the maximum rate or
the uplink transmission power reported by UE exceeds the threshold AMR_6A2. If
uplink overload or resource congestion occurs during the increase of the AMR, it is
necessary to stop increasing the AMR. If the uplink transmission power reported by
UE exceeds the threshold AMR_6A2, the AMR increase will be terminated.
10
In order to avoid Ping-Pang AMR rate adjustment and the bad user experience due
to over frequent AMR rate adjustment, ZTE RNC restricts the two consective AMR
rates adjustment of the same direction by the parameter RevEvtDetectIme.
Figure 2
100ms)
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 local end 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 local end 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 the
maximum uplink rate allowed by the current local end according to the uplink load state
of the current cell and the single-link UE transmission power measurement report, and
then returns this rate in the rate control response command to the peer end. At the same
time, the RNC sends to the UE the TFC control command, requiring adjustment of the
UE uplink rate to a smaller one of the maximum uplink AMR available with the local end
and the maximum uplink AMR stated in the rate control command sent to the RNC from
the CN.
3.3.2.2
When the special downlink transmission power reported by NodeB exceeds the
threshold AMR_E1 (invariably configured as 90% of the maximum downlink
transmission power (MaxDlDpchPwr) of AMR service), the downlink AMR should be
reduced by one level if the current downlink AMR is not the minimum rate. If the
special downlink transmission power reported periodically (The period is invariably
configured as four seconds) by NodeB after the downlink AMR reduction still
exceeds the threshold AMR_E1, we can concluded that the current transmission
11
power is still relatively high. And the downlink AMR should be further reduced to the
minimum rate, or the special downlink transmission power reported by NodeB is
reduced to a value lower than AMR_E2 (invariably configured as 80% of the
maximum transmission power (MaxDlDpchPwr) of downlink DPCH of AMR-WB
service). If the special downlink transmission power reported by NodeB is reduced
to a value lower than the threshold AMR_E2, the AMR reduction should be stopped.
When the special downlink transmission power reported by NodeB is lower than the
threshold AMR_F1 (invariably configured as 60% of the maximum transmission
power (MaxDlDpchPwr) of downlink DPCH of AMR service), 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. If the
special downlink transmission power reported periodically (The period is invariably
configured as four seconds) by NodeB after the rate increase is still ultra-lower than
the threshold AMR_F1, we can concluded that the current transmission power is
still relatively low. If the current downlink AMR is not the maximum rate and the
downlink load of the system is neither overloaded nor congested, the downlink AMR
should be further increased level by level until the downlink AMR rises to its
maximum or the special downlink transmission power reported by NodeB is higher
than the threshold AMR_F2 (invariably configured as 70% of the maximum
downlink transmission power (MaxDlDpchPwr) of AMR service). If downlink
overload or resource congestion occurs during increase of the AMR rate, it is
necessary to stop increasing the AMR rate. If the special downlink transmission
power reported by NodeB has exceeded the threshold AMR_F2, the downlink AMR
increase should be stopped.
In order to avoid Ping-Pang AMR rate adjustment and the bad user experience due
to over frequent AMR rate adjustment, ZTE RNC restricts the two consective AMR
rates adjustment of the same direction by the parameter RevEvtDetectIme.
Figure 3
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 end. Therefore, the downlink AMR-WB rate adjustment algorithm has
the following changes in comparison with the TrFO connection mode:
12
When the local end 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-end RNC. The returned rate control
response command contains the maximum uplink rate available with the peer end.
The peer end UE sends data at the smaller rate between the maximum uplink rate
supported by the peer end and the target rate required by the local end, so as to
complete downlink rate adjustment for the local end.
When the uplink rate of the peer end is decreased, the downlink rate of the local
end will be decreased accordingly.
When the uplink rate of the peer end is increased, the downlink rate of the local end will
be increased accordingly, resulting in change of the cell downlink load and the singlelink downlink D-TCP. The RNC should determine whether to decrease the increasing
downlink rate according to the cell downlink load and the single-link 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
end, so as to control the downlink rate of the Iu port.
3.3.3
3.3.4
3.4
TrFO Support
At the R99 stage, voice at the CN CS employs 64kbit/s PCM encoding based on TDM
bearer. Therefore, the R99 MSC must have the voice TC function. But voice
encoding/decoding is apt to 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 node of a call connection. For example, for a call between UMTS UE and
a fixed telephone, the TrFO connection only exists between UMTS UE and a core
network. The core network and RNC in the TrFO connection must support the IuUP V2.
13
Otherwise, no TrFO connection can be established. ZTE supports the IuUP V1 and
IuUP V2. The RNC will make a choice according to CN RAB assignment parameters.
The TrFO is implemented by employing the outband signaling encoding/decoding
control function (OoBTC). It is applicable to the calls between mobile networks and
those between a mobile network and an external network. When the same voice
encoding/decoding type is used between both call parties or between one call party and
a node in the call connection, the TrFO can transparently transmit compressed voice,
which improves voice quality and saves transmission bandwidth.
The node on both sides with a TrFO connection successfully established between them
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 nonTrFO 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 voice
quality;
The insertion position should save transmission bandwidth, that is, it should prolong
the connection which uses compressed voice encoding data for transmission.
For a UTRAN, its IuUP initialization, reverse initialization, IuUP rate control, and IuUP
reverse rate control are related to the TrFO process.
3.4.1
14
O-MSC
T-MSC
Transit
Transit
MGW
O-MGW
T-MGW
Selected Codec = v
Selected Codec = v
Bearer Established
Figure 4
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.4.2
IuUP Initialization
IuUP initialization serves to define the mapping relationship (used at the data
transmission stage) between the RNC and CN on both sides of IuUP, including RAB
sub-flow combination, RFCIs, and SDU size of 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. Thus, the initialization frame will only be used to negotiate about IuUP
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 IuUP reverse initialization. IuUP
initialization is shown in Figure 5.
15
RNC/
CN
*
CN/
RNC
INITIALISATION
2)
((RFCI, SDU sizes[, IPTIs ])m)
INITIALISATION ACK
Transfer Of User Data
Figure 5
optional
IuUP Initialization
In the RFCI set determined during IuUP 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 IuUP rate
control after IuUP initialization. The rate greater than the guaranteed rate is called a
controllable rate. The rate lower than the guaranteed rate cannot be modified.
3.4.3
RNC/
CN
CN/
RNC
RATE CONTROL
(RFCI indicators)
RATE CONTROL ACK
(RFCI indicators)
Figure 6
Note: The rate control frame describes the use limit of an "RFC set", which is called
"RFC limit set" in the following parts.
16
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 IuUP 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 TrFO. For example, in SRNS relocation, the CN first performs 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 IuUP 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 rate control.
Compared with the encoding/decoding type negotiation before initialization, the IuUP
rate control is in-band rate control.
4.1
Parameter List
Id
Abbreviated
Parameter name
AmrRncAdjust
MaxUlDpchPwr
MaxDlDpchPwr
AmrNbMode0UseTag
AmrNbMode1UseTag
AmrNbMode2UseTag
AmrNbMode3UseTag
AmrNbMode4UseTag
AmrNbMode5UseTag
10
AmrNbMode6UseTag
11
AmrNbMode7UseTag
12
AmrWbMode0UseTag
13
AmrWbMode1UseTag
14
AmrWbMode2UseTag
15
AmrWbMode3UseTag
16
AmrWbMode4UseTag
17
17
AmrWbMode5UseTag
18
AmrWbMode6UseTag
19
AmrWbMode7UseTag
20
AmrWbMode8UseTag
RevEvtDetectIme
WAMRSUPIND
21
22
4.1.1
4.1.1.1
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage dialog box -> RNC Radio Resource
Management label -> AMR Rate Adjustment Switch for RNC
Parameter Configuration
When the value of this parameter is "Closed", AMR dynamic rate adjustment will not
be triggered due to UE internal measurement and NodeB special measurement;
when the value of this parameter is "Open", AMR dynamic rate adjustment will be
triggered due to the above-mentioned measurement. When this parameter is closed,
AMR voice quality remains unchanged in any case; when this parameter is opened,
AMR voice quality may slightly degrade according to different scenarios, but system
capacity can be increased accordingly.
4.1.1.2
OMC Path
View -> Configuration Management -> Rnc Radio Resource Management->Modify
Advanced Parameter -> Power Control Related to Service and Diversity Mode
Parameter Configuration
Background configuration value. The greater this value is, the higher the maximum
permissible uplink transmission power.
4.1.1.3
OMC Path
View -> Configuration Management ->Rnc Radio Resource Management->Modify
Advanced Parameter ->Power Control Related to Service and Diversity Mode
18
Parameter Configuration
It represents the maximum permissible downlink DPCH transmission power. It is
related to service sub-class.
4.1.1.4
AmrNbMode0UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_NB 4.75k Use Tag
Parameter Configuration
AMR_NB 4.75k using label
0: not using
1: using
4.1.1.5
AmrNbMode1UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_NB 5.15k Use Tag
Parameter Configuration
AMR_NB 5.15k using label
0: not using
1: using
4.1.1.6
AmrNbMode2UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_NB 5.90k Use Tag
Parameter Configuration
AMR_NB 5.90k using label
0: not using
1: using
4.1.1.7
AmrNbMode3UseTag
OMC Path
19
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_NB 6.70k Use Tag
Parameter Configuration
AMR_NB 6.70k using label
0: not using
1: using
4.1.1.8
AmrNbMode4UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_NB 7.40k Use Tag
Parameter Configuration
AMR_NB 7.40k using label
0: not using
1: using
4.1.1.9
AmrNbMode5UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_NB 7.95k Use Tag
Parameter Configuration
AMR_NB 7.95k using label
0: not using
1: using
4.1.1.10
AmrNbMode6UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_NB 10.2k Use Tag
Parameter Configuration
AMR_NB 10.2k using label
0: not using
1: using
20
4.1.1.11
AmrNbMode7UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_NB 12.2k Use Tag
Parameter Configuration
AMR_NB 12.2k using label
0: not using
1: using
4.1.1.12
AmrWbMode0UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_WB 6.60k Use Tag
Parameter Configuration
AMR_WB 6.60k using label
0: not using
1: using
4.1.1.13
AmrWbMode1UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_WB 8.85k Use Tag
Parameter Configuration
AMR_WB 8.85k using label
0: not using
1: using
4.1.1.14
AmrWbMode2UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_WB 12.65k Use Tag
Parameter Configuration
AMR_WB 12.65k using label
0: not using
21
1: using
4.1.1.15
AmrWbMode3UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_WB 14.25k Use Tag
Parameter Configuration
AMR_WB 14.25k using label
0:not using
1: using
4.1.1.16
AmrWbMode4UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_WB 15.85k Use Tag
Parameter Configuration
AMR_WB 15.85k using label
0: not using
1: using
4.1.1.17
AmrWbMode5UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_WB 18.25k Use Tag
Parameter Configuration
AMR_WB 18.25k using label
0: not using
1: using
4.1.1.18
AmrWbMode6UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_WB 19.85k Use Tag
Parameter Configuration
22
0: not using
1: using
4.1.1.19
AmrWbMode7UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_WB 23.05k Use Tag
Parameter Configuration
AMR_WB 23.05k using label
0: not using
1: using
4.1.1.20
AmrWbMode8UseTag
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> AMR_WB 23.85k Use Tag
Parameter Configuration
AMR_WB 23.85k using label
0: not using
1: using
4.1.1.21
RevEvtDetectIme
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> Advanced Parameter Manage -> RNC Radio Resource
Management -> Time Interval for Consecutive AMR Adjustment of Same Direction
Parameter Configuration
It is used to set the time interval of two consecutive rate of AMR in the same
direction.
4.1.1.22
WAMRSUPIND
OMC Path
View -> Configuration Management -> RNC NE -> RNC Radio Resource
Management -> RNC Configuration Supplement Parameters-> WB-AMR Speech
Support Indicator
23
Parameter Configuration
This parameter indicates whether support for WB-AMR voice services.
5
5.1
5.2
Description
C301140968
C301140969
C301140970
C301140971
C301140972
C301140973
C301140974
C301140975
Alarm List
No related alarm list.
Glossary
A
AMR
Adaptive Multi-Rate
AMRC
AMR-NB
AMR-WB
C
CN
Core Network
D
D-TCP
24
I
IAM
IuUP
Iu User Plane
M
MSC
N
NAS
Non-Access-Stratum
O
OoBTC
P
PCM
PSTN
Q
QoS
Quality of Service
O-MSC
R
RAB
RFC
RFCI
RL
Radio Link
RX
Receive
RNC
S
SCR
SDU
SID
SRNC
Serving RNC
25
TC
Transcoder
TCP
TFC
TFO
T-MSC
TrFO
TX
Transmit
U
UMTS
26