Beruflich Dokumente
Kultur Dokumente
Guide
WCDMA RAN
Feature
Date
2012-5-11
Author
Huang He
Reviewer
Lu Li
Revision History
Modified
the
name
and
path
of
the
parameters.
Added the new feature of Initial AMR Rate
V8.0
2012-11-23
Huang He
Xia Lei
V8.5
2013-11-26
Huang He
Cai Yaofang
Xia Lei
TABLE OF CONTENTS
1
2
2.1
2.2
2.3
2.4
2.5
Overview ............................................................................................................ 5
ZWF21-02-001 CS Conversational RAB for AMR-NB Speech ............................. 8
ZWF21-02-020 WB-AMR Speech Support ........................................................... 8
ZWF21-04-005 AMR Rate Controlling.................................................................. 8
ZWF21-04-014 Adaptive Radio Bearer Control .................................................... 9
ZWF21-06-002 TrFO ......................................................................................... 10
3
3.1
3.2
3.2.1
3.2.2
3.2.3
3.2.4
3.2.5
3.2.6
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.5
3.5.1
3.5.2
3.5.3
3.6
3.6.1
3.6.2
3.6.3
4
4.1
4.1.1
4.1.2
4.2
4.2.1
4.2.2
4.3
4.5.1
4.5.2
4.6
4.6.1
4.6.2
5
5.1
5.2
Glossary ........................................................................................................... 64
4.3.1
4.3.2
4.4
4.4.1
4.4.2
4.5
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
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]
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:
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
Total Number
Codec Mode
of Bits
Sub-flow 1
Sub-flow 2
Sub-flow 3
95
42
53
103
49
54
118
55
63
134
58
76
148
61
87
159
75
84
204
65
99
40
244
81
103
60
39
39
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 Codec
Total Number
Mode
of Bits
Sub-flow 1
Sub-flow 2
Sub-flow 3
AMR-WB_6.60
132
54
78
AMR-WB_8.85
177
64
113
AMR-WB_12.65
253
72
181
AMR-WB_14.25
285
72
213
AMR-WB_15.85
317
72
245
AMR-WB_18.25
365
72
293
AMR-WB_19.85
397
72
325
AMR-WB_23.05
461
72
389
AMR-WB_23.85
477
72
405
AMR-WB_SID
40
40(including
35 comfort
noise bits)
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
2.2
2.3
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
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.
10
Technical Descriptions
3.1
Figure 3-1
UE
Node B
Serving RNS
Serving
RNC
RANAP
CN
1. RAB Assignment
Request
RANAP
[Establishment]
Select L1, L2 and Iu Data
Transport Bearer parameters
2. ALCAP Iu Data
Transport Bearer Setup
Not required towards PS
domain
NBAP
NBAP
NBAP
NBAP
DCH-FP
6. Downlink Synchronisation
DCH-FP
7. Uplink Synchronisation
DCH-FP
NBAP
DCH-FP
NBAP
RRC
Apply new transport format set
RRC
RRC
RANAP
RANAP
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:
11
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
Codec_Type
Name
CoID (Codec
Identification)
0000.0101
UMTS
Adaptive
UMTS AMR
Adaptive
UMTS AMR 2
Adaptive
UMTS AMR-WB
Multi-Rate
0000.0110
UMTS
Multi-Rate 2
0000.1010
UMTS
Allocation/Retention Priority
User Plane Mode, set to support mode for predefined SDU sizes for AMR
services
12
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.
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).
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.
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.
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.
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.
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.
The NBAP message Radio Link Reconfiguration Commit is sent from the SRNC to
the Node B.
13
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
3.2.1
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.
If the value of UP Mode Versions in the RAB ASSIGNMENT REQUEST message is set
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.
If the value of UP Mode Versions in the RAB ASSIGNMENT REQUEST message is set
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
14
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
3.2.2
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.
15
3.2.4
3.2.5
3.2.6
3.3
3.3.1
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.
16
(14.25
kbps),
amrWbMode4UseTag
(15.85
kbps),
amrWbMode5UseTag
(18.25
kbps),
amrWbMode6UseTag
(19.85
kbps),
If the value of UP Mode Versions in the RAB ASSIGNMENT REQUEST message is set
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
17
3.3.2
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
3.3.5
3.4
3.4.1
18
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:
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.
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,
19
ZTE has not yet implemented SRB5-based uplink AMR-NB and AMR-WB rate
adjustment.
3.4.2
3.4.2.1
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
20
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
maximum output power of
3
+24
4
+21
the UE (dBm)
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
3.4.2.1.2
Parameter name
UAmrEvtTPUeInt.measRptTrMod
UAmrEvtTPUeInt.meaEvtId
UAmrEvtTPUeInt.trigTime
maximum
(Power in dBm)
UAmrEvtTPUeInt.txPowerThres
Filter coefficient
UAmrEvtTPUeInt.filterCoeff
UE
TX
power
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.
21
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
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
22
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.
Parameter name
REQUEST
Dedicated Measurement Type
measFilterCoeff
Report Characteristics
rptType
23
3.4.2.2.2
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
24
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
3.4.4
3.5
25
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:
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.
26
3.5.1
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.
27
3.5.2
and 3.3.1.2
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
28
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:
29
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
30
Figure 3-2
O-MSC
T-MSC
Transit
Transit
MGW
O-MGW
T-MGW
Selected Codec = v
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
31
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
RNC/
CN
*
CN/
RNC
INITIALISATION
2)
((RFCI, SDU sizes[, IPTIs ])m )
INITIALISATION ACK
Transfer Of User Data
optional
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.
32
Figure 3-4
RNC/
CN
CN/
RNC
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.
33
4.1
4.1.1
Parameter List
No.
Abbreviate
Parameter name
amrNbMode0UseT
ag
2
amrNbMode1UseT
ag
3
amrNbMode2UseT
ag
4
amrNbMode3UseT
ag
5
amrNbMode4UseT
ag
6
amrNbMode5UseT
ag
7
amrNbMode6UseT
ag
8
amrNbMode7UseT
ag
9
interRatV1V2AmrC
ut
10
intraRatV1V2AmrC
ut
4.1.2
Parameter Configurations
4.1.2.1
OMC Path
34
Parameter Configuration
4.1.2.2
OMC Path
Parameter Configuration
4.1.2.3
OMC Path
Parameter Configuration
4.1.2.4
OMC Path
Parameter Configuration
35
1: used
4.1.2.5
OMC Path
Parameter Configuration
The use of the label AMR_NB 7.40k 0: not used
1: used
4.1.2.6
OMC Path
Parameter Configuration
4.1.2.7
OMC Path
Parameter Configuration
36
4.1.2.8
OMC Path
Parameter Configuration
4.1.2.9
OMC Path
Parameter Configuration
In the process of Iu UP initialization, the ZTE RNC controls whether to cut some of the
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
OMC Path
Parameter Configuration
In the process of Iu UP initialization, the ZTE RNC controls whether to cut some of the
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.
37
4.2
4.2.1
Parameter List
No.
Abbreviate
Parameter name
wAmrSupInd
amrWbMode0UseT
ag
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
12
intraRatV1V2AmrC
ut
4.2.2
Parameter Configurations
4.2.2.1
OMC Path
38
Parameter Configuration
This parameter indicates whether the RNC supports the AMR-WB voice services.
4.2.2.2
OMC Path
Parameter Configuration
4.2.2.3
OMC Path
Parameter Configuration
4.2.2.4
OMC Path
Parameter Configuration
0: not used
1: used
39
4.2.2.5
OMC Path
Parameter Configuration
0: not used
1: used
4.2.2.6
OMC Path
Parameter Configuration
0: not used
1: used
4.2.2.7
OMC Path
Parameter Configuration
0: not used
1: used
4.2.2.8
OMC Path
40
Parameter Configuration
0: not used
1: used
4.2.2.9
OMC Path
Parameter Configuration
0: not used
1: used
4.2.2.10
OMC Path
Parameter Configuration
0: not used
1: used
4.2.2.11
41
4.2.2.12
4.3
4.3.1
Parameter List
No.
Abbreviate
Parameter name
amrRncAdjust
refUUeIntMeasProf
ile
3
profileId
Profile Id
measRptTrMod
filterCoeff
Filter coefficient
measEvtNum
Maximum
Event
Number
of
UE
Internal
Measurement
7
meaEvtId
trigTime
Time to Trigger
txPowerThres
10
maxUlDpchPwr
4.3.2
Parameter Configurations
4.3.2.1
OMC Path
Parameter Configuration
42
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
OMC Path
Parameter Configuration
4.3.2.3
Profile Id
OMC Path
GUI:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter Configuration
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
OMC Path
Path:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
43
Parameter Configuration
This parameter indicates the RLC mode of the UE internal measurement report.
4.3.2.5
Filter Coefficient
OMC Path
Path:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter Configuration
This parameter indicates the filtering factor that UE performs the L3 filtering on the
measurement results of the internal measurement.
4.3.2.6
OMC Path
Path:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter Configuration
4.3.2.7
OMC Path
Path:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
44
Transmitted
Power
Event
Measurement
Configuration
for
AMR->UE
Internal
Parameter Configuration
4.3.2.8
Time to Trigger
OMC Path
Path:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter Configuration
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
OMC Path
Path:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter Configuration
4.3.2.10
OMC Path
Path1:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
45
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter Configuration
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
4.4.1
Parameter List
No.
Abbreviate
Parameter name
amrRncAdjust
nbDMCfgNote
dedMeasType
measFilterCoeff
rptType
Report Characteristics
evtAbTcpThrd
Measurement
Threshold
of
Event
A/B
for
evtAbcdefTime
Measurement
Change
Time/Measurement
Hysteresis Time
8
rptPrdUnit
rptPrd
Report Period
10
maxDlDpchPwr
11
dtcpEaThd
12
dtcpEbThd
46
4.4.2
Parameter Configurations
4.4.2.1
4.4.2.2
OMC Path
Path: Managed Element ->UMTS Logical Function Configuration->Service
Configuration->Measurement Configuration->Node B Dedicated Measurement
Profile->Node B Dedicated Measurement Configuration->Function of configuration
Parameters
Parameter Configuration
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
GUI:
OMC Path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->Node
Function
B
Configuration->Service
Dedicated
Measurement
Parameter Configuration
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
OMC Path
47
GUI:
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->Node
Function
B
Configuration->Service
Dedicated
Measurement
Parameter Configuration
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
GUI:
OMC Path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->Node
Function
B
Configuration->Service
Dedicated
Measurement
Parameter Configuration
48
4.4.2.6
OMC Path
Path: Managed Element ->UMTS Logical Function Configuration->Service
Configuration->Measurement Configuration->Node B Dedicated Measurement
Profile->Node B Dedicated Measurement Configuration->Measurement Threshold
of Event A/B for Transmitted Code Power
Parameter Configuration
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
OMC Path
Path:
Managed
Element
->UMTS
Logical
Configuration->Measurement
Configuration->Node
Profile->Node
Measurement
Dedicated
Function
B
Configuration->Service
Dedicated
Measurement
Configuration->Measurement
Change
Parameter Configuration
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
GUI:
OMC Path
Managed
Element
Configuration->Measurement
->UMTS
Logical
Configuration->Node
Function
B
Configuration->Service
Dedicated
Measurement
49
Parameter Configuration
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
GUI:
Managed
Element
->UMTS
Configuration->Measurement
Logical
Configuration->Node
Function
B
Configuration->Service
Dedicated
Measurement
Parameter Configuration
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
OMC Path
Path1:
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Managed
Element
->UMTS
Logical
Function
Configuration->Service
Parameter Configuration
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.
50
4.4.2.11
OMC Path
Parameter Configuration
This parameter indicates the event A counter threshold of consecutive DTCP reports. If
the times of dedicated transmitted code power event A reporting exceed the threshold
indicated by this parameter, downlink PS or AMR decreasing rate are triggered.
4.4.2.12
OMC Path
Parameter Configuration
This parameter indicates the event B counter threshold of consecutive D-TCP reports. If
the times of dedicated transmitted code power event B reporting exceed the threshold
indicated by this parameter, downlink AMR increasing rate is triggered or it is allowed
that downlink DCH increasing rate is triggered for the PS services based on the traffic
volume measurement report.
51
4.5
4.5.1
Parameter List
No.
Abbreviate
Parameter name
GresPara47
4.5.2
Parameter Configurations
4.5.2.1
OMC Path
Parameter Configuration
Bit6 of the parameter indicates the switch of forbidding AMR downgrade. When the
switch is on (GresPara47:bit6 = 1), the AMR downgrade command triggered by the
congestion control and load control is not allowed until the switch is off (GresPara47:bit6
= 0).
4.6
4.6.1
Parameter List
No.
Abbreviate
Parameter name
AmrBadCovSwh
BadCovEcN0
BadCovRscp
amrUlLdThrd
amrDlLdThrd
52
Decision
6
nAmrInitialRate
wAmrInitialRate
amrGbrResInd
interRatV1V2AmrC
ut
10
intraRatV1V2AmrC
ut
11
GresPara47
4.6.2
Parameter Configurations
4.6.2.1
OMC Path
Parameter Configuration
This parameter indicates whether to decrease the AMR initial data rate in case of bad
coverage.
4.6.2.2
OMC Path
Path:
Managed
Element->UMTS
Logical
Function
Configuration->UTRAN
Parameter Configuration
When the reported P-CPICH Ec/No is smaller or equal to the threshold, it indicates that
the UE is in a bad coverage area.
53
4.6.2.3
OMC Path
Path:
Managed
Element->UMTS
Logical
Function
Configuration->UTRAN
Parameter Configuration
When the reported P-CPICH RSCP is smaller or equal to the threshold, it indicates that
the UE is in a bad coverage area.
4.6.2.4
OMC Path
Path:
Managed
Element->UMTS
Logical
Function
Configuration->UTRAN
Cell->Extended Info of UTRAN Cell->Cell Uplink Load Threshold for AMR Data Rate
Decision
Parameter Configuration
This parameter is relative to the cell uplink base noise and is set to decide the initial AMR
data rate. When the cell effective uplink load is larger than this threshold, the new
narrowband AMR will be set up with the data rate of nAmrInitialRate or GBR, and the
new wideband AMR will be set up with the data rate of wAmrInitialRate or GBR.
Otherwise, the new narrowband AMR will be set up with the maximum data rate of the
narrowband AMR, and the new wideband AMR will be set up with the maximum data rate
of the wideband AMR.
4.6.2.5
OMC Path
Path:
Managed
Element->UMTS
Logical
Function
Configuration->UTRAN
Cell->Extended Info of UTRAN Cell->Cell Downlink Load Threshold for AMR Data Rate
Decision
Parameter Configuration
54
This parameter is relative to the cell maximum transmitted power and is set to decide the
initial AMR data rate. When the cell effective downlink load is larger than this threshold,
the new narrowband AMR will be set up with the data rate of nAmrInitialRate or GBR,
and the new wideband AMR will be set up with the data rate of wAmrInitialRate or GBR.
Otherwise, the new narrowband AMR will be set up with the maximum data rate of the
narrowband AMR, and the new wideband AMR will be set up with the maximum data rate
of the wideband AMR.
4.6.2.6
OMC Path
Parameter Configuration
This parameter indicates the initial AMR data rate when the cell load is high. When the
cell effective downlink load is larger than amrDlLdThrd or the cell effective uplink load is
larger than amrUlLdThrd, the new narrowband AMR will be set up with the data rate of
nAmrInitialRate or GBR; otherwise, the new narrowband AMR will be set up with the
maximum data rate of the narrowband AMR.
4.6.2.7
OMC Path
Parameter Configuration
This parameter indicates the initial AMR data rate when the cell load is high. When the
cell effective downlink load is larger than amrDlLdThrd or the cell effective uplink load is
larger than amrUlLdThrd, the new wideband AMR will be set up with the data rate of
wAmrInitialRate or GBR; otherwise, the new wideband AMR will be set up with the
maximum data rate of the wideband AMR.
55
4.6.2.8
OMC Path
Parameter Configuration
This parameter indicates whether the GBR rate of AMR service assigned by the CN is
forcibly reserved in Iu UP V1 when it does not match the AMR rate configured by the
RNC.
4.6.2.9
4.6.2.10
4.6.2.11
OMC Path
Parameter Configuration
Bit 7 of the parameter indicates whether the AMR-NB or AMR-WB service rate is allowed
to be changed after the relocation. "0" indicates the rate changing after relocation is not
allowed. "1" indicates the rate changing after relocation is allowed. This parameter
should be set according to the UE compatibility. If it becomes mute for some UEs after
the relocation, the parameter should be set to not allow the AMR rate changing after
relocation.
56
5.1
Counter List
Counter No.
Description
C310030466
C310030467
C310030468
C310030469
C310030470
C310030471
C310030472
C310030473
C310030474
C310030475
C310030476
C310030477
C310030478
C310030479
C310030480
C310030481
C310030482
C310030638
C310030639
C310030640
C310030641
C310030642
C310030643
C310030644
C310030645
C310030646
C310030647
57
C310030648
C310030649
C310030650
C310030651
C310030652
C310030653
C310030654
C310063411
C310063412
C310063413
C310063414
C310063415
C310063416
C310063417
C310063418
C310063419
C310063420
C310063421
C310063422
C310063423
C310063424
C310063425
C310063426
C310063427
C310040001
C310040002
C310040003
C310040004
C310040005
C310040006
C310040007
C310040008
58
C310040009
C310040010
C310040011
C310040012
C310040013
C310040014
C310040015
C310040016
C310040017
C310040075
C310040076
C310040077
C310040078
C310040079
C310040080
C310040081
C310040082
C310040083
C310040084
C310040085
C310040086
C310040087
C310040088
C310040089
C310040090
C310040091
C310073296
C310073297
C310073298
C310073299
C310073300
C310073301
59
C310073302
C310073303
C310073304
C310073305
C310073306
C310073307
C310073308
C310073309
C310073310
C310073311
C310073312
C310073296
C310073297
C310073298
C310073299
C310073300
C310073301
C310073302
C310073303
C310073304
C310073305
C310073306
C310073307
C310073308
C310073309
C310073310
C310073311
C310073312
C310291935
C310291936
60
C310291937
C310291938
C310291939
C310291940
C310291941
C310291942
C310291943
C310373804
C310373805
C310373806
C310373807
C310373808
C310373809
C310373810
C310373811
C310373812
C310373827
C310373828
for CS,conversation:
WB-AMR 23.85
Number of
for CS,conversation:
WB-AMR 23.05
Number of
for CS,conversation:
WB-AMR 19.85
Number of
for CS,conversation:
WB-AMR 18.25
Number of
for CS,conversation:
WB-AMR 15.85
Number of
for CS,conversation:
WB-AMR 14.25
Number of
for CS,conversation:
WB-AMR 12.65
Number of
for CS,conversation:
WB-AMR 8.85
Number of
for CS,conversation:
WB-AMR 6.60
Number of
for
for
61
C310373829
C310373830
C310373831
C310373832
C310373833
C310373834
C310373835
Number of
for
for
for
for
for
for
for
C310231193
C310231194
C310231195
C310231196
C310231197
C310231198
C310231199
C310231200
C310231201
C310231239
C310231240
C310231241
C310231242
C310231243
C310231244
for
CS domain,WB-AMR 23.85
Number of RAB release by RNC receive Iu-release
for
CS domain,WB-AMR 23.05
Number of RAB release by RNC receive Iu-release
for
CS domain,WB-AMR 19.85
Number of RAB release by RNC receive Iu-release
for
CS domain,WB-AMR 18.25
Number of RAB release by RNC receive Iu-release
for
CS domain,WB-AMR 15.85
Number of RAB release by RNC receive Iu-release
for
CS domain,WB-AMR 14.25
62
C310231245
C310231246
C310231247
C310231216
C310231217
C310231218
C310231219
C310231220
C310231221
C310231222
C310231223
C310231224
C310231170
C310231171
C310231172
C310231173
C310231174
C310231175
for
CS domain,WB-AMR 12.65
Number of RAB release by RNC receive Iu-release
for
CS domain,WB-AMR 8.85
Number of RAB release by RNC receive Iu-release
for
CS domain,WB-AMR 6.60.
Number of RNC initiate release by Rab Release Request
for CS domain,WB-AMR 23.85
Number of RNC initiate release by Rab Release Request
for CS domain,WB-AMR 23.05,
Number of RNC initiate release by Rab Release Request
for CS domain,WB-AMR 19.85,
Number of RNC initiate release by Rab Release Request
for CS domain,WB-AMR 18.25,
Number of RNC initiate release by Rab Release Request
for CS domain,WB-AMR 15.85,
Number of RNC initiate release by Rab Release Request
for CS domain,WB-AMR 14.25,
Number of RNC initiate release by Rab Release Request
for CS domain,WB-AMR 12.65,
Number of RNC initiate release by Rab Release Request
for CS domain,WB-AMR 8.85,
Number of RNC initiate release by Rab Release Request
for CS domain,WB-AMR 6.60.
Number Of RAB release for UTRAN Abnormal Reason for
CS domain,WB-AMR 23.85
Number Of RAB release for UTRAN Abnormal Reason for
CS domain,WB-AMR 23.05,
Number Of RAB release for UTRAN Abnormal Reason for
CS domain,WB-AMR 19.85,
Number Of RAB release for UTRAN Abnormal Reason for
CS domain,WB-AMR 18.25,
Number Of RAB release for UTRAN Abnormal Reason for
CS domain,WB-AMR 15.85,
Number Of RAB release for UTRAN Abnormal Reason for
CS domain,WB-AMR 14.25,
63
C310231176
C310231177
C310231178
5.2
Alarm List
This feature has no related alarm.
Glossary
A
AMR
Adaptive Multi-Rate
AMRC
AMR-NB
AMR-WB
C
CN
Core Network
D
D-TCP
I
IAM
IuUP
Iu User Plane
64
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
65
SID
SRNC
Serving RNC
T
TC
Transcoder
TCP
TFC
Transport
TFO
T-MSC
TrFO
TX
Transmit
Format Combination
U
UMTS
66