Professional Documents
Culture Documents
Rate Control Description (2008!07!30)
Rate Control Description (2008!07!30)
Rate Control Description (2008!07!30)
Issue 02
Date 2008-07-30
Website: http://www.huawei.com
Email: support@huawei.com
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Contents
4 DCCC Algorithm........................................................................................................................4-1
4.1 Rate Reallocation Based on Traffic Volume..................................................................................................4-1
4.1.1 Traffic Volume Measurement and Event Reporting .............................................................................4-1
4.1.2 UL Rate Reallocation Based on Traffic Volume ..................................................................................4-4
4.1.3 DL Rate Reallocation Based on Traffic Volume ..................................................................................4-8
4.1.4 Signaling Procedure of Rate Reallocation Based on Traffic Volume.................................................4-12
4.2 Rate Reallocation Based on Throughput .....................................................................................................4-14
4.2.1 Throughput Measurement and Event Reporting ................................................................................4-14
4.2.2 Rate Reallocation Action Based on Throughput ................................................................................4-17
Rate Control Change History provides information on the changes between different
document versions.
02(2008-07-30)
This is the document for the second commercial release of RAN10.0.
Compared with 01 (2008-05-30) of RAN10.0, issue 02 (2008-07-30) of RAN10.0
incorporates the changes described in the following table.
Feature The switch of rate reallocation based on The add parameters are listed
throughput is added. For detail, see 4.2 Rate
Event 4A threshold
z Traffic Measurement
Event 4B threshold
z Pending time after trigger
4A
z Pending time after trigger
4B
z Time to trigger 4A
z Time to trigger 4B
01(2008-05-30)
This is the document for the first commercial release of RAN10.0.
Compared with draft (2008-03-20) of RAN10.0, issue 01 (2008-05-30) of RAN10.0
incorporates the changes described in the following table.
of Traffic AMR
z Wait Timer for Uplink Rate Adjustment
of Traffic WAMR
z DL Measurement Reporting Period
EDCH
z Period Amount to trigger 4B on EDCH
EDCH
z Percent Of Ratio For 128Kbps
DCH
z UL measurement filter coefficient
Draft (2008-03-20)
This is a draft of the document for the first commercial release of RAN10.0.
Compared with issue 03 (2008-01-20) of RAN 6.1, this issue incorporates the changes
described in the following table.
Rate control triggers rate upsizing, rate downsizing, and handover for different services
according to the consumption of resources.
Rate control in the Wideband Code Division Multiple Access (WCDMA) system has two
types: rate control over Adaptive Multi Rate (AMR) services and rate control over Best Effort
(BE) services. Rate control herein is described in terms of the following algorithms:
z Adaptive Multi-Rate Control (AMRC) / AMRC-WB algorithms: They are implemented
by the RNC. They dynamically adjust the transport format based on the cell load, link
power, and Iub resource utilization, so as to achieve the balance between the system load,
link stability, Iub resources, and link QoS. The UL AMRC/AMRC-WB algorithm and
the DL AMRC/AMRC-WB algorithm work independently.
z Dynamic Channel Configuration Control (DCCC) algorithm: It is implemented by the
RNC. It controls the rate of BE services according to the traffic volume, throughput,
radio link quality, or congestion state. The UL DCCC algorithm and the DL DCCC
algorithm work independently.
z Link stability control algorithm: It is implemented by the RNC. It triggers rate
downsizing, inter-frequency handover, and inter-RAT handover to guarantee the stability
of links and QoS of services. The rate downsizing of this algorithm is the power-based
rate downsizing in AMRC/AMRC-WB and DCCC.
Impact
AMRC/AMRC-WB Impact on System Performance
z The AMRC/AMRC-WB algorithm can be used to steer the UL permitted highest
AMR/AMR-WB speech codec mode down according to the UE transmit power. In this
way, the UL coverage is expanded.
z The AMRC/AMRC-WB algorithm can be used to steer the permitted highest
AMR/AMR-WB speech codec mode down according to the downlink DPCH transmit
code power or UE transmit power. In this way, the system capacity is increased in terms
of the maximum number of UEs that the system can process.
z The AMRC/AMRC-WB algorithm can be used to choose a proper AMR/AMR-WB
speech codec mode according to the quality of the transmission environment. In this way,
the speech quality is ensured.
DCCC Impact on System Performance
z Every time rate adjustment occurs, there is interactive signaling on the Uu and Iub
interfaces. The impact on the system performance has relations with the user profile
mode and the user traffic mode. In general, there is little impact of DCCC on the system
performance.
Link Stability Control Algorithm Impact on System Performance
z Link stability control algorithm has no impact on system performance.
Rate Control Impact on Other Features
z Rate control has no impact on other features.
√ √ √ – √ – – –
NOTE:
z –: not involved
z √: involved
UE = User Equipment, RNC = Radio Network Controller, MSC = Mobile Service Switching Center,
MGW = Media Gateway, SGSN = Serving GPRS Support Node, GGSN = Gateway GPRS Support
Node, HLR = Home Location Register
3 AMRC/AMRC-WB Algorithms
Term Definition
Guaranteed bit rate The GBR is the minimum bit rate for the RNC to adjust. It is
(GBR) contained in the RAB assignment message that the CN sends to the
RNC.
The supported The set consists of all the AMR speech codec modes that can be used
AMR speech codec for the service transport. The set is decided by the RNC according to
mode set the mode set specified by the RAB assignment.
The controllable The set consists of the AMR speech codec modes that are contained
AMR speech codec in the supported AMR speech codec mode set and are equal to or
mode set larger than the GBR. The modes in this set can be selected by the
AMRC/AMRC-WB algorithm.
For example:
The supported AMR speech codec mode set is {NO DATA, SID, 4.75 kbit/s, 7.95 kbit/s,
12.2 kbit/s}.
Then, the controllable AMR speech codec mode set is {4.75 kbit/s, 7.95 kbit/s, 12.2 kbit/s},
if the GBR is 4.75 kbit/s.
This chapter describes two important algorithms: AMRC and AMRC-WB, the following lists
the contents of this chapter.
z Initial Access Rate of AMRC/AMRC-WB
z AMRC/AMRC-WB Algorithm Based on Uplink Stability
z AMRC/AMRC-WB Algorithm Based on Downlink Stability
z AMRC/AMRC-WB Algorithm Based on Basic Congestion
z AMRC/AMRC-WB Algorithm for TFO/TrFO
The UE-priority-oriented maximum rate refers to the Max mode of narrowband AMRC for golden
users, Max mode of narrowband AMRC for silver users, and Max mode of narrowband AMRC for
copper users parameters. For detailed information about the definitions and description of the user
priority, see “Priorities Involved in Load Control”.
If the UE-priority-oriented maximum rate is lower than the GBR in the RAB assignment message, then
the initial access rate is the GBR.
This note applies to all the initial access rates mentioned thereafter.
The DL code-resource-saving algorithm is available for the RNC. This algorithm allows a single speech
service which has a DL maximum rate of 7.95 kbit/s or lower to use 256 as the Spreading Factor (SF)
for the downlink. When the DL code-resource-saving algorithm is disabled, SF128 is used for the
downlink.
z For downlink, the initial access rate is the maximum permitted bit rate at the start of the
communication phase.
The UE-priority-oriented maximum rate refers to the Max mode of wideband AMRC for golden users,
Max mode of wideband AMRC for silver users, and Max mode of wideband AMRC for copper
users parameters. For detailed information about the definitions and description of the user priority, see
“Priorities Involved in Load Control” in Load Control.
If the UE-priority-oriented maximum rate is lower than the GBR in the RAB assignment message, then
the initial access rate is the GBR.
This note applies to all the initial access rates mentioned thereafter.
− Higher than or equal to the GBR in the RAB assignment message sent from the
CN
− Lower than or equal to the UE-priority-oriented maximum rate that is set on the
RNC LMT
Then, if Rmax is higher than the GBR, the downlink controllable mode set is {GBR in
the RAB assignment message, Rmax}. Otherwise, the downlink controllable mode set
contains only one rate, which is {GBR in the RAB assignment message}.
UL Measurement
In the uplink, the measurement quantity is the transmit power of the UE.
The Delta_6a1, Delta_6b1, Delta_6a2, and Delta_6b2 in Figure 3-1 refer to the following
relative values respectively:
z The relative value between the TX power threshold 6A1 and the Max UL TX power of
conversational service
z The relative value between the TX power threshold 6B1 and the Max UL TX power of
conversational service
z The relative value between the TX power threshold 6A2 and the Max UL TX power of
conversational service
z The relative value between the TX power threshold 6B2 and the Max UL TX power of
conversational service
Therefore, Delta_6a1, Delta_6b1, Delta_6a2, and Delta_6b2 are relative measurement
thresholds.
A set of relative measurement thresholds for all AMR/AMR-WB services is as follows:
z Uplink 6A1 event relative threshold
z Uplink 6B1 event relative threshold
z Uplink 6A2 event relative threshold
z Uplink 6B2 event relative threshold
The values of the preceding relative thresholds are listed in Table 3-2.
BE(32kbit/s) 1 1 5 5
BE(64kbit/s) 1 1 3 3
BE(128kbit/s) 1 1 6 6
BE(144kbit/s) 1 1 6 6
BE(256kbit/s) 1 1 3 3
AMR 2 2 10 10
WAMR 2 2 10 10
VP 2 2 - -
The measurement thresholds, that is, the absolute measurement thresholds, are calculated on
the basis of the following formula:
z Measurement threshold 6A1 = Max UL TX power of conversational service – Uplink
6A1 event relative threshold
z Measurement threshold 6B1 = Max UL TX power of conversational service – Uplink
6B1 event relative threshold
Event Reporting
After establishing an AMR/AMR-WB speech service, the UTRAN sends the UE a
MEASUREMENT CONTROL message to configure
z the TX power threshold of 6A1, 6B1, 6A2, 6B2, and 6D.
z the trigger time of 6A1, 6B1, 6A2, 6B2, and 6D.
For AMR/AMR-WB service, the trigger time of 6A1, 6B1, 6A2 and 6B2 is set to 320 ms,
and the trigger time of 6D is set to 640 ms.
Then, the UE measures the TX power in real time, filters the measurement results, and makes
decisions as follows:
z If the UE TX power has been higher than TX power threshold 6A1 for a period longer
than 320 ms and the TRIGGERED_6A1_EVENT variable is FALSE, event 6A1 is
triggered and the TRIGGERED_6A1_EVENT variable is set to TRUE.
z If the TRIGGERED_6A1_EVENT variable is TRUE and the UE TX power is lower than
TX power threshold 6A1, the TRIGGERED_6A1_EVENT variable is set to FALSE.
z If the UE TX power has been lower than TX power threshold 6B1 for a period longer
than 320 ms and the TRIGGERED_6B1_EVENT variable is FALSE, event 6B1 is
triggered and the TRIGGERED_6B1_EVENT variable is set to TRUE.
z If the TRIGGERED_6B1_EVENT variable is TRUE and the UE TX power is higher than
TX power threshold 6B1, the TRIGGERED_6B1_EVENT variable is set to FALSE.
z If the UE TX power has been lower than TX power threshold 6B2 for a period longer
than 320 ms and the TRIGGERED_6B2_EVENT variable is FALSE, event 6B2 is
triggered and the TRIGGERED_6B2_EVENT variable is set to TRUE.
z If the TRIGGERED_6B2_EVENT variable is TRUE and the UE TX power is higher than
TX power threshold 6B2, the TRIGGERED_6B2_EVENT variable is set to FALSE.
z If the UE TX power has been higher than TX power threshold 6A2 for a period longer
than 320 ms and the TRIGGERED_6A2_EVENT variable is FALSE, event 6A2 is
triggered and the TRIGGERED_6A2_EVENT variable is set to TRUE.
z If the TRIGGERED_6A2_EVENT variable is TRUE and the UE TX power is lower than
TX power threshold 6A2, the TRIGGERED_6A2_EVENT variable is set to FALSE.
z If the UE Tx power equals the maximum UE TX power for 240 ms and the variable
TRIGGERED_6D_EVENT is set to FALSE, event 6D is triggered and the variable
TRIGGERED_6D_EVENT to TRUE.
z If the variable TRIGGERED_6D_EVENT is set to TRUE and if the UE Tx power is less
than the maximum UE TX power, set the variable TRIGGERED_6D_EVENT to
FALSE.
Each time a measurement event is triggered, the UE sends the measurement report to the
UTRAN (as shown in Figure 3-1) and the UL AMRC/AMRC-WB algorithm makes a
corresponding adjustment according to the reported measurement event. For detailed
information about the signaling procedure, see 3.2.3 UL AMRC/AMRC-WB Signaling
Procedure.
− If the event 6B1 or 6B2 is received before the UL AMRC/AMRC-WB timer expires,
the adjustment is completed. Then, the UL AMRC/AMRC-WB algorithm stops the
UL AMRC/AMRC-WB timer and ends the adjustment.
− If no event 6B1 or 6B2 is received before the UL AMRC/AMRC-WB timer expires
and if the current rate is higher than GBR, the adjustment is not complete. The UL
AMRC/AMRC-WB algorithm decreases the UL permitted highest AMR/AMR-WB
speech codec mode by one more level and restarts the UL AMRC/AMRC-WB timer.
If the rate before the decrease is GBR, handover can be performed. For details or rate
decrease fails, refer to 5.1 Link Stability Control Algorithms for AMR/AMR-WB
Speech Services.
z When an event 6B2 is received and UL load resource is not in congestion state, the UL
AMRC/AMRC-WB algorithm increases the UL permitted highest AMR/AMR-WB
speech codec mode by one level and starts the UL AMRC/AMRC-WB timer whose
length is specified by Wait Timer for Uplink Rate Adjustment of Traffic
AMR/WAMR. If the rate before the increase is the maximum one in the controllable
mode set, no increase will be performed, and the UL AMRC/AMRC-WB timer does not
start.
− If the event 6A2 or 6A1 is received before the UL AMRC/AMRC-WB timer expires,
the adjustment is completed. Then, the UL AMRC/AMRC-WB algorithm stops the
UL AMRC/AMRC-WB timer and ends the adjustment.
− If no event 6A2 or 6A1 is received before the UL AMRC/AMRC-WB timer expires
and if UL load resource is still not in congestion state, the adjustment is not complete.
The UL AMRC/AMRC-WB algorithm increases the UL permitted highest
AMR/AMR-WB speech codec mode by one more level and restarts the UL
AMRC/AMRC-WB timer. If the rate before the increase is the maximum one in the
controllable mode set, no increase will be performed, and the UL AMRC/AMRC-WB
timer does not restart.
In current version, there are two rates in the controllable mode set at most.
6A1 ↓ Started
6B1 → Stopped
6A2 → Stopped
6B2 ↑ Started
↓: depicts decrease in the permitted highest AMR/AMR-WB speech codec mode.
↑: depicts increase in the permitted highest AMR/AMR-WB speech codec mode.
→: depicts no change on the current permitted highest AMR/AMR-WB speech codec
mode.
If event 6B1 is reported when the permitted highest AMR/AMR-WB speech codec mode is
↑, then no adjustment related to event 6B1 is made.
If event 6A2 is reported when the permitted highest AMR/AMR-WB speech codec mode is
↓, then no adjustment related to event 6A2 is made.
If the event 6A2 or 6B1 is received when the UL AMRC/AMRC-WB timer is not started, the
AMRC/AMRC-WB algorithm regards it as a normal variation of UE TX power and does not make any
adjustment.
As shown in Figure 3-4, the UE reports events 6A1, 6B1, 6A2, 6B2 or 6D by sending a
MEASUREMENT REPORT message.
As shown in Figure 3-5, the RNC adjusts the UL permitted highest AMR/AMR-WB speech
codec mode by sending a TRANSPORT FORMAT COMBINATION CONTROL message
and adjusts the UL bandwidth by sending a QAAL2 MODIFY message.
DL Measurement
In the downlink, the measurement quantity is the DPDCH transmit (TX) power.
In Figure 3-6:
z For event E1, the average TX power on the DPDCH is higher than the TX power
threshold E1.
z For event E2, the average TX power on the DPDCH is lower than the TX power
threshold E2.
z For event F1, the average TX power on the DPDCH is lower than the TX power
threshold F1.
z For event F2, the average TX power on the DPDCH is higher than the TX power
threshold F2.
The Delta_E1, Delta_E2, Delta_F1, and Delta_F2 in Figure 3-6 refer to the following relative
values respectively:
z The relative value between the TX power threshold E1 and the RL Max DL TX power
z The relative value between the TX power threshold E2 and the RL Max DL TX power
z The relative value between the TX power threshold F1 and the RL Max DL TX power
z The relative value between the TX power threshold F2 and the RL Max DL TX power
Therefore, Delta_E1, Delta_E2, Delta_F1, and Delta_F2 are relative measurement thresholds.
A set of relative measurement thresholds for all AMR/AMR-WB services are configured. The
set includes the following parameters:
z DL E1 event relative threshold
z DL E2 event relative threshold
z DL F1 event relative threshold
z DL F2 event relative threshold
The measurement thresholds, that is, the absolute measurement thresholds, are calculated on
the basis of the following formula:
z Measurement threshold E1 = RL Max DL TX power – DL E1 event relative threshold
z Measurement threshold E2 = RL Max DL TX power – DL E2 event relative threshold
z Measurement threshold F1 = RL Max DL TX power – DL F1 event relative threshold
z Measurement threshold F2 = RL Max DL TX power – DL F2 event relative threshold
Event Reporting
After establishing a service, the UTRAN sends a request to the NodeB for periodical
measurements of DL Transmitted Code Power (TCP) in the pilot field of DPCCH, and NodeB
sends the TCP measurement reports to the RNC every 480 ms.
The RNC processes the measurement report as follows:
1. The RNC converts DL TCP in the pilot field of DPCCH to the average TX power of the
DPDCH.
2. The RNC compares the average DPDCH TX power with the measurement thresholds E1,
E2, F1 and F2 to determine the type of event.
AMRC/AMRC-WB status to Rate-Up. If the rate before the increase is the maximum
one in the controllable mode set, no increase will be performed.
z When the average DPDCH power is between the thresholds E2 and F2, the current DL
AMR/AMR-WB speech rate is appropriate. The DL AMRC/AMRC-WB algorithm
makes no adjustment and sets the AMRC/AMRC-WB status to Normal.
z When the average DPDCH power is lower than or equal to the threshold E1 and higher
than the threshold E2, the DL AMRC/AMRC-WB algorithm makes adjustments
according to the AMRC/AMRC-WB status.
− If the AMRC/AMRC-WB status is Rate-Down, the DL AMRC/AMRC-WB
algorithm decreases the DL permitted highest AMR/AMR-WB speech codec mode
by one level. If the rate before the decrease is GBR or rate decrease fails, handover
can be performed. For detailed information, see 5.1 Link Stability Control Algorithms
for AMR/AMR-WB Speech Services.
− If the AMRC/AMRC-WB status is Normal or Rate-Up, the DL AMRC/AMRC-WB
algorithm makes no adjustment.
z When the average DPDCH power is lower than the threshold F2 and higher than or equal
to the threshold F1, the DL AMRC/AMRC-WB algorithm makes adjustments according
to the AMRC/AMRC-WB status and DL load status.
− If the AMRC/AMRC-WB status is Rate-Up and the DL load is not in congestion state,
the DL AMRC/AMRC-WB algorithm increases the DL permitted highest
AMR/AMR-WB speech codec mode by one more level. If the rate before the
increase is the maximum one in the controllable mode set, no increase will be
performed.
− If the AMRC/AMRC-WB status is Normal or Rate-Down, the DL
AMRC/AMRC-WB algorithm makes no adjustment.
DPDCH Mode Change when Mode Change when Mode Change when
Power AMRC/AMRC-WB AMRC/AMRC-WB AMRC/AMRC-WB
Status is Normal Status is Rate_Down Status is Rate_Up
DPDCH ↓ ↓ ↓
power > the
TX power
threshold E1
The TX → ↓ →
power
threshold E2
< DPDCH
power ≤ the
TX power
threshold E1
The TX → → →
power
threshold F2
≤ DPDCH
power ≤ the
TX power
threshold E2
DPDCH Mode Change when Mode Change when Mode Change when
Power AMRC/AMRC-WB AMRC/AMRC-WB AMRC/AMRC-WB
Status is Normal Status is Rate_Down Status is Rate_Up
The TX → → ↑
power
threshold F1
≤ DPDCH
power < the
TX power
threshold F2
DPDCH ↑ ↑ ↑
power < the
TX power
threshold F1
↓: depicts the decrease in the permitted highest AMR/AMR-WB speech codec mode.
↑: depicts the increase in the permitted highest AMR/AMR-WB speech codec mode.
As shown in Figure 3-8, the NodeB reports the measurement results by sending a
DEDICATED MEASUREMENT REPORT message.
As shown in Figure 3-9, the RNC adjusts the DL rate by sending an IUUP RATE CONTROL
REQUEST message.
When the originating and terminating connections are using the same speech codec, it is
possible to transmit transparently the speech frames received from the originating UE to the
terminating UE without activating the transcoding functions in the originating and terminating
networks. In this configuration, TFO or Transcoder Free Operation (TrFO) is ongoing.
For detailed information about TFO and TrFO, see 3GPP TS 28.062.
If... Then...
The current UL highest codec mode is The local RNC sends the TRANSPORT
higher than the highest codec mode FORMAT COMBINATION CONTROL
requested by the peer RNC. message to the UE to steer the permitted
highest AMR/AMR-WB speech codec mode
down to the mode that is lower than and
nearest to the highest AMR/AMR-WB speech
codec mode requested by the peer RNC in the
UL controllable mode set.
If... Then...
The following conditions are fulfilled at The local RNC sends the TRANSPORT
the same time: FORMAT COMBINATION CONTROL
z The current UL highest codec mode is message to the UE to steer the permitted
lower than the highest codec mode highest AMR/AMR-WB speech codec mode
requested by the peer RNC. up to the mode that is lower than and nearest to
the highest AMR/AMR-WB speech codec
z The highest codec mode requested by mode requested by the peer RNC in the UL
the peer RNC is not in the UL controllable mode set.
controllable mode set.
z In the UL controllable mode set, there
is an AMR/AMR-WB speech codec
mode that is lower than and nearest to
the highest AMR/AMR-WB speech
codec mode requested by the peer RNC
and that is higher than the current UL
highest AMR/AMR-WB speech codec
mode.
z The UL load resource is not in
congestion state.
The following conditions are fulfilled at The local RNC sends the TRANSPORT
the same time: FORMAT COMBINATION CONTROL
z The current UL highest codec mode is message to the UE to steer the permitted
lower than the highest codec mode highest AMR/AMR-WB speech codec up to
requested by the peer RNC. the highest codec mode requested by the peer
RNC.
z The highest codec mode requested by
the peer RNC is in the UL controllable
mode set.
z The UL load resource is not in
congestion state.
z In the downlink, the permitted highest AMR/AMR-WB speech codec mode can be
adjusted according to 3.3.1 DL Measurement and Event Reporting. If the mode needs to
be adjusted, the local RNC sends the mode adjustment command to the peer RNC. Based
on its own AMRC/AMRC-WB algorithm, the peer RNC will further decide whether to
perform the mode adjustment.
4 DCCC Algorithm
The DCCC_SWITCH is used for internal testing. Do not set the DCCC_SWITCH to OFF
in the commercial network.
The traffic volume measurements defined in 3GPP TS 25.331 are applicable only to the uplink.
Regarding the downlink traffic volume measurements and associated rate reallocation, the design and
implementation are Huawei specific.
When the current traffic rate is 0kbit/s, the traffic measurement event 4A threshold is set to 16byte; when
the current traffic rate is not 0kbit/s, the traffic measurement event 4A threshold is set to 1024byte.
When the current traffic rate is below 128kbit/s, the traffic measurement event 4B threshold is set to
128byte; when the current traffic rate is above 128kbit/s, the traffic measurement event 4B threshold is
set to 256byte.
Traffic volume measurement triggering can be associated with both the time-to-trigger (time
to trigger 4A which is set to 240ms and time to trigger 4B) and the pending time after
trigger(pending_time_after_trigger_4a which is set to 4,000 ms and
pending_time_after_trigger_4b which is set to 4,000 ms). For the definitions of
time-to-trigger and pending time after trigger, refer to section 14.4.3 "Traffic volume
reporting mechanisms" in 3GPP TS 25.331.
In uplink, the time to trigger 4B is 30s. In downlink, the time to trigger 4B is 5000 ms.
z Time-to-trigger is used to get time domain hysteresis, that is, the condition must be
fulfilled during the time-to-trigger period before a report is sent.
z Pending time after trigger is used to limit consecutive reports when one traffic volume
measurement report has already been sent.
In the uplink:
z When the traffic volume is higher than the value of Traffic Measurement Event 4A
threshold for a period of time defined by Time to trigger 4A, the UE reports an event 4a.
No more events 4a are reported during the pending_time_after_trigger_4a.
z When the traffic volume is lower than the value of Traffic Measurement Event 4B
threshold for a period of time defined by Time to trigger 4B, the UE reports an event 4b.
No more events 4b are reported during the pending_time_after_trigger_4b.
In the downlink:
z When the traffic volume is higher than the value of Traffic Measurement Event 4A
threshold for a period of time defined by Time to trigger 4A, the RNC reports internally
an event 4a. No more events 4a are reported during the pending_time_after_trigger_4a.
z When the traffic volume is lower than the value of Traffic Measurement Event 4B
threshold for a period of time defined by Time to trigger 4B, the RNC reports internally
an event 4b. No more events 4b are reported during the pending time
pending_time_after_trigger_4b.
Figure 4-1 Event 4a triggered by an increase in the transport channel traffic volume
Figure 4-2 Event 4b triggered by a decrease in the transport channel traffic volume
The UE reports the uplink event 4a and event 4b by sending the MEASUREMENT REPORT
message.
In the downlink, there are also MEASUREMENT CONTROL message, which carries the
absolute threshold, time-to-trigger of event 4a, time-to-trigger of event 4b,
pending_time_after_trigger_4a, pending_time_after_trigger_4b, and MEASUREMENT
REPORT message, which carries event 4a and event 4b. The difference to those in the uplink
is that they are internal messages in the RNC.
All the preceding parameters associated with events 4a and 4b (Traffic Measurement Event
4A/4B threshold and Time to trigger 4A/4B) take effect in uplink or downlink.
z If Direction is UPLINK, all the preceding event-related parameters take effect in the
uplink.
z If Direction is DOWNLINK, all the preceding event-related parameters take effect in the
downlink.
The rate reallocation based on traffic volume works in either direction separately.
z The RATE_UP_ONLY_ON_DCH strategy means that the rate can only be upsized.
When the network resources are sufficient, the RATE_UP_ONLY_ON_DCH strategy is
recommended.
z The UL DCCC algorithm is unavailable for the BE services whose applied uplink maximum rate is
lower than or equal to the Uplink bit rate threshold for DCCC because DCCC can otherwise bring
processing burden for these BE services.
z The prerequisite of UL rate reallocation based on traffic volume described herein is as follows:
- The UL channel power is ample if the rate reallocation based on uplink quality algorithm is
enabled (see 4.3 Rate Reallocation Based on Link Quality).
- The cell is not in the basic congestion state in the uplink (see 4.4.1 UL BE Rate Downsizing and
Recovery Based on UL Basic Congestion). If the cell is in the basic congestion state in the uplink,
only the service whose bit rate is lower than GBR can upsize bit rate to GBR.
Principles of RATE_UP_AND_DOWN_ON_DCH
z Rate downsizing is performed if the RNC receives a report of event 4b about the uplink
traffic volume.
z Rate upsizing is performed if the RNC receives a report of event 4a about the uplink
traffic volume.
z The lowest value that the rate can be downsized to is the value of Uplink bit rate
threshold for DCCC. The highest value that the rate can be upsized to is MBR.
z When Uplink Rate decrease adjust level is 2_Rates, the data rate is downsized directly
to the value of Uplink bit rate threshold for DCCC.
In the process of upsizing, if the current rate is lower than the value of Uplink bit rate
threshold for DCCC, the rate is upsized to the value of Uplink bit rate threshold for
DCCC. If the current rate is higher than or equal to the value of Uplink bit rate
threshold for DCCC but lower than MBR, the rate is upsized directly to the MBR.
z When Uplink Rate decrease adjust level is 3_Rates, the data rate is downsized to the
value of Uplink mid bit rate threshold if the current rate is the MBR, and then to the
value of Uplink bit rate threshold for DCCC. If the current rate is lower than MBR
and higher than the value of Uplink bit rate threshold for DCCC, the data rate is
downsized to the value of Uplink bit rate threshold for DCCC when downsizing is
triggered.
In the process of upsizing:
− If the current rate is lower than the value of Uplink bit rate threshold for DCCC,
the data rate is upsized to the value of Uplink bit rate threshold for DCCC.
− If the current rate equals the value of Uplink bit rate threshold for DCCC, the data
rate is upsized to the value of Uplink mid bit rate threshold and then to the MBR.
− If the current rate is lower than MBR and higher than the value of Uplink bit rate
threshold for DCCC, the rate is upsized to MBR when upsizing is triggered.
Figure 4-5 Rate reallocation when both Uplink Rate decrease adjust level and Uplink Rate
increase adjust level are 2_Rates
Figure 4-6 Rate reallocation when both Uplink Rate decrease adjust level and Uplink Rate
increase adjust level are 3_Rates
Principles of RATE_UP_ONLY_ON_DCH
z Rate downsizing is prohibited. If a UE is in low activity, the state of the UE is directly
transited to CELL_FACH when the UE state transition algorithm is enabled.
z Rate upsizing is performed if the RNC receives a report of event 4a about the uplink
traffic volume.
Figure 4-7 Rate reallocation when Uplink Rate increase adjust level is 2_Rates
Figure 4-8 Rate reallocation when Uplink Rate increase adjust level is 3_Rates
z The DL DCCC algorithm is unavailable for the BE services whose applied downlink maximum rate
is lower than or equal to the Downlink bit rate threshold for DCCC because DCCC can otherwise
bring processing burden for these BE services.
z The prerequisites of DL rate reallocation based on traffic volume described herein are as follows:
- The DL channel power is ample if the rate reallocation based on downlink quality algorithm is
enabled (event F is reported, see 4.3.2 Downlink Quality Measurement and Event Reporting).
- The cell is not in the basic congestion state in the downlink (see 4.4.2 DL BE Rate Downsizing and
Recovery Based on DL Basic Congestion).
If the cell is in the basic congestion state in the downlink, only the service whose bit rate is lower
than GBR can upsize bit rate to GBR.
Principles of RATE_UP_AND_DOWN_ON_DCH
z Rate downsizing is performed if the RNC receives a report of event 4b about the
downlink traffic volume.
z Rate upsizing is performed if an event 4a about the downlink traffic volume is triggered.
z The lowest value that the rate can be downsized to is the value of Downlink bit rate
threshold for DCCC. The highest value that the rate can be upsized to is MBR.
z When Downlink Rate decrease adjust level is 2_Rates, the rate is downsized directly to
the value of Downlink bit rate threshold for DCCC, or the rate is upsized directly to
the MBR from the value of Downlink bit rate threshold for DCCC.
In the process of upsizing, if the current rate is lower than Downlink bit rate threshold
for DCCC, the rate is upsized to the value of Downlink bit rate threshold for DCCC.
If the current rate is higher than or equal to the value of Downlink bit rate threshold for
DCCC but lower than MBR, the rate is upsized directly to the MBR
z When Downlink Rate decrease adjust level is 3_Rates, the rate is downsized to the
value of Downlink mid bit rate threshold if the current rate is the MBR, and then to the
value of Downlink bit rate threshold for DCCC. If the current rate is lower than MBR
and higher than Downlink bit rate threshold for DCCC, the rate is downsized to the
value of Downlink bit rate threshold for DCCC when downsizing is triggered.
In the process of upsizing:
− If the current rate is lower than Downlink bit rate threshold for DCCC, the data
rate is upsized to the value of Downlink bit rate threshold for DCCC.
− If the current rate equals the value of Downlink bit rate threshold for DCCC, the
data rate is upsized to the value of Downlink mid bit rate threshold and then to the
MBR.
− If the current rate is lower than MBR and higher than Downlink bit rate threshold
for DCCC, the rate is upsized to MBR when upsizing is triggered.
Figure 4-9 Rate reallocation when both Downlink Rate decrease adjust level and Downlink
Rate increase adjust level are 2_Rates
Figure 4-10 Rate reallocation when both Downlink Rate decrease adjust level and Downlink
Rate increase adjust level are 3_Rates
Principles of RATE_UP_ONLY_ON_DCH
z Rate downsizing is not performed. If a UE is in low activity, the state of the UE is
directly transited to CELL_FACH when the UE state transition algorithm is enabled.
z Rate upsizing is performed if an event 4a about the downlink traffic volume is triggered.
z The highest value that the rate can be upsized to is MBR.
z When Downlink Rate increase adjust level is 2_Rates, if the current rate is lower than
Downlink bit rate threshold for DCCC, the rate is upsized to the value of Downlink
bit rate threshold for DCCC. If the current rate is higher than or equal to Downlink bit
rate threshold for DCCC but lower than MBR, the rate is upsized directly to the MBR
z When Downlink Rate increase adjust level is 3_Rates:
− If the current rate is lower than the value of Downlink bit rate threshold for DCCC,
the data rate is upsized to the value of Downlink bit rate threshold for DCCC.
− If the current rate is the value of Downlink bit rate threshold for DCCC, the data
rate is upsized to the value of Downlink mid bit rate threshold and then to the
MBR.
− If the current rate is lower than MBR and higher than the value of Downlink bit rate
threshold for DCCC, the rate is upsized to MBR when upsizing is triggered.
Figure 4-11 Rate reallocation when Downlink Rate increase adjust level is 3_Rates
Figure 4-12 Rate reallocation when Downlink Rate increase adjust level is 2_Rates
z To enable rate reallocation based on throughput for DCH, set the THROU_DCCC_SWITCH of
Channel Class Algorithm Switch parameter to ON through the SET CORRMALGOSWITCH
command firstly.
z To enable rate reallocation based on throughput for HSUPA, set the HSUPA_DCCC_SWITCH of
Hspa Algorithm Switch parameter to ON through the SET CORRMALGOSWITCH command
firstly.
Throughput Measurement
In each measurement period, the MAC-d takes statistics of the data volume properly received
by this RB. The result is then divided by the measurement period to obtain the throughput
value.
z For E-DCH service, the throughput measurement period is specified by the E-DCH Throu Meas
Period parameter.
z For DCH service, the throughput measurement period is set to 1,000 ms.
z For throughput-based rate reallocation on the E-DCH, both events 4a and 4b apply, that is, both rate
upsizing and downsizing are applicable for uplink.
z For throughput-based rate reallocation on the DCH, only event 4b applies, that is, only rate
downsizing is applicable.
Mechanism
Figure 4-17 illustrates the mechanism of throughput measurement and reporting of events 4a
and 4b. In this example, the time to trigger for 4a/4b is three consecutive measurement
periods, and the pending time after trigger for 4a/4b is four consecutive measurement periods.
In RAN10.0, the time to trigger for 4a/4b is set to two consecutive measurement periods; the pending
time after trigger for 4a/4b is set to sixteen consecutive measurement periods.
− The RN is the highest rate in the set defined by the HSUPA UpLink rate adjust set
parameter.
Assume that the maximum bit rate of a service assigned through an RAB
ASSIGNMENT REQUEST message is MaxRate. Then, MaxRateThreshold = MaxRate
x threshold rate ratioMaxRate.
− If Rt < MaxRate ≤Rt+1 (1 ≤ t ≤ N–1), the HSUPA adjustment rate and associated
throughput threshold set is: {(R1, TR1), ..., (Ri, TRi), ..., (Rt, TRt),( RMaxRate,
TRMaxRate)}.
− If MaxRate > RN, the HSUPA adjustment rate and associated throughput threshold set
is: {(R1, TR1), ..., (Ri, TRi), ..., (RN, TRN) ,( RMaxRate, TRMaxRate)}.
8Kbps 90%
16Kbps 90%
32Kbps 90%
64Kbps 90%
128Kbps 80%
144Kbps 80%
256Kbps 80%
384Kbps 75%
608Kbps 75%
1450Kbps 75%
2048Kbps 75%
2890Kbps 70%
5760Kbps 70%
z For DCH services, the rate adjustment set is {rate threshold for DCCC, middle rate,
maximum rate} permanently.
− The rate threshold for DCCC is defined by the Uplink/Downlink bit rate threshold
for DCCC parameter.
− The middle rate is defined by the Uplink/Downlink mid bit rate calculate method
and Uplink/Downlink mid bit rate threshold parameters. For detailed information,
see 4.1.2 UL Rate Reallocation Based on Traffic Volume and 4.1.3 DL Rate
Reallocation Based on Traffic Volume.
− The maximum rate is the MBR.
During each measurement period, throughput measurement on this RB is performed to obtain
the throughput of this period, defined as AvgThroughput.
z If the AvgThroughput is higher than the 4a threshold for two consecutive measurement
periods and the Tpend_4a timer, which is set to sixteen consecutive measurement periods
after event 4a is triggered, is not started, event 4a is reported and the Tpend_4a timer is
started.
z If the AvgThroughput is lower than the 4b threshold for two consecutive measurement
periods and the Tpend_4b timer, which is set to sixteen consecutive measurement
periods after event 4b is triggered, is not started, event 4b is reported and the Tpend_4b
timer is started.
z For E-DCH service, the throughput measurement period is specified by E-DCH Throu Meas
Period parameter..
z For DCH service, the throughput measurement period is set to 1,000 ms.
Thresholds
In the aspect of DCCC for HSUPA,
z The 4a threshold is the throughput threshold associated with the current HSUPA
adjustment rate, that is, TRt.
TRt = Rt x threshold rate ratiot
z The 4b threshold is the throughput threshold associated with the previous rate, that is,
TRt–1.
TRt–1 = Rt–1 x threshold rate ratiot–1
If the current HSUPA adjustment rate is the minimum rate, the 4b rate threshold is the
threshold rate of E-DCH to FACH state transition (E-DCH to FACH 4b Threshold).
In the aspect of DCCC for DCH services, the 4b threshold is calculated as follows:
TRt-1 = Rt-1 x threshold rate ratiot-1
where:
z Rt-1 is the previous rate in the rate adjustment set.
z Threshold rate ratiot-1 is equal to 90%.
Principles of RATE_UP_ONLY_ON_EDCH
z After event 4a is reported, the rate is adjusted by one level upwards. If the current rate is
the maximum rate, no action is required.
z After event 4b is reported, no rate downsizing is done. However state transition can be
done according to rules specified in 4.5 UE State Transition Algorithm.
The DCH rate reallocation based on throughput is implemented through the signaling over the Uu and
Iub interfaces. Only downsizing is applicable to the DCH rate reallocation based on throughput.
For the detailed information about Higher Layer Filtering in the downlink, see 4.3.2 Downlink Quality
Measurement and Event Reporting
Event 6A and 6B
In the uplink, the measurement of UE transmit power can trigger event 6A or event 6B.
z If the transmit power of the UE is above a certain threshold for a period of time, event
6A is triggered.
Event 6A involves two thresholds: 6A1 and 6A2. For detailed information, see 3.2.1 UL
Measurement and Event Reporting.
z If the transmit power of the UE is below a certain threshold for a period of time, event
6B is triggered.
Event 6B involves two thresholds: 6B1 and 6B2. For detailed information, see 3.2.1 UL
Measurement and Event Reporting.
The parameters related to events 6A and 6B are as follows:
z Be trigger time 6A1
z Be trigger time 6A2
z Be trigger time 6B1
z Be trigger time 6B2
Event 6D
If the transmit power of the UE is equal to the maximum transmit power of the UE for a
period of time (the time is defined by the hysteresis), the UE reports event 6D.
For BE services, the hysteresis is specified by the Be trigger time 6D parameter.
Event 5A
The uplink BLER reflects the uplink quality. The change in the BLER is indicated by event
5A.
The RNC defines a sliding window of a certain length. If the number of error blocks during
the sliding window is greater than or equal to a predefined number, event 5A is triggered.
For a specific service parameter index, set the following parameters related to event 5A:
z Statistic Block Number for 5A Event: the length of the sliding window in which the
number of error blocks is counted
z Event 5A Threshold: the number of error blocks in a sliding window, which determines
whether to trigger an event 5A or not
z Interval Block Number: After an event 5A is triggered, no more event 5A is triggered
before a number of blocks (the number is defined by this parameter) are received.
Figure 4-21 shows the triggering and reporting mechanism of event 5A.
Each time a block is received, the number of error blocks within the sliding window is
compared with the Event 5A Threshold parameter. If the number of error blocks is equal to or
greater than the value of the parameter, an event 5A is triggered. When event 5A is triggered,
a pending counter is started to prevent further triggering of the event before a certain number
of transport blocks which is specified by Interval Block Number are received.
The whole process is based on the sliding window mechanism. This window slides with the
arrival of each block. Each time a block is received, the decision on whether to trigger event
5A is made. The number of error blocks is still counted when the pending timer after trigger
timer works. However, no event 5A is triggered even if the triggering conditions are met.
Where:
Event E
Event E has two measurement thresholds, that is, threshold 1, and threshold 2.
z Event Ea means that the transmit power rises higher than measurement threshold 1.
z Event Eb means that the transmit power falls below measurement threshold 2.
For different services, there are different Ea and Eb thresholds. For the sake of simplicity of
parameters, a set of relative thresholds is defined for all BE services, and absolute Ea and Eb
thresholds are calculated by the following formula:
Where:
z is the relative transmit power offset between pilot fields of the DPCCH and
DPDCHs. The relative threshold is Event Ea relative threshold, and maximum DL power
is configured through RL Max DL TX power that is specific to the DPDCHs.
z Maximum DL power is defined through the RL Max DL TX power parameter that is
specific for the DPDCHs.
Both Event Ea relative threshold and Event Eb relative threshold are set to 1dB.
z When the transmit power of the pilot fields of the DPCCH remains above the
measurement threshold 1 for a time period longer than T1 (Be trigger time of Event E),
event Ea is triggered. The NodeB periodically reports the measurement results of the
transmit power to the RNC.
z When the transmit power of the pilot fields of the DPCCH remains below the
measurement threshold 2 for a time period longer than T1 (the trigger time of event E
which is set to 640 ms for BE service), event Eb is triggered. The NodeB stops reporting
the measurement results of the transmit power.
Before event E measurement event evaluation and reporting, DL TCP Measurement Filter
Coefficient is used to perform higher layer filtering.
Event A
The RLC PDU retransmission rate is calculated according to the ACK and NACK feedback
information. The RLC PDU retransmission rate is optional. It is controlled by the Srnc
Downlink RLC QOS Action Trigger Indicator of Traffic BE parameter (through the SET
QOSACT command).
RLC retransmission rate is reported to layer 3 by layer 2. Figure 4-23 shows the RLC
retransmission rate.
Event F
Event F is used to check whether the current transmit power allows rate upsizing.
Event F has two measurement thresholds, threshold 1, and threshold 2.
z Event Fa means that the transmit power falls below threshold 1.
z Event Fb means that the transmit power rises above threshold 2.
The measurement thresholds are various for different current rates and upsizing target rates
which are triggered by event 4a reports. For the sake of simplicity, measurement threshold 1
Where:
z is the power difference between current rate and target rate which is calculated in
RNC through the parameters acquired by the simulation and field test results.
Though these parameters can be changed by using the MML commands on the LMT, it is strongly
recommended that no change be made to them.
z is the event F reporting power margin (Event F reporting power margin)..
z Event Ea relative threshold is used to protect triggering event report Ea after upsizing.
z is the maximum DL power of target rate, that is, the maximum configured power of
the target rate.
z is the relative transmit power offset between pilot fields of the DPCCH and
DPDCHs.
Figure 4-24 shows the reporting mechanism of event F.
z When the transmit power of the pilot fields of the DPCCH remains below the
measurement threshold 1 for a time period longer than T1 (Be trigger time of Event F),
event Fa is triggered. Then the NodeB periodically reports the measurement results of
the transmit power to the RNC.
z When the transmit power of the pilot fields of the DPCCH remains above the
measurement threshold 2 for a time period longer than T1 (the trigger time of event F
which is set to 640 ms for BE service), event Fb is triggered. The NodeB then stops
reporting the measurement results of the transmit power.
Before event F measurement event evaluation and reporting, DL TCP Measurement Filter
Coefficient is used.
The event F threshold cannot be higher than the Ea threshold. Otherwise, this threshold is set to Ea
threshold.
Rate Downsizing
For rate downsizing based on uplink quality, only the 3-rate downsizing applies.
z If the current rate is MBR, the rate is downsized to the value of Uplink mid bit rate
threshold.
z If the current rate is higher than Uplink full coverage bitrate but lower than MBR, the
rate is downsized to the value of Uplink full coverage bitrate.
The Uplink mid bit rate threshold parameter is the same as that described in 4.1 Rate Reallocation
Based on Traffic Volume.
The Uplink mid bit rate threshold is the middle bit rate threshold for adjustment of the traffic volume
in the uplink. When Uplink Rate decrease adjust level is 2_Rates, the middle bit rate for the rate
reallocation based on uplink quality is equal to the RB rate closest to MBR divided by two. The bit rate
is calculated in the RNC.
Figure 4-25 Rate downsizing based on uplink quality in the case of 3-rate adjustment
Rate Upsizing
Figure 4-26 shows the process of rate upsizing based on uplink quality.
If the RNC receives an event 6B2 but no event 6A2, rate upsizing based on
traffic-volume-related event 4a is allowed.
If the RNC receives an event 6A2, rate upsizing based on traffic-volume-related event 4a is
not allowed. If the RNC receives an event 6B1, rate downsizing is stopped and rate upsizing
is still prohibited.
For detailed information about event 4a reporting and the rate upsizing process, see 4.1.2 UL
Rate Reallocation Based on Traffic Volume.
Rate Downsizing
For rate downsizing based on downlink quality, only the 3-rate downsizing applies.
z If the current rate is MBR, the rate is downsized to the value of Downlink mid bit rate
threshold.
z If the current rate is higher than Downlink full coverage bitrate but lower than MBR,
the rate is downsized to the value of Downlink full coverage bitrate.
z The Downlink mid bit rate threshold parameter is the same as that described in 4.1 Rate
Reallocation Based on Traffic Volume.
z The Downlink mid bit rate threshold is the middle bit rate threshold for adjustment of the traffic
volume in the downlink. When Downlink Rate adjust level is 2_Rates, the middle bit rate for the
rate reallocation based on downlink quality is equal to the RB rate closest to MBR divided by two.
The bit rate is calculated in the RNC.
Figure 4-27 Rate downsizing based on downlink quality in the case of 3-rate adjustment
Rate Upsizing
The rate upsizing process requires checking whether the current DL channel power is ample.
Rate upsizing is allowed only when the DL channel power is ample. Figure 4-28 shows the
process of rate upsizing based on downlink quality.
If event Fa is reported, it indicates that the DL channel power is ample. Rate upsizing is then
performed if event 4a is reported.
If event Fb is reported, it indicates that the DL channel power is not ample. Then rate upsizing
is prohibited.
For detailed information about event 4a reporting and the rate upsizing process, see 4.1.3 DL
Rate Reallocation Based on Traffic Volume.
z The Uplink mid bit rate threshold parameter is the same as that described in 4.1 Rate Reallocation
Based on Traffic Volume.
z The Uplink mid bit rate threshold is the middle bit rate threshold for adjustment of the traffic
volume in the uplink. When Uplink Rate decrease adjust level is 2_Rates, the middle bit rate is
equal to the RB rate closest to MBR divided by two. The bit rate is calculated in the RNC.
z If the selected RAB is an HSUPA RAB, the target rate is determined according to the
configured HSUPA adjustment rate in order (For detailed information about the HSUPA
UpLink rate adjust set parameter, see 4.2.1 Throughput Measurement and Event
Reporting). The target rate has to be greater than or equal to GBR.
Figure 4-30 shows an example of UL BE rate downsizing and upsizing (DCH RAB). In this
example, the Uplink Rate decrease adjust level parameter is set to 3_Rates, rate downsizing
is triggered by UL basic congestion, and rate upsizing is triggered when basic congestion is
removed. In addition, the current UL rate can be the initial rate, middle rate, or maximum bit
rate.
When the current UL rate is the maximum bit rate, the current rate is downsized to the middle rate if a
UL basic congestion report is received, and the rate is then downsized to the GBR if a second UL basic
congestion report is received.
Figure 4-30 UL BE rate downsizing and upsizing based on UL basic congestion (2)
z The Downlink mid bit rate threshold parameter is the same as that described in 4.1 Rate
Reallocation Based on Traffic Volume.
z The Downlink mid bit rate threshold is the middle bit rate threshold for adjustment of the traffic
volume in the downlink. When Downlink Rate decrease adjust level is 2_Rates, the middle bit rate
is equal to the RB rate closest to MBR divided by two. The bit rate is calculated in the RNC.
Figure 4-31 shows an example of DL BE rate downsizing and upsizing. In this example, rate
downsizing is triggered by DL basic congestion, and rate upsizing is triggered when basic
congestion is removed. In addition, the current DL rate can be the initial rate, middle rate, or
maximum bit rate.
When the current DL rate is the maximum bit rate, the current rate is downsized to the middle rate if a
DL basic congestion report is received, and the rate is then downsized to the GBR if a second DL basic
congestion report is received.
Figure 4-31 DL BE rate downsizing and upsizing based on DL basic congestion (2)
UL Signaling Procedure
Figure 4-32 shows the signaling procedure of UL rate downsizing based on the UL cell basic
congestion.
DL Signaling Procedure
Figure 4-33 shows the signaling procedure of DL rate downsizing based on the DL cell basic
congestion.
z The upsizing failure counter always works, instead of being valid only during the DCCC rate
upsizing failure monitoring time. The DCCC rate upsizing failure monitoring timers for uplink and
downlink, which have the same length, work independently.
z If the number of rate upsizing failures equals or exceeds the threshold of rate upsizing failure times,
the DCCC rate upsizing failure penalty timer is started, and the DCCC rate up fail monitor timer is
stopped.
z When the cell is in basic congestion state, the services, whose bit rate is lower than GBR, are
allowed to upsize rates. The success of the rate upsizing, however, depends on the related resources
being sufficient.
z PS_NON_BE_STATE_TRANS_SWITCH
z HSDPA_STATE_TRANS_SWITCH
z HSUPA_STATE_TRANS_SWITCH
If the above state transition switches are set to on, and:
z The DCCC_SWITCH is on and DCCC strategy is
RATE_UP_AND_DOWN_ON_DCH, the UE state transition algorithm starts to work if
the uplink and downlink bit rate equals or falls below the Uplink/Downlink bit rate
threshold for DCCC.
z The DCCC_SWITCH is on and DCCC strategy is RATE_UP_ONLY_ON_DCH, the
UE state transition algorithm always works.
z The DCCC_SWITCH is off; the UE state transition algorithm always works.
The following types of UE state transition are described:
z UE State Transition From CELL_DCH to CELL_FACH
z UE State Transition From CELL_FACH to CELL_PCH
z UE State Transition From CELL_PCH to URA_PCH
z UE State Transition From CELL_PCH or URA_PCH to CELL_FACH
z UE State Transition From CELL_FACH to CELL_DCH
For UE state transition, if the corresponding parameters for the PS' user inactive detecting timer in the
SET PSINACTTIMER command are set too small, the RRC connection is released before state
transition.
When the RNC receives the 4b event report, the CELL_DCH to CELL_FACH transition
timer and the uplink and downlink 4b counters are started on the RNC side. If both uplink and
downlink 4b counters of traffic volume event 4b report are greater than or equal to a
CELL_DCH to CELL_FACH transition threshold before the timer expires, the UE state
transits from CELL_DCH to CELL_FACH when the timer expires.
The CELL_DCH to CELL_FACH transition threshold is the rounded-down value of the
following formula:
CELL_DCH to CELL_FACH transition threshold = [CELL_DCH to CELL_FACH transition
time / (time to trigger + pending time after trigger) x state transition traffic redundancy
coefficient]
Where:
z CELL_DCH to CELL_FACH transition time, time to trigger, and pending time after
trigger are set through the parameters listed in Table 4-2.
z State transition traffic redundancy coefficient is used to avoid detecting UE in
low-activity state incorrectly due to the loss of measurement reports. The value of this
coefficient is set to 80%.
Table 4-2 Parameters used for UE state transition from CELL_DCH to CELL_FACH
Real-time Realtime Traff Realtime Traff Realtime Traff Realtime Traff DCH
PS service DCH or HSPA to DCH or HSPA to DCH or HSPA to or HSPA to FACH 4b
FACH transition FACH 4b FACH 4b time to pending time
timer threshold trigger
The state transition from E-DCH to FACH is similar to the state transition from CELL-DCH
to CELL-FACH. The difference is that the measurement quantity of the 4b event is the
throughput value. The throughput measurement period configured on the network side is
E-DCH Throu Meas Period. the threshold configuration value of the associated event 4b is
also the throughput value which is indicated by the E-DCH to FACH 4b Threshold
parameter.
UE state transition, however, is not applicable in the following cases:
z For BE services on the DCH,
If PS_BE_STATE_TRANS_SWITCH is set to OFF, or other services which cannot
perform state transition are configured for the UE, no state transition is performed on the
UE. Instead, if both uplink and downlink 4b counters of traffic volume event 4b report
are greater than or equal to a CELL_DCH to CELL_FACH transition threshold when the
CELL_DCH to CELL_FACH transition timer expires, the UE is reconfigured to the
low-activity rate that is defined through the Low activity bit rate threshold parameter.
However, if the value of Low activity bit rate threshold is greater than or equal to that
of Uplink/Downlink bit rate threshold for DCCC, the reconfiguration to Low activity
bit rate threshold is prohibited.
z For BE services on the HS-DSCH or E-DCH,
If PS_BE_STATE_TRANS_SWITCH or
HSDPA_STATE_TRANS_SWITCH/HSUPA_STATE_TRANS_SWITCH is set to
OFF, or other services which cannot perform state transition are configured for the UE,
the UE does not undergo state transition.
z For real-time PS services,
If PS_NON_BE_STATE_TRANS_SWITCH is set to OFF, or other services which
cannot perform state transition are configured for the UE, the UE does not undergo state
transition.
z For the BE services on the uplink DCH and downlink HS-DSCH, configure time to trigger, pending
time after trigger, and 4b threshold respectively for the uplink and downlink.
z For the BE and real-time services on the uplink and downlink DCH, configure time to trigger,
pending time after trigger, and 4b threshold by using the same parameters for both the uplink and
downlink.
z For the real-time services on the uplink DCH and downlink HS-DSCH, configure time to trigger,
pending time after trigger, and 4b threshold by using the same parameters for both the uplink and
downlink.
z For the BE and real-time services on the uplink E-DCH and downlink DCH or HS-DSCH, configure
time to trigger, pending time after trigger, and 4b threshold respectively for the uplink and downlink.
Table 4-3 lists the parameters used to calculate the threshold for UE state transition from
CELL_FACH to CELL_PCH.
Table 4-3 Parameters used for UE state transition from CELL_FACH to CELL_PCH
The state transition from CELL_PCH to URA_PCH involves the transient state CELL_FACH, in which
some necessary signaling interaction is performed.
Table 4-4 Parameters used for UE state transition from CELL_FACH to CELL_DCH
BE service on BE F/RACH to z For the uplink, the target rate equals the smaller one
the DCH DCH 4a of MBR and Uplink bit rate threshold for DCCC
threshold z For the downlink, the target rate equals the smaller
one of MBR and Downlink bit rate threshold for
DCCC
z Streaming service T1
z Streaming service T2
z Interactive service T1
z Interactive service T2
z Background service T1
z Background service T2
z IMS signal T1
z IMS signal T2
3. If the CN does not initiate the service release, and the PDCP still detects no UL or DL
data packet when timer T2 expires, the PDCP entity sends the request again to the RRC
layer for the service release.
− If there is only one RAB for the UE in the PS domain, the RNC sends an IU
RELEASE REQUEST message to the CN.
− If there is more than one RAB for the UE in the PS domain, the RNC sends an RAB
RELEASE REQUEST message to the CN.
The release cause carried in both messages is "User Inactivity".
4. When the CN receives the message, it initiates the release procedure.
The CN reserves the PDP context of the service and the UE does not have to apply for the
PDP context again when it reinitiates the service.
The service release request sent from the PDCP entity may not be processed in time. That is because the
associated processor in the RNC is busy.
z The link stability control algorithm is applied only to single RAB case.
z To enable link stability control algorithms, the switches of link stability control algorithms must be
set to ON through the SET QOSACT command.
Related Actions
z When rate downsizing is configured, that is, when link-quality-based
AMRC/AMRC-WB algorithm is enabled, if a 6A1 or 6D report is received or the UL
For AMR service, the trigger time of event E is set to 640 ms, and the reporting period of event E is set
to 4,800 ms.
Related Actions
z When rate downsizing is configured (that is, when link-quality-based
AMRC/AMRC-WB algorithm is enabled) and the current rate is GBR, if the average
DPDCH transmit power is lower than the E1 threshold and higher than the E2 threshold
but the AMR/AMR-WB status is "Rate-Down" (described in 3.3.2 DL
AMRC/AMRC-WB Algorithm) or higher than the E1 threshold, then
− If InterFreq Handover Switch based on Downlink Traffic AMR/WAMR is set to
YES, inter-frequency handover is performed.
− If InterRat Handover Switch based on Downlink Traffic AMR/WAMR is set to
YES, inter-RAT handover is performed.
− If both the switches are set to YES, the inter-frequency and inter-RAT measurement
are started at the same time, and then the RNC decides to perform which type of
handover based on the first report from the UE.
z When rate downsizing is not configured, that is, when link-quality-based
AMRC/AMRC-WB algorithm is not enabled, if an event Ea report is received, then
For VP service, the trigger time of event 6A1 and 6B1 are both set to 640 ms, and the trigger time of
event 6D is set to 240 ms.
Related Actions
When link stability control algorithm for VP services is enabled for uplink (InterFreq
Handover Switch based on Uplink Traffic VP is set to YES), Inter-frequency handover is
performed if an event 6A1 or 6D report is received. For detailed information about the
handover action, see Inter-Frequency Handover.
For VP service, the trigger time of event E is set to 640 ms, and the reporting period of event E is set to
4,800 ms.
Related Actions
When link stability control algorithm for VP services is enabled for downlink (InterFreq
Handover Switch based on Downlink Traffic VP is set to YES), Inter-frequency handover
is performed if an Ea report is received. For details of the handover action, see
Inter-Frequency Handover.
Triggering Condition
z When Measurement of 6D Switch is ON, event 6D can directly trigger uplink link
stability control action.
z When Uplink QOS Action Trigger Indicator of Traffic BE is SINGLE and
Measurement of 6A1 Switch is ON, event 6A1 can trigger uplink link stability control
action.
z When Uplink QOS Action Trigger Indicator of Traffic BE is SINGLE and
Measurement of 5A Switch is ON, event 5A can trigger uplink link stability control
action.
z When Uplink QOS Action Trigger Indicator of Traffic BE is COMBINE, the
combination of event 6A1 and event 5A can trigger uplink link stability control action.
Related Actions
The related procedure is shown in the following figure.
Figure 5-1 The related procedure of uplink link stability control algorithm
Note 1:
The sequence of the link stability control actions is determined by the settings of the
following parameters:
z First Uplink QOS Enhancement Action for Traffic BE
z Second Uplink QOS Enhancement Action for Traffic BE
z Third Uplink QOS Enhancement Action for Traffic BE
Note 2:
A, B, and C in the figure denote the actions as follows:
z A denotes rate downsizing.
z B denotes inter-frequency handover.
z C denotes inter-RAT handover.
Note 3:
The action in the dashed frame can be ignored in a link stability control procedure, if the
last procedure has contained the rate downsizing action and the current rate is above
Uplink Full Coverage Bitrate.
Note 4:
The timer waiting for uplink rate adjustment of traffic BE is specified by the Wait timer
for uplink rate adjustment of traffic BE parameter.
After the uplink link stability control algorithm is triggered, the RNC takes actions on the BE
service in the sequence defined on the LMT. The RNC takes a second action when the
previous action fails. The sequence of the actions is as follows:
z The action defined by the First Uplink QOS Enhancement Action for Traffic BE
parameter
z The action defined by the Second Uplink QOS Enhancement Action for Traffic BE
parameter
z The action defined by the Third Uplink QOS Enhancement Action for Traffic BE
parameter
For detailed information about the rate downsizing action, see 4.3.3 Rate Reallocation Action
Based on Uplink Quality.
Triggering Condition
When determining the downlink link stability control, the following two aspects are taken into
account:
z One is the current transmit power.
When the transmit power of the downlink channel reaches the maximum power, it is an
indication that the radio link is unstable. The following condition must be fulfilled: The
transmit power of downlink channel exceeds the Ea event relative threshold which
equals to 1 dB.
z The other is RLC PDU retransmission rate in AM RLC mode.
When the Srnc Downlink RLC QOS Action Trigger Indicator of Traffic BE is set to
YES, the downlink link stability control algorithm is determined only if the RLC
retransmission rate exceeds the retransmission threshold (that is, Event A threshold,
which equals to 16%).
When the Srnc Downlink RLC QOS Action Trigger Indicator of Traffic BE is set to
NO, related actions are triggered so long as the current transmit power fulfils the criteria.
Related Actions
The related procedure is shown in Figure 5-2.
Figure 5-2 The related procedure of downlink link stability control algorithm
Note 1:
The sequence of the link stability control actions is determined by the settings of the
following parameters:
z First Downlink QOS Enhancement Action for Traffic BE
z Second Downlink QOS Enhancement Action for Traffic BE
z Third Downlink QOS Enhancement Action for Traffic BE
Note 2:
A, B, and C in the figure denote the actions as follows:
z A denotes rate downsizing.
z B denotes inter-frequency handover.
z C denotes inter-RAT handover.
Note 3:
The action in the dashed frame can be ignored in a link stability control procedure, if the
last procedure has contained the rate downsizing action and the current rate is above
Downlink Full Coverage Bit Rate.
After the downlink link stability control algorithm is triggered, the RNC takes actions on the
BE service in the sequence defined on the LMT. The RNC takes a second action when the
previous action fails. The sequence of the actions is as follows:
z The action defined by the First Downlink QOS Enhancement Action for Traffic BE
parameter
z The action defined by the Second Downlink QOS Enhancement Action for Traffic BE
parameter
z The action defined by the Third Downlink QOS Enhancement Action for Traffic BE
parameter
For detailed information about the rate downsizing action, see 4.3.4 Rate Reallocation Action
Based on Downlink Quality.
This chapter provides information on the effective level and configuration of the parameters
related to rate control.
Table 6-1 lists the parameters related to rate control.
Rate Control Reference Documents lists the reference documents related to the feature.
z 3GPP TS 25.331: Radio Resource Control (RRC)
z 3GPP TS 25.413: UTRAN Iu interface RANAP signalling
z 3GPP TS 25.415: UTRAN Iu interface user plane protocols
z 3GPP TS 25.433: UTRAN Iub interface NBAP signalling
z 3GPP TS 26.101: Mandatory speech codec speech processing functions; Adaptive
Multi-Rate (AMR) speech codec frame structure
z 3GPP TS 26.201: Speech codec speech processing functions; Adaptive Multi-Rate -
Wideband (AMR-WB) speech codec; Frame structure
z 3GPP TS 28.062: Inband Tandem Free Operation (TFO) of speech codecs; Service
description; Stage 3