3G:

NodeB Fast Dynamic Code Allocation

By default, HS-PDSCHs are allocated by the RNC dynamically. Compared with the HSDPA 2ms scheduling,
the signaling delay between the RNC and the NodeB is too long, thus the RNC has to reserve sufficient idle
codes for R99 when allocating HS-PDSCHs. The idle codes may cause SF16 resource waste. Therefore,
dynamic code allocation by the NodeB is used instead of dynamic HS-PDSCH allocation by the RNC.

Fast Dormancy
To save battery consumption, for some smart phones whose versions are 3GPP Release 7 or Pre-Release 7,
once the data transmission ends, they send a SIGNALLING CONNECTION RELEASE INDICATION (SCRI)
message. Upon receiving the SCRI message, the network releases the Iu signaling and RRC connection.
This process is called “Pre-R7 Fast Dormancy”. When there are data packages to be transmitted again, the
RRC connection and RB/RAB are reestablished. This frequent data transmission causes frequent network
connection and release, and produces many signaling messages, and it is easy to cause a signaling storm.
To resolve this problem, 3GPP Release 8 introduced a simple UE signaling to indicate the state of a UE for
the network. A new UE information element (IE) "Signaling Connection Release Indication Cause" is added
to the SCRI message, and is used to indicate that the UE has decided to stop activated PS data
transmission. On receiving the IE, the UTRAN can decide to trigger an RRC state transition from the
CELL_DCH state to the CELL_FACH, URA_PCH or IDLE state.
The RNC controls whether timer T323 can be broadcast in the SIB1 by using switch
UUeCnst.t323Swch. If the switch is enabled, timer T323 is broadcast in the SIB1. The value of
T323 is determined by UUeCnst.t323.
When the UE sends an SCRI message with the IE "Signaling Connection Release Indication Cause" being set
to "UE Requested PS Data session end", timer T323 is started. During the running of timer T323, the UE is
inhibited from sending the SCRI message with the IE "Signaling Connection Release Indication Cause"
being set to "UE Requested PS Data session end" again.
service Optimization for Multi-RAB Feature
This feature decreases the interference in voice services caused by high bit-rate data services in
multi-RAB scenarios ensures voice service quality, and improves user experience.
With the popularization of smart phones and data services, during a voice service keeping procedure, data
transmission procedures, such as Keep-Alive message receiving and transmission, are often initiated by
applications. Such data transmission processes are even invisible to users. Voice services, especially
incoming calls, may still be connected during the data service keeping process. In most cases, the duration
of a voice service is comparatively shorter, and users are more sensitive to voice service quality. Therefore,
in such multi-RAB scenarios, the dropped-call rate of voice services must be decreased to the greatest
extent possible to guarantee the voice service quality. To achieve this goal, the PS service can be
established at the minimum bit rate of DRBC on the DCH channel in case that a PS service is added to a
voice service. Conversely, if a voice service is added to a PS service, the PS service is again reconfigured to
operate at the minimum bit rate of DRBC on the DCH channel. In addition, during a voice service process,
it is prohibited to reallocate the PS service to HSPA due to traffic volume to avoid call drops caused by
HSDPA serving cell change, and decrease the interference in voice services caused by high-speed PS
services carried over HSPA. If some CS voice services last for a long time, to avoid PS service Quality of
Experience (QoE) degradation within the whole CS+PS duration, the ZTE RAN provides a configurable
timer. This timer is triggered when a CS service is established. If there are concurrent PS services initiated
before the timer expires, then, after the timer expires, DRBC operations for those concurrent PS services,
such as rate adjustment and channel switching, are allowed.
The policies described above aims to improve the CS voice service experience.
Handover Optimization in Weak Coverage
1. The fundamental principle is that a decision of handover is made according to the quality of the target
cell to be added into the active set. If the quality of the target cell does not meet the quality
threshold, a soft handover is not performed to avoid call dropping due to the poor quality of the
target cell.
2. The feature provides optimization for the second scenario. When the timer expires before the RNC
 receives the Active Set Update Complete message, if the user plane confirms that the UE has received
the Active Set Update message, the active set update procedure is considered a success, and the RNC
can proceed with the subsequent processes. The call drops due to not receiving the Active Set Update
Complete message can be avoided.

Adaptive Radio Bearer

To connect a user to the network faster, a high speed SRB, such as the 13.6 kbps SRB, is used by the RAN in
signal radio bearer establishment. However, comparing with a low speed SRB, the high speed SRB
consumes more downlink and uplink transmission power. When a user is in a poor coverage area, a high
speed SRB establishment may fail easily. By using the radio quality information carried in the connection
request message, ZTE RAN uses the 3.4 kbps SRB for users in weak coverage areas.

DCH HSDPA Fairness

In a cell shared by R99 and HSDPA users, to prevent the service experience of HSDPA users from being
worse than that of R99 users because more cell resources are used by R99 users, the RAN regularly
detects the total downlink channelization codes used by R99 and HSDPA users, and dynamically adjusts
the codes allocated between them. If the number of downlink channelization codes used by HSDPA users
is above the safe threshold, the RAN reduces the downlink bit rate of R99 users, and forbids the downlink,
bit rate of online R99 users from being increased. Otherwise, R99 users have priority rights to use
downlink channelization codes, the codes that are not used by R99 users are allocated to HSDPA users.
DCH HSUPA Fairness
In a cell shared by R99 and HSUPA services, the uplink cell resources are preferentially allocated to R99
users in most cases. As more and more HSUPA handsets are penetrating commercial networks, the uplink
bit rate of HSUPA users may be lower than that of R99 users over a long period, resulting in a bad
experience for HSUPA users. An HSUPA congestion status is recognized when the number of unhappy
HSUPA users is higher than the predefined threshold and the bit rate of unhappy HSUPA users is lower
than the predefined threshold. The uplink bit rate of online R99 users is downgraded, and the upgrade
requirements for their uplink bit rate are rejected until the congestion is removed.