Beruflich Dokumente
Kultur Dokumente
UR11.1
Optional
Feature Description
Date
2012/04/05
Author
ZTE
Reviewer
Notes
Not open to the third party
FIGURES
Figure 1-1
Figure 2-1
Figure 2-2
Figure 2-3
Figure 2-4
Figure 2-5
Figure 2-6
Figure 2-7
Figure 2-8
Figure 2-9
SR-VCC............................................................................................................ 33
Figure 2-10
Figure 2-11
Figure 2-12
Figure 2-13
Figure 2-14
Figure 2-15
Figure 2-16
Figure 2-17
Figure 2-18
Figure 2-19
Figure 2-20
Figure 3-1
Figure 3-2
Figure 3-3
Figure 3-4
Figure 3-5
Figure 3-6
Figure 3-7
Figure 3-8
Figure 3-9
Figure 3-10
Figure 3-11
Figure 3-12
Figure 3-13
Figure 3-14
Figure 3-15
Figure 4-1
Figure 7-1
Figure 7-2
Figure 7-3
Figure 7-4
TABLES
Table 2-1
Table 3-1
Table 3-2
Table 4-1
Table 6-1
1.1
1.2
Introduced Version
U9.1&Before
Enhanced Function
No
1.3
Figure 1-1
Node B
UE
RNC
(e.g.
3GSGSN)
Node B
UE
Cell
Broadcast
Center
(CBC)
Iub
Uu
Iu
Bc
In Figure 1-1, CBE (Cell Broadcast Entity) is the source of CBS content, interface to
information provider and is in charge of formatting CBS messages. CBC is cell broadcast
center and is in charge of the storage and the management of CBS messages. CBC
connects to RNC via Iu-BC interface standardized by 3GPP. RNC receives commands
and CBS messages from CBC and executes the broadcasting procedure in the air in the
certain area. RNC also needs to give response to the CBC inquiring and report
broadcasting states of CBS messages.
ZTE RNC supports standard Iu-BC interface and its protocol SABP (please refer to
3GPP TS25.419). ZTE RNC can be connected to one or more CBC products from the
third party with standard Iu-BC interface.
ZTE RNC also supports ETWS service (please refer to 3GPP TS 22.168) to activate user
to receive alarming CBS message in case of a disaster. To enable ETWS function, CBC
and UE are required.
Introduced Version
U9.2
Enhanced Function
No
1.4
1.4.1
The IMS introduced into the R5 version by the 3GPP provides universal network
architecture of multimedia service in an IP-based network. It also makes it possible to
bear AMR or WB-AMR services based on PS. These services require higher real time
requirements than those of the interactive services, background services, and streaming
services that generally borne by PS. The CN is required to configure traffic class as
session when establishing the RAB of this type of services.
ZTE RAN equipment supports PS session services:
According to the parameters assigned by the CN, ZTE RAN equipment can
provide a higher priority for PS session services during the packet scheduling
and RRM algorithm processing to ensure the QoS performance required by
session services, such as GBR, delay, and jitter and provide better services.
The improved user plane supports multiple PDU lengths of RLC in UM mode
to match data load. It also reduces the padding resulting from RLC
segmentation and reassembly, and enhances the efficiency of payload
transfer rate of an air interface.
The RAB radio parameters of ZTE RAN equipment, used to bear PS session services,
follow the definition in the 3GPP TS 34.108.
Introduced Version
U9.1&Before
Enhanced Function
No
1.4.2
Benefits
This feature supports compressing IP header of the service data in PDCP layer to reduce
the radio bearer bandwidth required for VoIP service and enhance the capacity of system
VoIP service.
l
Description
When a radio link bears VoIP service, the overhead of the IP packet header is large. A
VoIP data packet includes an IPv4 header (20 bytes), a UDP header (8 bytes), and an
RTP header (12 bytes). When IPv4 is used for bearer, VoIP protocol header needs
altogether 40 bytes; the header of IPv6 is 40 bytes; therefore, VoIP packet header
amounts to 60 bytes; but in 12.2K AMR codec voice, a frame only occupies 32 bytes.
Thus, the data payload in the VoIP packet is even smaller than the protocol header. For
a radio link which can only provide limited data bandwidth, direct VoIP service bearer will
waste a huge number of radio resources.
Between a terminal and a UTRAN access point, channelization code, scrambling or
other user IDs are used for addressing. This is a point-to-point connection and it is
unnecessary for both call parties to transfer complete RTP (RTCP)/UDP/IPv6 (IPv4)
header in each frame. IP header can be compressed through negotiation to reduce the
waste of radio resources.
However, characteristics of a radio link make a common IP header mark compression
-1
-3
plan unable to work well. First, a radio channel has path loss and must bear 10 ~10 Bit
Error Ratio (BER); second, the Return Time (RTT) may be as long as 100ms; last but not
least, the residual BER should be taken into consideration. That is, sometimes a low
layer submits an undetected error frame to a higher layer.
The 3GPP introduces the robust header compression ROHC algorithm defined in the
RFC3095. This algorithm can effectively compress header on a link with a long RTT and
high error rate. The ROHC enhances the error recovery mechanism. Each compressed
header contains a checksum calculated according to the original uncompressed header.
Loss of synchronization of context can be repaired at the receiving terminal based on this
checksum. After the adoption of the ROHC technology, IP/UDP/RTP protocol header
may be compressed to one byte. This greatly improves the bandwidth efficiency of VoIP
bearer on a radio link.
l
Introduced Version
U9.1&Before
l
Enhanced Function
No
1.4.3
1.4.4
2.1
Connection Management
2.1.1
ZWF21-01-009 SIB11bis
Benefits
This feature supports the cell System Information Block broadcast of the SIB11bis,
realizes the broadcast of more adjacent cell information over complicated networking
environment (such as dense urban area) and optimizes cell reselection of the terminal.
Description
Limited by the length of the broadcasted information block, SIB11 can broadcast
information to up to 96 adjacent cells, including intra-frequency cells, inter-frequency
cells and inter-system cells. In the complicated networking environment with multiple
frequency points, multiple frequency bands, and multiple systems, the configuration
of adjacent cell broadcasting is a bottleneck. The SIB11bis extends the adjacent
cells broadcasting capability of SIB11 with the adjacent cell number doubled.
Introduced Version
U9.1&Before
Enhanced Function
No
2.1.2
Domain Specific Access Restriction (DSAR) enables operator to restrict the traffic load of
a specific Core Network (CN) domain. And moreover, different access restrictions can be
applied to different CN domains.
Most possibly, core network may become congested in case of football games, large
meeting presentations and etc. When a CN domain is overloaded, RAN informs UEs
belonging to some access classes (AC) that they are not allowed to access to such a CN
domain. The restriction information is broadcasted in the system information message on
AC basis sequentially. A certain proportion of AC, R%, is limited at a fixed interval. Within
the next interval, RAN limits the other R% of UEs and releases all the other UEs.
The proportion of limited AC is configurable per domain for a cell. And the restriction
interval is also configurable per cell. It is possible to have different access class
restrictions on different CN domain.
below gives an example as 2% of AC is prohibited from accessing
CS domain and 3% of AC are prohibited from accessing CS domain. The restriction
interval is 1 minute.
Figure 2-1 An example of DSAR activated for both CS domain and PS domain
Timer (minute)
1
AC0
AC1
AC2
AC3
x
x
AC4
AC5
AC7
AC8
10
o
x
o
x
o
x
AC9
AC6
x CS Domain
O PS Domain
When the specific CN domain recovers from overload, RAN would stop DSAR for the
domain. The operator can decide whether to trigger the DSAR function when a CN
domain is overloaded.
Manually enabling DSAR for a domain is also supported in ZTE RAN. It is possible to
control and restrict CS traffic and PS traffic separately with more flexibility. For example,
More PS traffic may be restricted in order to leave CS capacity for users.
Logs and alarms about DSAR are provided for operator to monitor the network status.
Function of PPAC, Paging Permission with Access Control, also could be implemented
to set indicator in cell broadcast system information to allow UE responding paging
message, which is useful to avoid failure of communication between UE or emergency
service call back where access control is performed.
Introduced Version
U9.3
l
Enhanced Function
No
2.1.3
Enhanced Function
No
2.1.4
2.1.5
When a UE makes a connection with the UTRAN, the UE indicates the confidentiality
and integrity algorithms supported by the UE in MS/USIM Classmark. RNC compares the
information with the confidentiality and integrity capability when a user subscribes for the
service, then a proper algorithm is selected. Thus more and more flexible encryption
algorithms are provided.
This feature complies with the security mechanism and SNOW 3G algorithms specified
in 3GPP TS 33.102 TS 35.215~218 TS 35.919.
Introduced Version
U9.3
Enhanced Function
No
2.1.6
Besides UIA1, an alternative integrity protection algorithm is offerd to make the network
safer, and integrity protection can be carried out based on user level.
Description
This feature realizes UIA2, which is known as f9 and is specified in 3GPP R7. The
algorithm f9 is used to protect the integrity of the signaling sent between the UE and the
RNC.
The followings are the diffirences between UIA2 and UIA1:
When a UE makes a connection with the UTRAN, the UE indicates the confidentiality
and integraty algorithms supported by the UE in MS/USIM Classmark. RNC compares
the information with the integrity capability when a user subscribes for the service and
the RNC capability, then a proper algorithm is selected. Thus more and more flexible
integrity algorithms are provided.
This feature complies with the security mechanism and SNOW 3G algorithms specified
in 3GPP TS 33.102 TS 35.215~218 TS 35.919.
l
Introduced Version
U9.3
Enhanced Function
No
2.2
Mobility Management
2.2.1
This feature is used to guarantee users communication quality, avoid the interference to
other users, and optimize the system capacity.
Description
This feature contains two handover types: HO based on uplink transmitting power and
HO based on downlink transmitting power.
In the real network, there may exist such a scenario: the quality of pilot signal hasnt
reached the threshold which can trigger the coverage based handover, but UEs uplink
transmitting power or Node Bs downlink transmitting power has already reached a high
degree as a result of the interference or the different coverage scope between the
service channel and the pilot signal channel. In that case, increasing transmitting power
cant guarantee UEs QoS. To avoid the interference to other users, it is necessary to
hand over UE to other cell.
ZTE RNC equipment detects uplink transmitting power reported from UE or downlink
transmitting power reported from Node B. Once the transmitting power is higher than a
certain threshold (configured as close to the maximum transmitting power allowed in
usual), RNC can automatically initiate inter-frequency or inter-system measurement to let
UE hand over to an inter-frequency or inter-system cell which has better quality.
Introduced Version
U9.1&Before
Enhanced Function
No
2.2.2
In the real network, there may exist such a scenario: the quality of pilot signal hasnt
reached the threshold which can trigger the coverage based handover, but the UEs
uplink quality is bad, error packet ratio is high and the target SIR value has reached the
maximum, as a result of the interference or the different coverage scope between the
service channel and the pilot signal channel. In that case, power control cant guarantee
UEs QoS anymore. To avoid call drop, it is necessary to hand over UE to other
inter-frequency cell.
ZTE RNC equipment detects certain users uplink connection. Once the quality of the
connection cant keep the QoS and inner-loop power control has modified the target SIR
to the maximal SIR value allowed, RNC will automatically initiate inter-frequency or
inter-system measure to let UE hand over to an inter-frequency or inter-system cell which
has better quality.
Introduced Version
U9.1&Before
Enhanced Function
No
2.2.3
ZTE develops a unique enhanced Iur-g interface to connect RNC and BSC, with
proprietary messages and the handover procedure to reduce the delay and failure rate of
inter-RAT handover. Through the enhanced Iur-g interface and its procedure, RNC and
BSC can exchange the cell load information to increase the handover success rate. The
enhanced Iur-g procedure parallels the two phases of inter-RAT handover by sending
Radio Resource Prepare message to BSC before handover is performed, as shown in
Figure 2-2. So the BSC can prepare the radio resource in advance. Compared with the
typical inter-RAT procedure, ZTE enhanced Iur-g can reduce the delay by about 200ms
to 300ms.
Target 2G cell information included in Radio Resource Ready message, like NACC
Related Data, cell capacity and Load/RT Load/NRT, is also used in load balancing
strategy of RRM algorithm.
Introduced Version
U9.2
Enhanced Function
No
2.2.4
Introduced Version
U9.1&Before
Enhanced Function
No
2.2.5
2.2.6
This feature shortens the PS service interruption when there is a handover between
inter-RAT adjacent cells. With this feature, PS service continuity is enhanced, especially
for real-time packet service with higher QoS requirements. User experience gets
improved.
Description
Cell reselection procedure is usually executed when UE is moving between GERAN and
UTRAN. But this makes the PS service interruption last for a long time, which will
definitely affect user experience.
Inter-RAT PS handover is applicable for a UE in Cell_DCH state. The procedure of
Inter-RAT PS handover is just like the CS service inter-RAT handover. The message flow
of inter-RAT PS handover is shown as below, with message within CN omitted:
Figure 2-3
UE
RNC
PS CN
RANAP
Relocation
Required
RANAP
BSSMAP
RRC
RANAP
Relocation
Command
BSC
BSSMAP
PS Handover
Request
PS Handover
Request ACK
BSSMAP
BSSMAP
RANAP
RRC
First correctly received
RLC/MAC block
(XID Resp., RAU req.
or Cell Update)
BSSMAP
Iu Release
Command
RANAP
RANAP
Iu Release
Complete
RANAP
RANAP
PS Handover
Complete
BSSMAP
Figure 2-4
UE
RNC
PS CN
Relocation
Request
Relocation
RANAP Request ACK
RANAP
RANAP
RANAP
PS Handover
BSSMAP Required Ack
PS Handover Command
RR
RRC
BSC
PS Handover Required
BSSMAP
BSSMAP
Handover to
UTRAN Complete
RANAP
RRC
RANAP
Relocation
Detect
Relocation
Complete
BSSMAP
RR
RANAP
RANAP
BSSMAP
BSSMAP
Clear Command
Clear Complete
BSSMAP
BSSMAP
Compared with the cell reselection, inter-RAT PS handover decreases both interruption
of data transmission and packet loss rate. And it provides better user experience of
real-time PS service with higher QoS requirements in inter-RAT moving.
Inter-RAT PS handover is not applicable unless UTRAN, GERAN, CN and UE all support
it. Otherwise, either NACC or normal cell change order will be used for PS service to
access an inter-RAT adjacent cell.
Introduced Version
U9.2
Enhanced Function
No
2.2.7
Figure 2-5
UE
RNC
RANAP
CS CN
Relocation
Req uired
BSC
RANAP
BSSMAP
RANAP
PS CN
Relocation
Required
RANAP
PS Handover
Request
BSSM AP
Handover
Request Ack
BSSMAP
BSSMAP
RANAP
RRC
BSSMAP
BSSMAP
Relocation Command
RANAP
Relocatio n Command
RRC
RANAP
RANAP
BSSMAP
Handover
BSSMAP
RR
PS Hando ver
Request Ack
BSSMAP
Detect
7 . Handover Complete
BSSMAP
BSSMAP
RR
BSSMAP
I u Release
Command
RANAP
Handover Complete
BSSMAP
RANAP
I u Release
Co mplete
RANAP
RANAP
Iu Release
Co mmand
RANAP
RANAP
Iu Release
Complete
RANAP
RANAP
PS Handover
Comp lete
BSSMAP
BSSMAP
Figure 2-6
UE
RNC
CS CN
PS CN
Handover Required
BSSMAP
RANAP
Relocation Request
RANAP
BSSMAP
Relocation Request
RANAP
Relocation
R equest Ack.
RANAP
PS Handover
Required
B SSMAP
BSSMAP
R ANAP
RANAP
Relocation
R equest Ack.
RANAP
BSC
R ANAP
BSSMAP
Handover Command
BSSMAP
BSSMAP
PS Handover
Required Ack
BSSMAP
RR
RR
RANAP
Relocation
Detect
RANAP
Relocation
Detect
RANAP
RANAP
Handover to
UTRAN Complete
RRC
R RC
RANAP
RANAP
Relocation Complete
RANAP
Relocation Complete
R ANAP
Without DTM handover, for CS service and PS service in parallel, PS service does not
access inter-RAT cell until CS service completes handover to inter-RAT cell. Obviously,
DTM handover improves inter-RAT handover performance of PS service when CS
service and PS service are in parallel. It also improves user experience.
DTM handover is applicable when both UMTS system and GSM system support DTM
handover, and UE supports PS service inter-RAT handover.
Introduced Version
U9.2
Enhanced Function
No
2.2.8
ZWF21-03-025 NACC
Benefits
This feature shortens the procedure of inter-RAT cell re-selection. It improves the
performance of the package service during inter-RAT moving. As a result, user
experience is enhanced.
Description
When a UE establishes a PS service handover to GREAN via cell reselection procedure,
the interruption of PS service is among 4 seconds to 8 seconds, which brings about bad
user experience. Network Assisted Cell Change (NACC) reduces the duration of UE
inter-RAT cell re-selection procedure.
RNC adds the SI/PSI (System Information /Packet System Information) of the target
GERAN cell in CELL CHANGE ORDER FROM UTRAN message, and transfers the
message to UE. With this information, UE doesnt search the target cells system
information. Consequently, the procedure of the inter-RAT cell re-selection is shortened.
This kind of inter-RAT cell re-selection is NACC.
When an Iur-g connection works normally between an RNC and a BSC, SI/PSI of the
target GERAN cell is transferred to the RNC via Iur-g. Otherwise, the RNC initials
DIRECT INFORMATION TRANSFER message to a CN to request SI/PSI of the target
GERAN cell via the Iu connection, and the CN responses SI/PSI in DIRECT
INFORMATION TRANSFER message.
NACC is used if an RNC gets SI/PSI of the target GERAN cell and UE supports NACC.
Otherwise, inter-RAT cell reselection without network assistance is used.
Introduced Version
U9.2
Enhanced Function
No
2.2.9
This feature increases the success rate of inter-RAT handover and decreases the call
drop rate in inter-RAT handover between UMTS system and GSM system, which
improves user satisfaction.
Description
Without this feature, the load of target cell is not considered in the inter-RAT handover.
When the load of a target cell is high, inter-RAT handover is easy to fail or the quality of
service in the target system cannot get guaranteed.
The Target cell Load based inter-RAT HO enables the RNC, via an Iu connection or an
Iur-g connection, to get load information of GSM adjacent cell, or transfer load
information of UMTS adjacent cell to GSM system. The RNC selects a GSM adjacent cell
with lower load as target cell to perform handover to the GSM system.
When an Iur-g connection works normally between an RNC and a BSC, the Iur-g is
preferred to be used to exchange load information. Otherwise, the load information is
exchanged in relocation procedure via the Iu connection.
RNC will periodically update the load of adjacent GSM cells, to guarantee the availability
and correctness of adjacent cells load information.
This feature is applicable when the UTRAN, Core Network, GSM network and UE all
support it.
Introduced Version
U9.2
Enhanced Function
None
2.2.10
Description
When a PS service user leaves LTE network to UMTS network, PS service handover
from LTE to UMTS is needed to keep service connectivity continuity. The handover is
initialized via relocation required from E-UTRAN to core network. When UTRAN receives
relocation request, it allocates resource for the UE and waits for UE accessing. For a
LTE-capable UE is ongoing PS service in UMTS and enters the coverage of LTE, it is
recommended to handover to LTE for high bit rate service experience in LTE. UTRAN
initials relocation required message to core network to start handover. When UTRAN
receives relocation command message, it informs the UE handover to E-UTRAN
neighbor.
Signal flow for PS service handover form UTRAN to E-UTRAN is shown in the figures
below.
Figure 2-7
UE
Target
Source
Target
RNC
eNodeB
SGSN
MME
Handover Initiation
Relocation Required
Forward Relocation
Request
Handover request
Handover Request Acknowledge
Forward Relocation
Response
Relocation Command
Handover from UTRAN
Command
E-UTRAN access procedure
Handover to E-UTRAN Complete
Handover Notify
Forward Relocation
Complete Notification
Forward Relocation
Complete Acknowledge
Iu Release Command
Iu Release Complete
Signal flow for PS service handover form E-UTRAN to UTRAN is shown in the figures
below.
Source
Target
Source
Target
eNodeB
RNC
MME
SGSN
Handover Initiation
Handover Required
Forward Relocation
Request
Relocation Request
Relocation Request Acknowledge
Forward Relocation
Response
Handover Command
Handover from E-UTRAN
Command
UTRAN access procedure
Handover to UTRAN Complete
Relocation Complete
Forward Relocation
Complete Notification
Forward Relocation
Complete Acknowledge
Release Resource
This feature includes dual direction handover between UMTS and LTE, and it is applied
in only PS service scenario.
Introduced Version
UR11.1
Enhanced Function
No.
2.2.11
ZWF21-03-120 SR-VCC
Benefits
This feature maintains IMS VoIP call when the LTE coverage gets worse, and allows
making use of CS domain in UMTS network for bearing voice call.
Description
SR-VCC provides the ability to transition a voice call from the VoIP/IMS packet domain to
the legacy circuit domain. Voice call is allowed to be provided to user only when IMS
network elements are deployed in LTE network. Then a user is ongoing voice call and
the E-UTRAN coverage gets worse, via SR-VCC, the user is transited to UMTS network
and the voice call is carried by circuit domain in core network,
In case of a user establishing voice call and packet data service both in LTE network,
SR-VCC mechanism can also be used to transit user form LTE network to UMTS
network. When the user completes accessing in UMTS network, the voice call is serviced
by circuit domain core network, and the packet data service is serviced by packet domain
core network.
The signaling flow for SR-VCC during voice call and data service in combination is
shown in figure below.
MSC Server/
MGW
Source
MME
Source
E-UTRAN
UE
Target
SGSN
Target
RNS/BSS
SGW
IMS
(SCC AS)
1. Measurement reports
2. Decision for HO
3. Handover Required
4. Bearer Splitting
5a. PS to CS Req
5b. Prep HO
Req
6a. Forward Reloc Req
15. UE tunes to
UTRAN/GERAN
16. HO Detection
17a. Reloc/HO Complete
17b. SES (HO Complete)
17c. ANSWER
17d. PS to CS Complete/Ack
17f. TMSI Reallocation
17e. UpdateLoc
HSS/
HLR
Introduced Version
UR11.1
Enhanced Function
No.
2.3
2.3.1
This feature supports the dynamic AMR adaptation according to the uplink transmission
power of the UE or the downlink transmission power of the base station. And in case of
an admission failure or a handover failure, the AMR rate is also adjusted to guarantee
that maximal services can access the system. It is useful for increasing the number of
voice users in the system and enhancing the coverage of a voice service in the case of
the radio link quality degrading.
Description
In the UMTS system, the radio environment between UE and a base station always
changes. When a UE is far away from the base station or the radio environment
degrades, the base station or the UE will transmit at a higher power under the action of
the closed-loop power control in order to guarantee the QoS of the AMR service. The
power change and the power increase at this time may result in a sharp increase of the
power and further deterioration of the radio environment. Even when the power is
increased to the maximum value, QoS requirements of service cannot be satisfied. As a
result, the system capacity will decrease.
ZTE RAN monitors the uplink transmission power of the UE reported by internal
measurement or the downlink transmission power of a Node B reported by dedicated
measurement. When the uplink or downlink transmission power rises to a certain
threshold, the RNC will automatically adjust this user's AMR to reduce the power
necessary for service. That is, a conversation is most probably kept at the cost of
reducing voice quality. When the radio environment between the UE and the base station
is good and the transmission power of the base station or the UE decreases to a certain
threshold, AMR can be increased to provide users with better voice quality as long as
other users' feeling and system performance are not affected.
When a cell has high downlink load and uplink load, which is evaluated by means of the
downlink transmission power and the uplink interference respectively, ZTE RAN can
lighten the cell load by reducing the AMR of some low-priority users. In this way, more
users can be accommodated.
Considering the call quality of the AMR service, ZTE RAN always allocates the highest
bit rate supported by the AMR call and the system resource correspondingly. When the
system is congested, an AMR call, which requests a new establishment or handover to
access the current cell, is refused to access the system. At the moment, ZTE RAN
decreases the allocated bit rate of the AMR call to reduce the required resource. It makes
it easier for the AMR call to access the system. At the same time, congestion control (pls
refer to feature ZWF21-04-010 Congestion Control) is triggered to recover the system
from congestion. Consequently, the success rate of AMR call establishment is increased
and the user satisfaction is improved.
If the load of a cell is a little bit higher, the bit rate of voice call (including NB-AMR and
WB-AMR) is allowed to be restricted. It means a low bit rate is assigned to voice call.
Some area such as stadium is crowed sometimes. So when RAN detects the load of
cells belonging to these area getting higher than the pre-defined threshold, RAN restricts
the AMR voice call to a level to ensure more users accessible.
The actual AMR coding rates which can be adjusted by the RNC must belong to the AMR
code set configured for users by the CN during the call establishment. The voice quality
with low-rate AMR coding is not as good as that with high-rate AMR coding, but low-rate
AMR coding has higher capacity (number of users) and wider coverage than high-rate
AMR coding. Analysis of simulation result shows that there is about 30% coverage radius
gain when the lowest AMR (4.75Kbps) instead of the highest AMR (12.2Kbps) is used.
When the lowest AMR is used, a cell will accommodate twice as many users as those
when the highest AMR is used.
Introduced Version
U9.1&Before
Enhanced Function
This feature supports AMR rate adjusting in case of admission failure or handover failure
in release U9.2.
In release U9.3, the restriction to voice call bit rate based on cell load is introduced.
2.3.2
This feature allows the operator to configure a power control policy according to the
priority of the user so that the QoS of high-priority users in areas with poor network
quality can be guaranteed.
Description
Sometimes, the transmitting power of a terminal is so strong as to interfere with other
terminals, or the transmitting power of the base station targeting at a user occupies too
many downlink power resources. To avoid such event, the RNC needs to configure the
maximum uplink/downlink transmitting power allowed for each user. The ZTE RAN
supports configuring the maximum uplink/downlink transmitting power for various
services based on the priorities of these services so that users of high priority can obtain
more system resources and the QoS of users with high priority can be guaranteed even
though the network quality is poor, thus realizing differentiated QoS policy.
Introduced Version
U9.1&Before
Enhanced Function
No
2.4
QoS Guarantee
2.4.1
This feature provides service suspension parameters for each cell through the NMS.
Through the feature, the system can suspend specified services for specified cells. After
a service is suspended in an area, if the user initiates the service, the RNC indicates
RAB setup failure for the CN during the service setup process. If a connection has been
set up for a service, it is prohibited to hand over the service to the area where the service
is prohibited. If the CN and the UE support the feature, when the video call service is set
up or is handed over to the area where the service is closed, the RNC may roll back the
video call service into a common voice service. In this case, it is necessary to configure
the function ZWF21-05-024 video call fallback to voice call.
Introduced Version
U9.1&Before
Enhanced Function
No
2.4.2
a lower level rather than simply rejects the service. It can improve the success rate of
access and improve the customer satisfaction.
If the RNC sets up a bearer using the parameters in the Alternative RAB Parameter
Values rather than the MBR and GBR in RAB parameters assigned by the CN, the RNC
notifies the CN of the actual MBR and GBR after the completion of the bearer setup so
that the CN knows the actual capability of the bearer and bills the user on basis of the
bearer capacity.
The RAB QoS renegotiation is based on the system resource utilization. If the load of the
system is very low, the system can provide better services for the user through
negotiation; if the load of the system is very high, the system can adopt lower bit rate
through negotiation. In this way, the system can effectively utilize the resources and
serve more users.
The RAB QoS negotiation can be triggered in two modes:
Introduced Version
U9.1&Before
Enhanced Function
No
2.4.3
Handover to GSM should not be performed: it means that the service will have
to hand over to GSM in the case that UMTS cannot carry the service, and RNC
will trigger inter-RAT handover in the case UMTS quality degrading.
Handover to GSM shall not be performed: it means that this kind of service can
neither be handed over to GSM nor trigger a handover to GSM.
Regarding concurrent services, RAN network can combine service handover of multiple
services based on the priorities of service handover configured via OMC. For example,
one operator wants to have CS service in GSM network and PS services kept in WCDMA
network as long as possible. The configuration of service handover for CS service can be
Handover to GSM should be performed, and the configuration of service handover for
PS service can be Handover to GSM should not be performed. Also Handover to GSM
should not be performed should have a higher priority than Handover to GSM should be
performed. Based on this configuration, while one UE has concurrent services of CS
voice and PS data, WCDMA network is still selected to provide both CS and PS services
for the user in order to guarantee PS servie experience. CS service can not be handed
over to GSM network until PS service is released.
In reality, the load of GSM cell is high in some hot spots. If service based handover is
enabled and the load of GSM cell is not considered, it brings more load to GSM cell. To
avoide this, a configurable switch per cell is provided to disenable service based
handover. When the switch is set to be off, the attribute service handover is not
checked by RAN.
After introduction of LTE, information element of E-UTRAN Service Handover in RAB
assignment message is also introduced to indicate whether a UE could be handed over
to LTE. ZTE RAN can abbey the indication in the information element from CN.
Handover strategies based on services actually need to be configured in CN.
Introduced Version
U9.1&Before
Enhanced Function
The
priority
for
attribute
service
handover,
and
service
based
handover
2.4.4
UE
Node B
Serving RNS
Serving
RNC
RANAP
RANAP
NBAP
NBAP
NBAP
1. RAB Modification
Request
RANAP
2. RAB Assignment
Request
RANAP
[Modification]
NBAP
RRC
RRC
CN
RRC
7. DCCH: Radio Bearer Reconfiguration Complete
RRC
RANAP
8. RAB Assignment
Response
RANAP
The video call service, as a special feature in UMTS system, has been applied
extensively. But the GSM system cannot provide the video call service. As a result, the
video call service in the UMTS network cannot be switched to the GSM system. If the
video call service has to be switched to the GSM system, it may be interrupted forcedly.
This feature enables the system to roll back from the video call service to AMR service
and then implement handover from the 3G system to the 2G system, thus ensuring the
continuity of the voice service.
The implementation of the feature requires the cooperation from the CN and UEs that
support the SCUDIF function.
Introduced Version
U9.1&Before
Enhanced Function
No
2.5
2.5.1
SA mode
RNC reports the SA ID (SAI) of the cell where the UE camps to CN.
GA mode:
When there is no information about accuracy in the location request, the
coverage information (usually pre-configured in OMC) of the cell where the UE
camps is reported.
When accuracy requirement is indicated to be greater than a specific value
(usually 100 meter), cell ID + RTT method is used, which means UE position is
determined by Time of Arrive (TOA). Round Trip Time (RTT) is the time
difference between the start of a downlink frame and the reception of the
corresponding uplink frame. TOA can be derived by the NodeB RTT
measurement and the UE Rx-Tx time difference measurement. Type 2
measurement on UE Rx-Tx is adopted with priority Type 1 is used if UE does
not support type 1.
Cell ID + RTT positioning has an accuracy of 80-100m. But it requires that Node B should
support RTT measurement. Otherwise, only cell ID positioning is used.
According to the location request from CN, RNC reports position results immediately or
when SA where UE resides changes.
Introduced Version
U9.1&Before
Enhanced Function
No
2.5.2
ZWF21-10-002 AGPS
Benefits
This feature provides high-accuracy position service with large coverage, rapid location
and quick response.
Description
To use the A-GPS location service, the UE and radio access network must support GPS.
Compared with the traditional GPS, A-GPS system sends GPS location reference
information (encapsulated in system broadcast SIB15 or measurement control message)
from the network side to the mobile UE to help it acquire satellite signal and
measurement code phase information quickly. Therefore, A-GPS locates UE quickly with
rapid response, reducing power consumption of the UE.
A-GPS positioning methods are classified into two modes: UE-assisted (UE-A) and
UE-based (UE-B).
In the UE-A A-GPS location method, location calculation is achieved by the Service
Mobile Location Center (SMLC) at the network side. UE reports measurement results of
the satellite signals and code phase information to the RNC at the network side. The
RNC transmits the measurement results to the SMLC through the Iu-PC interface. The
SMLC then calculates the mobile location based on the measurement results and finally
reports the calculation result to the CN through the RNC. In the UE-B A-GPS method,
2.5.3
service in UMTS system is not high, UMTS system redirects emergency call to 2G
network. Then the location of the user is got via 2G networks location service.
When the Flag related to Emergency Call Re-direct to GSM is on, if a UE transfers RRC
CONNECTION REQUEST message with a cause of Emergency Call, and the cell where
the message is received has more than one co-located GSM adjacent cell, ZTE RAN
responds RRC CONNECTION REJECT message with the co-located GSM cell
information to the UE. Then the UE performs inter-RAT cell reselecting to the GSM cell
and makes an emergency call again. User does not feel the procedure of re-direction to
GSM, and it seems that the emergency call is launched in GSM network originally.
Introduced Version
U9.2
Enhanced Function
No
2.5.4
Enhanced Function
No
2.5.5
When the best cell is in the DRNC, SRNC obtains the location information of the
reference cell through iur information. For the Cell ID+RTT, SRNC needs to start
the RTT measurement on DRNC side through Iur common measurement
procedure.
UEB AGPS
When the best cell is in the DRNC, the SRNC obtains the accessory GPS
information of the reference cell on the DRNC side through initiating Iur information
exchange procedure
Enhanced Function
No
2.6
RAN Management
2.6.1
Introduced Version
U9.1&Before
Enhanced Function
No
2.7
2.7.1
ZWF21-30-021 Iu Flex
Benefits
This feature supports that one RNC can be connected to multiple MSC Servers/SGSNs
and these MSC Servers/SGSNs are combined into a pool to provide redundancy so as to
improve the network security, helping to achieve load balance between MSC
Servers/SGSNs and reducing waste of hardware resource and signaling overhead.
Description
The Iu Flex is a networking technology in the 3GPP R5 version. This networking mode
eliminates the restriction that one RNC can be connected to only one MSC Server/SGSN
in a traditional network. In the Iu Flex networking, one RNC can be connected to multiple
MSC Servers/SGSNs, and these MSC Servers/SGSNs are grouped to a pool area which
provides services to the RNC. As shown in Figure 2-11, a pool area is set according to
different CN domains. All the connected CS CN nodes constitute a CS pool area, and all
the connected PS CN nodes constitute a PS pool area.
MSC 6
MSC 5
MSC 1
MSC 4
MSC 7
CS poolarea 2
CS poolarea 1
RAN
node
Area 1
RAN
node
Area 2
RAN
node
Area 5
RAN
node
Area 3
RAN
node
RAN
node
Area 7
PS pool-area 1
Area 8
PS pool-area 2
SGSN 3
SGSN 2
Area 4
RAN
node
Area 6
SGSN 1
RAN
node
SGSN 6
SGSN 4
SGSN 5
Compared with traditional networks, the networking based on the Iu Flex technology has
the following advantages:
then the coverage of a single MSC Server/SGSN will be small. When UEs
move between the different CN nodes frequently, there are many signalings of
the LA/RA update, handover, relocation and the exchange of the HLR
parameters. With Iu Flex networking, a subscriber within one pool area can
enjoy his/her services provided by a specific MSC Server/SGSN, and need not
change serving CN node when moving within the pool area. So signaling load
caused by mobility is decreased significantly and the system capacity and the
network performance also get improved effectively.
ZTE RAN supports Iu Flex networking, that is multi MSC Servers/SGSNs can be
connected to one RNC. Network Node Selection Function (NNSF) is used to select a
serving CN node among multi CNs when a subscriber accesses the network or the
network pages a subscriber:
When users initiate attach procedure or LA/RU update procedure, RNC will
select CN node based on NRI configuration and IDNNS information to
establish a signaling connection, which reduces signaling interaction of
mobility between CN nodes.
When a user has a terminated call, the RNC will buffer the CN node
identification for utilization in future paging procedure to select a correct CN
node.
ZTE RAN equipment can recognize CN ID (Global CN-ID) in RANAP procedure of SRNS
relocation, the CN reset, the resource reset and the overload in the case of Iu Flex
networking, and it only processes messages from some specific CN nodes.
ZTE RAN equipment supports the combining of MBMS service of multiple SGSNs in the
case of Iu Flex networking.
Introduced Version
U9.1&Before
Enhanced Function
No
2.8
2.8.1
Figure 2-12
CN
O perator A
CN
O per ato r B
CN
O perator C
Iu
RNC
N ode B
N o de B
Figure 2-13
CN
Op erator A
CN
O perator B
S hared
MSC/SGSN
Shared
MS C/S GSN
CN
Op era tor C
S hared
MSC/SGSN
Iu
RN C
RN C
R NC
In this network sharing mode, the operators share the same CN network (such
as MGW, MSC server, and SGSN) as the network gateways and connect to
their respective HLR, GGSN, GMSC, GMGW, and billing & accounting
system.
ZTE UTRAN supports flexible UTRAN sharing deployment. Part of RNS could be set not
shared or shared by different operators from other parts. Iu Flex also can be activated to
MSCs of one or several operators.
Introduced Version
U9.1&Before
Enhanced Function
No
2.8.2
Figure 2-14
Operator one
Operator two
Shared RNC
Shared Node B
Frequency one
Frequency one
MNC
one
Frequency two
Frequency two
MNC
two
The frequencies of different operators can be distinguished according to the PLMN code
in the broadcasted system information. Through the broadcasted information of each
carrier, UE can identify the networks of different operators, camping on and accessing to
carriers with its home PLMN or authorized PLMN, and displaying the logo of the operator.
According to the access frequency of the UE, RNC routes signaling connection and
service to the respective CN. RAN sharing with dedicated carrier is transparent to UE
and UE neednt know whether the cells of various PLMNs use the shared resources.
Therefore, the UEs of all protocol versions can access the shared network and enjoy
respective services provided by the operators.
When ZTE RNC works in dedicated carrier sharing situation, a physical RNC can be
regarded as several virtual logical RNCs, and each logical RNC belongs to an operator.
The shared RNC can connect to not only shared Node Bs or shared RNCs, but
non-shared Node Bs or non-shared RNCs as well. When the shared RNC connects to
different operators CN, each operator also can deploy Iu flex for MSC/SGSN pooling
purpose.
When ZTE RNC works in dedicated carrier sharing situation, it distinguishes subscribers
from each operator by the cell they are connected with in shared or non-shared Node Bs
controlled by itself or other shared RNCs or non-shared RNCs. RNC ensures that users
can only access their own operators cells and users service continuity among those
cells.
RAN sharing with dedicated carrier is applied to both MOCN and GWCN modes.
Introduced Version
U9.1&Before
Enhanced Function
No
2.8.3
measurement,
inter-frequency
measurement,
and
inter-system
measurement according to the SNAC. Only the authorized SNAs cell can be included
into the new adjacent cell list (for measurement control) so that the UE can only hand
over within the authorized cells.
Each cell is labeled with some authorized PLMN IDs in ZTE RNC, which means
subscribers belonging to those PLMNs will be able to access in the cell. If there is no
SNA information from CN, ZTE RNC will filter target cells for a user during its handover
based on authorized PLMN IDs of each neighboring cell. Therefore, the user will not
move to cells not belonging to its authorized network.
Introduced Version
U9.1&Before
Enhanced Function
No
2.8.4
Most of those functions can be configured in RNC level based on PLMN and
differentiated applied to different subscribers belong to different operators. Still few
RNC level optional functions only support same configuration to all operators and
cannot be purchased separately.
All of those functions are configured in cell level and can be applied to different
subscribers belong to different operators in dedicated carrier network sharing
scenario, which means if different operators have different frequencies then those
functions can be purchased and configured separately.
All of those functions are applied to physical equipment but not to single subscriber,
like transmission function. Since physical equipments are shared when network
shared, those functions are shared as well and cannot be purchased and
configured separately.
Operator specific function control is implemented via license control mechanism of ZTE
RAN. Different operators can purchase different licenses in shared RAN, activating and
operating optional features separately.
Introduced Version
U11.1
Enhanced Function
No
2.8.5
No
2.8.6
ANI+Path+PLMN1
PathGroup
ANI+Path+PLMN1
ANI+Path1+PLMN2
ANI+Path1+PLMN2
Node B
RNC
ANI+Path1+PLMN3
ANI+Path1+PLMN4
ANI+Path+PLMN_MIX
ANI+Path1+PLMN3
ANI+Path1+PLMN4
ANI+Path+PLMN_MIX
2.8.7
2.8.8
This feature enables operator to independently manage the cell-level FM/PM/ CM, that
is:
Independent CM
In dedicated carrier network sharing scenario, different operators can
independently configure the parameters related to the cell which belongs to
only one operator. For example, different operators own dedicated SW
(software) function and feature differentiation can be embodied in cell-level
configuration. In shared carrier network sharing scenario, part of RNC level
parameters also can be configurable for each operator.
Independent PM
For those counters related to cells, performance statistics can be done based
on operator. The operator dedicated results of performance statistics can only
be accessed by their own PM Managers, for example, differentiate the
counters related to the networks KPI from different operators, and
independently manage their own measurement objects. Not all but only some
KPI related counters can be differentiated among operators in shared carrier
network sharing scenario.
Independent FM
Fault management can differentiate the cell-level alarms for different operators.
The fault alarm corresponds to only one operator so it can only be accessed
and processed by their own FM managers.
Introduced Version
U9.2
Enhanced Function
No
2.8.9
The feature provides baseband CE resources sharing by different operators when they
sharing RAN. And the proportion occupied by each operator is configured by OMC. This
feature can make the Node B hardware utilized sufficiently, reducing the CAPEX and
OPEX of operators.
Description
There are two ways to realize CE resources sharing by multi-operators: one is
multi-operators sharing CE resources in the same baseband pools, the other one is
multi-operators occupy different baseband pool independent in the same BBU. ZTEs
RAN support both the two ways.
ZTE support at most 6 cells in one baseband pool, and one baseband pool includes 1 to
5 baseband boards, and one baseband board only belongs to one baseband pool. The
CE proportion belongs to each operator can be configured by OMC when cells of
multi-operators configured in the same baseband pool or in different baseband pools.
And then the division of CE resources between operators by proportion can be realized.
In the shared carrier scenario, there must be a master operator, who pays for the whole
CE capacity of the network. Other operators rent the CE capacity from the master
operator. Thus this is a different CE configuration requirement from the dedicated carrier
sharing scenario. Only the total number of CE in Node B is controlled by the license,
partitioning of CE is done in RNC.
This feature doesnt support the deployment of both dedicated carrier and shared carrier
UTRAN sharing in the same Node B. But for the RNC, it supports that part of Node Bs
are in dedicated carrier UTRAN sharing mode, part of node Bs are in shared carrier
UTRAN sharing mode, and part of Node B are not shared.
Node B level configurable parameters are added to allocate the dedicated CE resource
percentage for each operator dedicated carrier RAN sharing mode and unallocated CE
resource could be shared by all operators. In the shared carrier mode, the whole Node B
carriers constitute a frequency pool and CE resource percentage for each operator is
configured in the RNC. For the reason that the CE resource can only be shared inside
one local cell group in ZTE Node B and cannot be shared across local cell groups, CE
usage percentage configured for one Node B in the RNC will be applied to all local cell
groups in the Node B.
Introduced Version
U9.2
Enhanced Function
No
2.8.10
the neighbor cells with higher priority are selected to send to the UE, due to the lack of
authorization information of the UE. In the UE connected state, SNAC based neighbor
cell selection is applied.
Introduced Version
U11.1
Enhanced Function
No
2.8.11
Description
ZTE RAN supports the configuration of different PLMNs to different cells. If a UTRAN is
shared by different operators, different PLMNs can be used to distinguish from different
operators.
If an operator owns several PLMNs, it can deploy different cells with different PLMNs at
the airports, piers, coach terminals and tourist spots where many inter-operator roaming
users enter. In the roaming area of a non-HPLMN coverage area, the UE will select a
new PLMN to register when it powers on. The PLMN belongs to a roaming partner
operator. During the process, the UE may automatically select a cell with the best access
radio quality, or the UE may indicate to the user a list of available PLMNs whose cell
radio quality is good enough to access and the user then makes the selection.
Configuration of more PLMNs is beneficial to increase the probability of network to be
selected by roaming users. Meanwhile, the RAN device of ZTE also supports the mobility
management among different PLMNs so that after a user selects a PLMN of the operator,
he may then switch over to a cell with another PLMN of the same operator to continue
the service.
Introduced Version
U9.1&Before
Enhanced Function
No
2.9
2.9.1
For UEs with 3GPP R6 RAN sharing capability, ZTE RNC routes them to CN
nodes with the same PLMN ID indicated in RRC connection request message
sent from those UEs.
For international roaming uses, ZTE RNC can set the percentage for different
operators to define the possibilities to be the first-chosen-CN, which helps to
allocate roaming users to different operators. In the UTRAN sharing
deployment, multi operators can give service to the roaming subscribers
according to the percentage agreed among the operators.
When ZTE RNC works in carrier sharing situation, a physical RNC is regarded as some
logical RNC for the operators which share the physical RNC. Each logical RNC belongs
to an operator. The shared RNC can connect to not only shared Node Bs or shared
RNCs, but non-shared Node Bs or non-shared RNCs as well. When the shared RNC
connects to different operators CNs, each operator also can use Iu flex for MSC/SGSN
pooling purpose.
When ZTE RNC works in carrier sharing situation, it can distinguish each operators
subscribers in shared or non-shared Node Bs controlled by itself or other shared RNCs
or non-shared RNCs. RNC ensures that subscribers of an operator can access in the
area of its authorized operator and the subscribers service continuity among cells in
those areas.
Since UE can only obtain the common PLMN code through the system message, the CN
can use the NITZ function (3GPP TS22.042) to force terminals to display operators logo.
After location updating succeeds, the network informs the UE of the operator's logo.
Introduced Version
U9.2
Enhanced Function
No
2.10
Radio Part
2.10.1
Enhanced Function
No
2.10.2
Track the transmitting power of antenna and map the output power of PA
Check the table with the output power of PA to find the drain voltage needed
Map the drain voltage to state machine of power module and then choose
appropriate output voltage of power module to meet traffic load
30
P A efficiency(% )
25
20
fix ed volta ge P A effic ie nc y
a djus te d voltag e P A e ffic ienc y
15
10
10
15
20
25
30
35
outp ut po we r(W )
40
45
50
55
As shown in Figure 2-16, with D-PT technology, it is obvious that gain of PA efficiency
can be achieved to save operation cost and enhance equipment stability.
Introduced Version
U9.1&Before
Enhanced Function
No
2.10.3
throughput of another carrier will be increased to improve the system capacity. Power
shared ratio can be configured by OMC.
Multi-carrier dynamic power sharing includes two scenarios:
Scene a: R99+ (R99+DPA). In this instance, the DPA cells can use the
remaining sharing power from R99 cell;
Scene b: (R99+DPA) + (R99+DPA). In this instance, the DPA cells can use the
remaining sharing power with each other.
In order to implement the sharing between each scheduler, the logic entity of the super
DPA scheduler which is independent of the present DPA scheduler to distribute the
sharing power will be introduced. Node B will notify the maximum transmitting power of
the local cell and the local cell group, and the relationship between the local cell and the
local cell group to RNC by auditing response. According to the acquired information and
Node B measurement information, RNC will execute the power admission control to
Node B.
Additionally, the power configuration principle of three-carrier power sharing is described
in the followings:
During the distribution, the sum of three carriers power keeps unchanged. Any
distribution will always make the sum of three carriers power equal to the
initial value.
The power distribution principle is the same as the one of dual-carrier. The big
step of step_1 (1w) extracted by the carrier that reports -1 and the small step
of step _2 (0.5w) extracted by the carrier that reports 0 will be used for the
carrier that reports 1.
Introduced Version
U9.2
Enhanced Function
No
2.10.4
2.
ii.
ii.
iii.
iv.
3.
4.
ii.
5.
ii.
Transmit diversity
iii.
When cell coverage reaches 80km, only one carrier sector is allowed in one base band
hardware board,
Large scaled coverage has some requirements on the height of antenna. For instance,
when the altitude of UE antenna is 3m, the height of antenna of base station needs to be
about 310m (2.1GHz) or 250m (900MHz) to meet the requirement of 80Km.
Introduced Version
U9.1&Before
Enhanced Function
No
2.10.5
This feature can be used for reducing attenuation, improving performance of radio uplink
and enhancing uplink coverage.
Description
Compared with dual-antenna receiving diversity, Four Antennas receiving can reduce
uplink attenuation further and theoretically increase receiving sensitivity by 3dB
corresponding to 20~30% coverage area increased.
Mechanism of Four-Antenna Receiving Diversity is shown in Figure 2-17.
RF Unit1 (RRU
Antenna 1
U
E
Antenna 2
Antenna 3
Antenna 4
RF
process
RF
process
RF
process
Finger
demodulation
RF
process
MRC
Symbol
level
process
RF Unit 2(RRU
2.10.6
Table 2-1
Closed-loop Transmit
Diversity
Diversity
STTD
Mode 1
P-CCPCH
SCH
S-CCPCH
DPCH
F-DPCH
PICH
MICH
HS-PDSCH
HS-SCCH
E-AGCH
E-RGCH
E-HICH
AICH
Figure 2-18
ANT2
ANT1
R&T
R&T
RRU/RSU
RRU/RSU
DF
T
DF
R
RTR+PA
R
RTR+PA
BBU
In open-loop transmit diversity mode, the terminal doesnt provide the Node B with the
feedback information, which is to reduce complexity of mobile station. In closed-loop
transmit diversity mode, terminal sends feedback information to the Node B to make
antenna transmit signal adjust to the current channel environment so as to achieve better
transmission performance in low-speed mobile environment.
Introduced Version
U9.1&Before
Enhanced Function
No
2.10.7
Adjust the down tilt angle of the electrical tilt antenna without switching off the
power. Detect the down tilt angle real time.
The down tilt angle of the antenna can be adjusted remotely without operator.
Weather, time and Node B location have no affect on the tilt operation of the
antenna.
Description
This function is used to adjust the down tilt angle through the remote or local control
software. It is achieved through changing the phase of multi-element antenna array and
adjusting the field amplitudes of the vertical and horizontal vectors. The electrical tilt
antenna control unit is integrated into the Node B internal rack. The operator can adjust
and detect the down tilt angle of an antenna through the RET software in the remote O &
M center, and it is shown in Figure 2-19. The electrical tilt antenna is widely used in radio
coverage system. And compared with the traditional antenna system, it has many
advantages.
m
Software of
Electrical Tilt
Antenna
Downtilt angle
n
O&M
Node B
Remote electrical tilt antenna allows the system to adjust the down tilt angle in directional
pattern without powering off. Therefore, the antenna can be detected and adjusted in real
time, regardless of weather, geographic environment, etc. Its step precision in angle
adjustment is high (0.1). Thus the remote electrical tilt antenna can be used to adjust the
network precisely, shortening the network construction and reducing the maintenance
cost.
ZTE RAN equipment supports the main functions of Electrical tilt antenna:
One RRU can control a maximum of three electrical tilt antennae to control the
motor
AISG has two protocol versions: ASIG1.1 and ASIG2.0. ASIG2.0 is written into 3GPP R7,
i.e., Iuant interface (electrical tilt antenna and tower amplifier standard control interface).
ZTE RAN equipment supports ASIG1.0 and ASIG2.0.
Introduced Version
U9.1&Before
Enhanced Function
No.
2.10.8
Benefits
preamble processing technology. The base station can cover a distance up to 120km.
When cell coverage reaches 120km, only one carrier sector is allowed in one base band
hardware board. To provide 120km remote coverage, the height of antenna should be
750m (2.1GHz frequency band) or 700m (900MHz frequency band).
Introduced Version
U9.1&Before
Enhanced Function
No
2.10.9
Enhanced Function
No
2.10.10
RAN
system
will
implement
the
interference
cancellation
of
Supporting twice demodulation for 2ms E-DPDCH. Being failed with the first
decoding, the scheduler can proceed further scheduling for this TTI to greatly
improve E-DPDCH decoding success rate.
Additionally, having introduced HSUPA 16QAM, the higher SNR exists in the uplink
when UE signal arrives at the receiver antenna (Because the SRN threshold of 16QAM
modulated signal is greatly bigger than QPSK signal). In this case, in order to conquer
the noise which is the interference noise signal brought by 16QAM relative to the UE
signal using QPSK, other UEs need to accordingly increase transmission power to be
satisfied with the requirement of SNR demodulation threshold.
In this case, the interference cancellation technology requires combining advanced
receiver to reduce QPSK demodulation threshold, increase cell system capacity and cell
coverage. For the terminal, the transmission power and power consumption can be
reduced and the battery life is extended.
Introduced Version
UR11.1
Enhanced Function
No
2.10.11
Finger Process
w1*
Finger 1
Channel delay
d1
Spreading waveform
correlator
y(d1 )
Finger 2
r (t )
Channel delay
d2
Spreading waveform
correlator
y(d 2 )
w2*
Finger N
Channel delay
dN
Spreading waveform
correlator
y (d N )
w*N
The traditional RAKE receiver which is equivalent to the optimal matching filter under
White Gaussian Noise will process the interference and the noise as white noise.
However, when WCDMA uplink achieves high speed, the traditional RAKE receiver is not
an optimal matching filter any longer. However, the A-RAKE receiver can process the
interference as the colored noise and utilize the correlation between the interference of
extra fingers and the multi-path interference to cancel partial multi-path interference and
achieve the effect of whiting colored-noise (interference). Consequently, the receiving
SNR (ratio of signal to noise) can be increased to get better performance.
Introduced Version
UR11,1
Enhanced Function
No
2.10.12
Enhanced Function
No
2.10.13
3.1
3.1.1
Table 3-1
Service Types
Bit Rate
Connection Type
Type A
Constant
Type B
Type C
Variable
Connection oriented
Connectless
AAL 3
Types of
AAL
AAL 1
Type D
AAL 4
AAL 2
AAL 5
Examples of
Services
Circuit
simulation
Video
Connection
Connectless
oriented data
Data
ATM network QoS including transmission delay, jitter and package loss and so on. In the
original categories of ATM QoS, there are four kinds which are CBR, VBR, ABR and
UBR, and later UBR+ is added.
Table 3-2
Bandwidth guarantee
Applicable to realtime
communication
CBR
rt-VBR
nrt-VBR
Yes
Yes
Yes
Optional
No
Yes
Yes
Yes
No
No
No
No
No
No
Yes
Yes
Yes
Yes
No
No
No
Yes
No
No
ABR
UBR
UBR+
Applicable to
non-realtime
communication
Any feedback on
congestion
ATM is adopted as the main protocol for interfaces between UTRAN NEs in 3GPP which
specifies AAL2 as the bearer of Iu CS IuUP and Iub/Iur FP and AAL5 as the bearer of
application layer protocol of terrestrial interface and Iu PS data.
ZTE RAN equipment supports complete ATM protocol stack in Iub interface, Iur interface,
IuCS and IuPS interface, which is shown in the following Figure 3-1,
, , .
Radio
Network
Layer
Radio
Network
Layer
Control Plane
User Plane
RANAP
Iu UP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
Q.2630.1/2
SCCP
Q.2150.1
MTP3B
MTP3B
SSCF -NNI
SSCF-NNI
SSCOP
SSCOP
AAL5
AAL5
AAL2
ATM
ATM
ATM
Physical Layer
Radio
Network
Layer
Control Plane
User Plane
RANAP
Iu UP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
SCCP
MTP3B
GTP-U
SSCF-NNI
UDP
SSCOP
IP
AAL5
AAL5
ATM
ATM
Physical Layer
Radio
Network
Layer
Control Plane
User Plane
RNSAP
Iur FP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
Q.2630 .1/2
SCCP
Q.2150.1
MTP3B
MTP3B
SSCF-NNI
SSCF-NNI
SSCOP
SSCOP
AAL5
AAL5
AAL2
ATM
ATM
ATM
Physical Layer
Radio
Network
Layer
Control Plane
User Plane
NBAP
Iub FP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
Q.2630 .1/2
Q.2150.2
SSCF-UNI
SSCF-UNI
SSCOP
SSCOP
AAL5
AAL5
AAL2
ATM
ATM
ATM
Physical Layer
ATM can be based on various types of physical transmission media. The external ATM
transmission interfaces supported by ZTE RAN equipment mainly include E1, T1 and
SDH (STM-1, CSTM-1) (see the detailed description of corresponding interfaces). E1
and T1 interfaces are used in scenarios with low bandwidth requirements, for example,
NEs are directly connected through lub or lur interfaces. CSTM-1 is used to implement
multiplexing and convergence of several E1/T1 low-speed links in STM-1 signals and
primarily used in the case that transmission convergence equipment is used in Iub and
Iur interface. ATM over STM-1 interface is used in scenarios with high bandwidth
requirement, for example, IuCS, and IuPS interfaces.
Introduced Version
U9.1&Before
Enhanced Function
3.1.2
3.1.3
3GPP defines AAL2 as bearer mode of Iu CS IuUP and Iub/Iur FP with the transmission
of ATM. In every AAL2 PVC link, multiplexing capability of multi-service is provided
above ATM cell layer by using micro-cell so as to improve the transmission efficiency of
small data packet like voice in Iub, Iur and Iu-CS interface. CID is used to differentiate
different micro-cells, and every (VPI, VCI, CID) composes an AAL2 connection which
becomes a micro-channel to provide transmission bearer for a service. The number of
CID supported by every AAL2 PVC link is limited. In the case of heavy traffic, multiple
AAL2 PVC links can be configured in every interface.
ZTE RAN equipment adopts Access Link Control Application Protocol (ALCAP, comply
with ITU-T Q.2630.1 and Q.2630.2) to provide dynamic management of AAL2 link,
including establishment, modification and release of AAL2 connection between two
nodes.
In the case of service establishment, ZTE RAN equipment selects links with adequate
resource to establish micro-channel in multiple AAL2 links, and guarantees the
uniqueness of CID allocated to different services. After the service is released,
transmission bandwidth and CID resource of the service need to be released for other
services.
When the flow of service bearing on DCH changes, such as decreasing, radio network
can reduce channel bandwidth allocated for the service to spare part of resource to other
users. ZTE RAN equipment supports modifying synchronously transmission bandwidth
of micro-channel of the service by using Q.2630.2 protocol to spare transmission
resource, and avoid the bandwidth waste caused by the mode of establishing new
micro-channel first with releasing old micro-channel later. When the flow of service is
increasing, ZTE RAN equipment can increase transmission bandwidth occupied by
service according to radio network configuration at the same time.
Introduced Version
U9.1&Before
Enhanced Function
No
3.1.4
3.1.5
This feature supports providing different service quality in the transport layer through
configuring different types of AAL2 PVC for the service of different QoS requirements so
as to guarantee the transmission priority of real-time data or time-sensitive data.
Description
ZTE RAN equipment supports ATM PVC service types as followed and can choose
different PVC types for AAL2 link of Iub, Iur and Iu-CS interface to correspond with
different QoS levels.
Conversational
class(C)
PVC type
Streaming
class(S)
Interactive
class(I)
Tolerant class
Stringent class
Real-time PVC
PRI:
C-hi gh
S- low
CBR or rt-VBR
Background
class(B)
Unreal-time PVC
PRI:
I- high
B-lo w
Common PVC
PRI:
C&S-hi gh
I&B-l ow
UBR or nrt-VBR
ZTE RAN equipment supports configuring real-time or non-real-time feature for AAL2
PVC link bearing services. When establishing services, Communication and Stream
services are mapped to real-time AAL2 PVC (CBR or rt-VBR) and I/B services are
mapped into non-real-time AAL2 PVC (UBR or nrt-VBR). It is shown in Figure 20.
Introduced Version
U9.1&Before
Enhanced Function
No
3.1.6
Load sharing mechanism for Multiple AAL2 links bearing user plane data in the
case of service access; when RNC detects through Continuity Check, known
as CC function, that some link has problem in a group of AAL2 links, this AAL2
link will no longer be used and other AAL2 links working normally will be
chosen; when the resource of AAL2 with problem recovers, the AAL2 link will
be added into the resource group again.
ZTE RAN equipment supports load sharing and re-routing of multiple links in
one link set for NCP, CCP and ALCAP connections in Iub interface. Adopt IP
re-routing mechanism to implement protection for Node Bs operation and
maintenance channel in Iub interface.
3.1.7
3.2
3.2.1
3.2.2
The static route is the route information configured by the network administrator manually.
When the network topology structure is changed, the network administrator should
modify the related static route information in the route table manually. The static route
information is private by default, and will not be sent to other routers. In the planning of IP
RAN network, the network topology is usually simple and the static route is sufficient to
meet the requirements.
The static route modes which ZTE supports are as follows:
ZTE RAN equipment can configure different priority for each next-hop path. The load
sharing of IP path is fulfilled based on priority between more next hops while packets are
sent by route.
Introduced Version
U9.1&Before
Enhanced Function
No
3.2.3
ZWF22-03-003 DHCP
Benefits
This feature supports all-IP networking mode with the IP address of Node B dynamically
assigned through DHCP protocol, manual configuration of static IP address no longer
essential, which reduces the workload of operation & maintenance.
Description
For IP transmission over Ethernet between RNC and Node B, or IP transmission over
E1/T1 through PPP/MLPP, the RNC needs to dynamically assign IP address through the
DHCP while Node B starts, which can be used to transfer both operation & maintenance
data and the control plane and user plane data on Iub interface.
ZTE RAN equipment supports the DHCP procedure following the definition in the
RFC2131 and RFC1542, which can be divided into three principal parts: Server, Client
(defined in the RFC2131) and Relay (defined in the RFC1542). DHCP Server is used to
allocate IP address of DHCP Client and configure local equipment. If DHCP Server and
Client are not in the same subnet, DHCP Relay is needed to transfer messages between
Server and Client.
Node B is always used as DHCP Client when DHCP is applied in UNRAN, then DHCP
Server may be other PC or RNC which supports it. If Node B and PC or RNC used as
DHCP Server are not in the same subnet, the router in the transmission network is
needed to support DHCP Server function.
For IP transmission over E1/T1 which is low rate link through PPP/MLPP, ZTE RNC
equipment can be used as DHCP Server to dynamically allocate IP address of Node B.
When Ethernet is used for IP transmission between RNC and Node B, ZTE RNC
supports DHCP Server function to allocate IP address for Node B, or acts as DHCP relay
to aggregate L2 physical link in front of DHCP server.
Introduced Version
U9.1&Before
Enhanced Function
In U9.2, RNC supports DHCP Server and DHCP Relay function when Ethernet is used
for IP transmission.
3.2.4
Benefits
When service throughput of one interface or port is overabundant, IP traffic shaping can
be used to shape the different services of this interface or port to protect it from
congestion, which helps to improve network utilization rate, system efficiency and QoS.
l
Description
When IP UTRAN is adopted in RNC, there is data transmission from Iub to Iu and from Iu
to Iub, also including Iur interface; besides, there may be synchronously transmitted data,
signaling and O&M information, which should be differentiated. When IP packets from
one interface or one port are overabundant and they cannot be transmitted from the
other interface or port, RNC is required to control the service QoS by definite congestion
control algorithm. This function provides IP traffic shaping based on priority queue
mechanism.
Provide IP traffic shaping to different service of IP ports in transmission, mainly provide
excellent priority-based queue forwarding mechanism, and realize fair Weighted Round
Robin (WRR) scheduling, which enables the traffic with higher weight to have more
chances to be scheduled than lower-weight traffic, thus providing different control to
different services.
l
Introduced Version
U9.3
l
Enhanced Function
None
3.2.5
Ethernet loopback.
It is an on-demand OAM functions for the following two purposes: to find adjacency
and fault location and to track and record a path through all the links.
Ethernet Remote Defect Indication enables MEP inform its peer MEP of a defect
encountered, such as signal failure or other defects. The function can be in effect
only when the Ethernet connectivity check is activated.
Based on this, the feature provides the Ethernet frame loss rate, one-way / two-way
delay, and one-way / two-way delay jitter of physical or VLAN port, which can be
queried and displayed on the OMC.
Introduced Version
UR11.1
Enhanced Function
None
3.2.6
DA
SA
Type
Data
CRC
S tan da rd
Et he rne t Fr am e
DA
SA
tag
Type
Data
CRC
TCI
TPID
(0x8100)
Priority
(4bits)
CFI
(1bit)
VLAN ID
(12bits)
Et her ne t Fr ame w it h I EE 8E 0 2. 1Q T ag
Tag Protocol Identifier (TPID), 802.1Q tag identifier, with a value of 0x8100
Tag Control Information (TCI), including:
VLAN Identified (VLAN ID): 12 bit ID which indicates the VLAN to which each
packet belongs.
Priority: 3bits, meets the COS definition in IEEE 802.1P criterion; the higher
the value is, the higher the priority of the frame is. 0 indicates the lowest
priority.
The different VLANs can be divided by VLAN tag in the same physical network; the
interconnection between VLANs is available only by routing or other means, instead of
direct interconnection. In this way, the broadcast packet is restricted in VLAN domain, the
bandwidth is saved, and the domain security is enhanced.
Introduced Version
U9.1&Before
Enhanced Function
No
3.2.7
3.2.8
In IP transmission, the user plane data between NEs are mainly carried in UDP packets.
Each user plane data packet will include the overheads of network layer, herein referred
to as the overheads of IP and UDP headers with a total of 28 bytes (20 bytes for the IP
header, 8 bytes for the UDP header). These overheads will do harm to the transmission
efficiency of the link with the low rate packet (such as the IP over E1).
ZTE RAN equipment supports an IP header compression method defined in RFC2507,
efficiently reducing the IP and UDP header overheads of each packet and improving the
transmission efficiency.
Introduced Version
U9.1&Before
Enhanced Function
No
3.2.9
ZWF22-03-015 DiffServ
Benefits
This feature provides differentiated handling priority for different service classes, to
ensure the QoS of different service classes.
Description
ZTE RAN equipment supports the DiffServ (Differentiated Services) technology defined
in IETF RFC2474 and RFC2475. Messages of different service on Iu/Iur/Iub interface
have been marked with different DSCP values in IP header, which can provide the QoS
guaranteed and the priority differentiation. DSCP (Differential Service Code Point) has 6
bits, redefining the TOS field of IPV4, it is renamed DS and carries the information
required by IP packet service. Technically, it is a three layer technology without low-layer
transmission technology involved.
DiffServ categorizes QoS service requirements by two mechanisms: DS mark and
Per-Hop-Behavior (PHB). Some different service levels are generated by processing
different marks of a packet DS field and PHB definition based on DS fields. ZTE RAN
equipment configures each service with corresponding DSCP value on OMCR based on
its type, the metering, packet loss, and shaping functions are implemented by queuing
and scheduling mechanism based on the DSCP service hierarchy, so the definition of the
QoS classes in wireless network layer can be mapped to the transmission network layer.
ZTE RAN equipment marks the DSCP of each service in the bearing IP packet. Network
elements, such as a router with MPLS function, examines the value of the DSCP field
along the transmission path and classifies the service levels. So the IP QoS function
based on DiffServ is accomplished together with the IP bearer network and the UTRAN
architecture.
Introduced Version
U9.1&Before
Enhanced Function
No
3.2.10
Real-time services are carried by IP over E1, while the non-real-time services
are carried by Ethernet.
Different services use different GE/FE ports and pass through different
transport networks.
Services are isolated by setting VLANs with different priorities for different
services.
The data service with the requirement of low real-time and high transport bandwidth is
carried on the transmission network with low QoS and lower cost. The service with high
real-time requirement such as voice is carried on the higher cost transmission network
with guaranteed QoS. In this way, the transmission cost can be minimized.
Introduced Version
U9.1&Before
Enhanced Function
No
3.2.11
U9.1&Before
Enhanced Function
Node B supports BFD based IP fast reroute in UR11.1 release.
3.2.12
It supports SLA test between ZTE RNC and ZTE Node B, and it adopts UDP
packets and ICMP packets.
It supports SLA test between ZTE RNC and other manufacturers CN, RNC
and Node B, and it adopts ICMP packets.
ZTE RNC supports SLA test between intermediate routers, and adopts ICMP
packets.
The SLA detection of ZTE RNC supports instant test and performance test. Through the
instant test, ZTE RNC can conduct a single SLA test for a specified object (the IP
address of a Node B); through the performance test, ZTE RNC can configure a test task
and conduct consecutive SLA tests for a specified object.
In the instant test, ZTE RNC can configure the SLA message forwarding rate and packet
length through the test task and test the transmission bandwidth of the IP channel.
However, the test is destructive and may cause loss of normal service data. Therefore,
the measurement parameters must be configured carefully.
Introduced Version
U9.1&Before
Enhanced Function
No
3.2.13
Discovery/Handshake
Remote loopback.
Link monitoring.
Introduced Version
U9.2
Enhanced Function
No
3.2.14
3.3
3.3.1
Description
E1 physical interface complies with ITU-T G.703 standards. The allowed jitter of the
physical interface complies with ITU-T G.823 standards. The structure of the frame which
is transferred over the E1 interface complies with the ITU-T G.704 standards. E1 has 32
timeslots numbered 0 to 31. Where, the timeslot 0 is used to carry the synchronization
information and the timeslot 16 for carrying the control signals (also transferring the
information signals if necessary). If the out-of-band common channel signaling (CCS) is
adopted, the timeslot 16 cannot transfer the signaling. Other timeslots can carry the data.
For the IMA protocol, ZTE RAN equipment uses the rest 30 timeslots to transfer the data,
and an E1 supports the physical bandwidth of 1920 kbps. For TC (UMI) mode, ZTE can
maximize the number of timeslot for data transmission to 31, and maximize the physical
bandwidth of an E1 to 1984 kbps.
Introduced Version
U9.1&Before
Enhanced Function
No
3.3.2
When ATM protocol stack is carried on a single T1 link and does not use IMA protocol,
the ATM protocol complies with ITUT- I.0321 standards.
Introduced Version
U9.1&Before
Enhanced Function
No
3.3.3
3.3.4
Description
The STM-1/OC-3 transmission supported by ZTE RAN complies with ITU-T G.957/G.958
standards. Transmission media is ITU-T G.652/G.653 single-mode fiber, the operating
wavelength is 1310nm, and the transmission rate is 155.520Mbps.
The channelized STM-1/OC-3 multiplexing is a technology that multiplexes low-speed
tributary signals (for example, 2Mb/s, 34Mb/s and 140Mb/s) into SDH signals (STM-1
frames). The E1-based CSTM-1 multiplexing refers to the insertion and separation of
STM-1/VC-12 signals, and T1-based CSTM-1 multiplexing refers to the insertion and
separation of STM-1/VC11 signals.
The channelized STM-1 supported by ZTE RNC meets ITUT-G.709. Each STM-1 signal
can multiplex 63 E1 or 84 T1 signals to reduce the number of E1/T1, and interface
integration is improved. At the same time, the protection for interface and line is
enhanced by the APS of SDH.
Introduced Version
U9.1&Before
Enhanced Function
No
3.3.5
ZTE supports the carry of TC (UNI) link on n 64K timeslot subset of one E1 trunk line
so that one E1 can be subdivided into several independent ATM transmission channels
(TC group). For ATM over Fractional E1, only the TC mode is used for each E1 to carry
the ATM transmission and multiple Fractional E1 links cant be combined to IMA groups.
This function does not apply to ZXUR9000 product.
Introduced Version
U9.1&Before and only be applicable for ZXWR V3 controller.
Enhanced Function
No
3.3.6
Enhanced Function
No
3.3.7
ZWF22-03-051 IP over E1
Benefits
This feature supports IP over E1, conveniently fulfilling all-IP networking of UTRAN with
existing low rate E1 link.
Description
The E1 physical interface complies with ITU-T G.703 standard. The allowed jitter of the
physical interface complies with ITU-T G.823 standard. The structure of the frame which
is transferred over the E1 interface complies with the ITU-T G.704 standard. The E1 has
32 timeslots numbered 0 to 31. Where, timeslot 0 is used to carry the synchronization
information of the clock, and timeslot 16 for carrying the control signals (also transferring
information signals if necessary). If out-of-band common channel signaling (CCS) is
adopted, the timeslot 16 dont need to transfer signaling, it can also carry data. Other
timeslots can carry data. ZTE uses the 31 timeslots to transfer data. An E1 supports the
physical bandwidth of 1984 kbps.
IP
MLPPP/MCPPP
PPP
PPP
HDLC
HDLC
E1
PPP
HDLC
ZTE RAN equipment supports IP over E1 by PPP and ML/MC-PPP protocol, the protocol
stacks are described in Figure 3-11. PPP protocol processing complies with RFC1661
and RFC1332 criterion, MLPPP processing complies with the RFC1990 criterion, and the
MCPPP processing complies with the RFC 2686 criterion.
MLPPP can integrate multiple PPP low rate links into one high rate link. MCPPP
supports up to 4 classes of priority (0~3, class 0 is the highest priority and class 3 is the
lowest one). MCPPP can guarantee the preferential processing for high priority service in
narrowband link.
When there are many low rate links, no matter PPP or MLPPP, the protocol can be set at
the OMC. In MLPPP mode, which links to group an MLPPP can be set at the OMC as
well. If some links fail when many low rate links grouped with MLPPP, the transmission
bandwidth of whole MLPPP group is influenced, but other links still guarantee that the
MLPPP group can serve the upper layer.
Introduced Version
U9.1&Before
Enhanced Function
No
3.3.8
ZWF22-03-052 IP over T1
Benefits
This feature supports IP over T1, conveniently fulfilling all-IP networking of UTRAN with
existing low rate T1 link.
Description
T1 physical interface complies with ITU-T G.703 standards. The allowed jitter of the
physical interface complies with the ITU-T G.824 standards. The structure of the frame
which is transferred over the T1 interface complies with the ITU-T G.704 standards. T1
has 24 timeslots numbered 0 to 23. All of these timeslots can carry data. The
synchronization is implemented based on the synchronization BIT of each frame,
Therefore, there is no independent synchronized timeslot. A T1 supports the physical
bandwidth of 1536 kbps.
ZTE RAN equipment supports IP over T1 by PPP and ML/MC-PPP protocol. PPP
protocol processing complies with the RFC1661 and RFC1332 criterion, MLPPP
processing complies with RFC1990 criterion, and MCPPP processing complies with RFC
2686 criterion.
Introduced Version
U9.1&Before
Enhanced Function
No
3.3.9
3.3.10
Description
Optical FE transmission supported by ZTE Node B complies with IEEE 802.3 standards.
The transmission media includes single-mode or multi-mode fiber (meets 100Base-FX
criterion), the data rate can reach 100Mbps.
ZTE Node B equipment supports FE fiber mode, IEEE 802.3 standard Ethernet frame
structure and VLAN frame structure which meets IEEE802.1Q and 802.1P criterions.
Introduce Version
U9.1&Before
Enhanced Function
No
3.3.11
No
3.3.12
3.3.13
The STM-1 transmission line complies with ITU-T G.957/G.958 standard. The
transmission medium is ITU-T G.652/G.653 single mode optical fiber; the working
wavelength is 1310nm; the transmission bit rate is 155.520Mbps.
Multiplexing of the channelized STM-1 (CSTM-1) is to multiplex the low-bit-rate tributary
signals (such as 2Mb/s, 34Mb/s, and 140Mb/s) into SDH signals (STM-1 frame). The E1
based CSTM-1 multiplexing is to insert and separate the STM-1/VC-12 signals; the T1
based CSTM-1 multiplexing is to insert and separate the STM-1/VC11 signals. ZTE RNC
supports the ITUT-G.709 compliant channelized STM-1 transmission. Each STM-1
channel can be multiplexed into 63 E1 channels or 84 T1 channels, reducing the
requirements for a large quantity of E1/T1 cables and improving the interface integration.
Meanwhile, if ZTE RNC adopts CSTM-1, it can use the APS protection technology of the
SDH and the interface and line protection can be enhanced.
Introduced Version
U9.1&Before
Enhanced Function
No
3.3.14
ZTE RAN carries the IP transmission over the Fractional E1 by using the PPP and
ML/MC-PPP protocol. The PPP processing complies with the RFC1661 and RFC1332
Standards; the MLPPP processing complies with the RFC1990 Standards; the MCPPP
processing complies with the RFC 2686 Standards.
When there are many low rate fractional E1 links, whether to use the MLPPP or which of
those links to group an MLPPP can be set at the OMC. If some links fail when many low
rate links group with MLPPP, the transmission bandwidth of the whole MLPPP group is
influenced, but other links still guarantee that the MLPPP group can serve the upper
layer.
Introduced Version
U9.1&Before
Enhanced Function
No
3.3.15
When there are many low rate fractional T1 links, whether to use MLPPP or which of
those links to group an MLPPP can be set at the OMC. If some links fail when many low
rate links group with MLPPP, the transmission bandwidth of the whole MLPPP group is
influenced, but other links still guarantee that the MLPPP group can serve the upper
layer.
Introduced Version
U9.1&Before
Enhanced Function
No
3.3.16
RAN
equipment
supports
GE
modes including
10/100/1000Mbps auto-negotiation.
1000Mbps forced
and
Introduced Version
In UR11.1, this function takes place of features of ZWF22-03-053 IP over Electric FE and
ZWF22-03-054 IP over Electric GE previously in U9.3 release.
Enhanced Function
No
3.4
3.4.1
Introduced Version
U9.1&Before
Enhanced Function
No
3.4.2
network if the IP network between RNC and Node B is complex and the number of
middle nodes is numerous. The clock source can also be set at a certain transmission
node from which Node B can obtain the clock synchronization by IEEE 1588.
To fulfill clock precision defined by 3GPP specification, there are some requirements on
the transmission link between the IEEE 1588 clock source and the Node B:
ZTE also supports clock synchronization from the switch via IEEE 1588 protocol. The
switch serves as Master that provides highprecision clock; the Node B serves as Slave
that extracts the clock information and performs the clock synchronization to avoid the
delay and the jitter generated by the complex transport network. The typical network
architecture is shown below.
Node B
Master
Switch
Network
RNC
GPS
Slave
Switch
Master
Node B
Introduced Version
U9.1&Before, UTRAN supports frequency synchronization
Enhanced Function
RNC
From U9.3 ZTE Node B supports clock synchronization from the switch via IEEE 1588
protocol.
3.5
3.5.1
Radio
Network
Layer
Radio
Network
Layer
Control Plane
User Plane
NBAP
Iub FP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
SCTP
UDP
IP
IP
Data Link
Data Link
Physical Layer
3.5.2
The adoption of the satellite for transmission mainly affects the transmission delay,
transmission jittering, and Bit Error Rate (BER) of the Iub interface. For the synchronous
satellite, the transmission delay normally ranges from 250ms to 280ms.
The BER of the communication channel of a satellite is higher than that of the
transmission channel in the earth. The BER of a typical satellite communication channel
ranges from 10-6 to 10-7, which is larger than the BER (10-7 10-8) of a digital microwave
-10
channel and the BER of an optical channel (10 ). In 3GPP TS 25.104, the BER of an air
-3
interface is required to be smaller than 10 , the extra BER brought about by the satellite
channel can be ignored. Operators only need to consider the impact of the time delay on
the system.
In ZTE RAN equipment, the different processing parameters of the transmission layer
and the FP/RLC layer can be configured according to the estimated time delay and the
transmission jittering for each Node B connected. The radio link transmission quality of
the Node B with the Iub interface over the satellite is guaranteed. The one-way delay of
satellite transmission link is less than 400ms.
ZTE RAN equipment also supports that the Iu-CS interface and the Iu-PS interface are
connected to CN over the satellite. The allowed transmission delay for the Iu interface
over the satellite transmission is less than 1000ms.
For the satellite transmission link influenced easily by the weather, the QoS of the Iub/Iu
interface cant be guaranteed fully.
Introduced Version
U9.1&Before
Enhanced Function
In U9.3, Iub over satellite support 400ms delay.
3.5.3
Radio
Network
Layer
Radio
Network
Layer
Control Plane
User Plane
RANAP
Iu UP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
SCCP
M3UA
RTP/RTCP*
SCTP
UDP
IP
IP
Data Link
Data Link
Physical Layer
3.5.4
Full functions defined in 3GPP IuPS protocols are supported when IP transmission is
applied to connect RNC with PS core equipments.
Radio
Network
Layer
Control Plane
User Plane
RANAP
Iu UP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
SCCP
M3UA
GTP -U
SCTP
UDP
IP
IP
Data Link
Data Link
Physical Layer
3.5.5
For a single E1/T1 trunk line, timeslot splitting and switching at the granularity of DS0 is
supported by this feature which can reduce the transmission resource in the scenario of
2G and 3G co-sharing transmission. .
Description
The Iub interface in the RAN network usually adopts the E1 and T1 transmission. In
some application scenarios where trunk resources are rather scarce and the rental of
lines are too high, ZTE RNC and Node B support timeslot splitting and switching of a
single E1/T1 link at the granularity of DS0, which can divide the timeslots into multiple
logic transmission channels and use these channels separately.
A typical application of the DS0 switching is to share transmission of 2G and 3G devices.
The Abis interface of the 2G device and the Iub interface of the 3G device can share a
physical trunk as the transmission line. Some timeslots of the transmission line are
allocated to the 2G device; some timeslots are allocated to the 3G device. The 3G Node
B and RNC realize the functions of a timeslot switch. They terminate the 3G service
carried over DS0 and switch the 2G service carried over DS0 to the adjacent BTS and
BSC. See the figure below:
Figure 3-13
2G
BTS
TDM
TDM
T1/E1/C-STM-1
3G
Node B
3G
RNC
Timeslots switched
2G
BSC
Timeslots switched
Timeslots for 2G
Timeslots for 3G
With the DS0 switching function, the 3G device can carry any DS0-based information
over the transmission resources of the Iub interface, not only for the 2G and 3G shared
transmission.
Introduced Version
U9.1&Before
Enhanced Function
None.
3.5.6
Carry PS traffic with high data rate and lower QoS requirement by low cost IP
network.
Description
ZTE supports ATM and IP on Iub interface simultaneously, and allocates different bearer
for different service types. Generally, for those data services with relaxed real time but
higher bandwidth requirement, IP transmission can be used. For signaling in control
plane, voice service, and other real time data services, ATM transmission can be used.
The RNC automatically allocates transmission bearer for service based on its type while
service is built, and fulfills hybrid transmission.
Introduced Version
U9.1&Before
Enhanced Function
No
3.5.7
Operators usually have multiple Iub transmission paths with different characteristics, and
use proper transmission path for R99/HSDPA/HSUPA. By multiple path protection, when
one path is down or degraded, system can switch the traffic to other path.
This feature can be used in hybrid transmission network, E1 and Ethernet transmission
network for example. The feature can provide redundancy protection between different
types of physical connections; in case of one physical connection fails, the traffic service
can be handed/balanced over to other physical connection to provide transmission
protection for upper application layer.
Description
For hybrid transmission network, operator can define in OMC different classes of
services going through different physical connection according to transmission network
QoS to enhance transmission efficiency and save transmission investment. For example,
operator can define PS services, which has a looser requirement on real time and QoS,
go through Ethernet, and CS services, which have a strict requirement on real time and
QoS, go through ATM or TDM physical connection. Even through IMA, MLPPP and APS
can provide redundancy protection between physical connections; these technologies
can not provide redundancy protection between different types of physical connection,
for example between E1 and Ethernet.
ZTE RAN equipment can support redundancy protection between physical connections
of ATM over E1 and IP over Ethernet, and between of IP over E1 and IP over Ethernet.
The following services in application layer can be protected during physical connection
handover, for example from Ethernet to E1, in case of Ethernet fails.
Signal
Service
O&M
RNC can configure multiple routing links of different priorities to realize OMCB
channels redundancy.
In hybrid transmission network of ATM over E1 and IP over Ethernet, downlink
packets of OMCB will select routing link of IPoA firstly, and then secondary routing
link in case of IPoA fails. ZTE Node B supports IP address handover automatically
form IPoA port to Ethernet port while detecting IPoA link fails and can send uplink
OMCB packets in Ethernet link.
In hybrid transmission network of IP over E1 and IP over Ethernet, downlink
packets of OMCB will select IP over E1 firstly, and then IP over Ethernet in case of
IP over E1 fails. ZTE Node B supports IP address handover automatically from
MP/PPP port to Ethernet port while MP/PPP ports fails and can send uplink OMCB
packets in Ethernet link.
For both hybrid transmission networks, link routing will be restored to normal status
if first priority link detected to be normal status, and downlink packets of OMCB will
go through first priority link automatically.
Synchronization
ZTE Node B supports multiple clock source configurations of different priorities. For
example, Clock source from E1 can be configured as first priority and Clock source
from Ethernet (1588 V2) can be secondary priority. Handover of Clock source can
be triggered from primary to secondary source in case of primary source fails.
When faults in primary links restore, ZTE RAN equipment can relocate application layer
services to primary links. Existing ongoing services will be kept on current links and new
services will be initiated in primary links in order to guarantee transmission network
reliability and QoS degrading.
The multi-path protection means Iub interface can take more than two paths in the
corresponding physical transmission layer. As the network changes, the ability of each
channel and performance would change or fail. At this time, in order to ensure operators
business continuity, improve the reliability of transmission Iub, ZTE UMTS uses SLA for
periodic monitoring of the transmission path. When the transmission degrades or is
interrupted, system will change the transmission paths equivalent bandwidth, or reduce
to 0 which will cause call release. In this way, a new call will change its path after the
equivalent bandwidth changing.
3.5.8
Radio
Network
Layer
Control Plane
User Plane
RNSAP
Iur FP
Transport Network
User Plane
Transport Network
Control Plane
Transport Network
User Plane
SCCP
M3UA
SCTP
UDP
IP
IP
Data Link
Data Link
Physical Layer
3.5.9
UDP MUX technology generally reduces IP transmission by 20%. It can be further save
IUB interface bandwidth. This function reduces the operator's transmission expenses.
Description
In IP UTRAN scenario, user plane FP frames on the Iub interface are carried based on
the UDP protocol. For typical CS services and SRB signaling, the payload is short and
sealed through the UDP/IP and the link layer. The frame header overhead of the entire
packet is large, wasting the limited transmission bandwidth on Iub interface.
The UDP MUX multiplexes the packets with the same destination IP address before
sending them, which reduces the frame header overhead, saves bandwidth resources,
and improves the transmission efficiency of Iub interface.
Multiplexing and de-multiplexing are implemented in the IP/UDP layer, regardless of the
link layer protocol. It is applicable to various carrier scenarios, such as Internet and PPP.
Introduced Version
U9.2
Enhanced Function
No
3.5.10
By RTP MUX, which uses one overhead for those small packages using the same IP
address, overhead decreased greatly and the transmission efficiency is enhanced. 3GPP
29.814 defines a kind of method to imply RTP MUX.
Introduced Version
U9.2
Enhanced Function
No
3.5.11
ZWF22-03-020 LACP
Benefits
This feature can improve transmission link availability, increase link capacity and provide
both load balance and system fault tolerance ability by aggregating multi-link into one
logical link.
Description
ZTE RNC supports LACP (Link Aggregation Control Protocol) which complies with IEEE
802.3ad protocol. This feature can bind multiple Ethernet physical links together to
provide high speed link capacity with only one IP address and provide backup
mechanism among links which have the same attribute like speed and deluxe mode.
Without LACP, the logical link is one-to-one mapping to physical link and the bandwidth
of the logical link is limited by the capability of physical link. As shown in Figure 3-15,
LACP binds three physical links, each with 100Mbps bandwidth for instance, into one
logical link. The LACP link is with bandwidth of 300Mbps and is able to bear higher data
rate.
Figure 3-15
LACP
Link1
Link2
Link3
Subflow1
Link A
Subflow2
Subflow3
Besides, LACP allocates traffic to every physical link it aggregates, which is a kind of
load balance in nature. When one link is broken in LACP link group, traffic will be
allocated to other physical links automatically.
When peer equipments, like switch, CN or other RNC, support LACP function, ZTE RNC
and Node B can be configured to aggregate some Ethernet links into one
higher-bandwidth link on Iu or Iur interface. ZTE RAN supports static and dynamic LACP
modes.
Introduced Version
U9.1&Before
Enhanced Function
LACP is introduced in Node B from UR11.1.
3.5.12
transmission state of the whole link to relieve the congestion of the transmission network
and avoid reduction of QoS of online service.
Description
In IP network, the real bandwidth of a link is determined by all nodes and all paths
between every two adjacent nodes. So it is important to perform transmission CAC
according to the real bandwidth of the link.
Transmission CAC based on SLA-PM function supported by ZTE is able to adjust
bandwidth used for CAC when some nodes or paths are broken, which increases packet
loss rate. For example, a VC12 is broken in the MSTP network, so the physical
bandwidth is reduced. ZTE RAN can find out the abnormal link by transmission SLA
monitor, and is able to decrease the bandwidth of the link used by CAC to prevent more
data being put into the transmission link. When the broken VC12 restores, ZTE RAN can
find out the link transition and recover to the normal CAC bandwidth.
In some special situation, for example some routers or switches are broken and there is
no link redundancy mechanism to bypass the broken node and constant packet loss rate
sustained. ZTE RAN can find out this situation and switch off transmission CAC
adjustment because this feature will not be able to help relieve network congestion.
Operator can find out the network fault by Transmission SLA Monitoring function
supported by ZTE.
The function of transmission CAC based on SLA-PM can be used on Iu, Iub and Iur
interface and based on any IP transmission network.
Introduced Version
U9.2
Enhanced Function
No
3.5.13
ZWF22-03-025 ACL
Benefits
This feature implements the access control by IP packages character. It limits the
throughput, improves the network performance, and provides a basic method for network
security access.
Description
ACL has two types: standard ACL and extended ACL. Standard ACL only checks the
source address of IP package, and extended ACL checks both source address and
destination address besides protocol type of package and ports. Since the standard ACL
checking rules are simple, some complex control rules cannot be achieved, so the
standard ACL is suitable when close to the target. On the contrary, extended ACL checks
any combination of fields, and it is more suitable when close to the source.
Unlike in point-to-point link scenario, the packets incoming to nodes of UMTS network
are diversified in Ethernet connection. Therefore, Address Control List (ACL) function is
deployed for ZTE UMTS equipments to filter incoming traffic so as to discard unexpected
packets. The ACL function may not be enabled if the transmission network is a private
network where unexpected packets are already filtered and discarded. When ACL
checks and finds that the package doesnt fit the access rule, ZTE UMTS equipments will
throw out the package, which increases the security of system and decreases the
attacking possibilities.
ZTE RNC supports quintuple-based packet filtering: Local IP address, peer IP address,
protocol Number, source port Number and destination port Number It allows the packets
from special address and port to access the system to avoid useless information and the
IP attack. The processing capability of IP interface board would be decreased when ACL
function is activated.
ZTE Node B supports packet filtering: protocol No, source port No, destination port
Number The source port and destination port depend on signaling consultations. The
filtering parameters cannot be manually configured.
The ACL supports packet filtering and discarding only in Ethernet transmission
scenarios.
Introduced Version
U9.2
Enhanced Function
U9.3 Node B supports ACL function.
3.5.14
Key management protocol IKE (Internet Key Exchange): IKE key management
protocol to provide secure and reliable algorithms and key agreement.
Moreover, the Internet Key Exchange (IKE) protocol provides automatic key
negotiation and security association (SA) setup and maintenance services to
simplify the use and management of IPSec.
All above of three mechanisms are independent of the algorithm, and by means of
modular design it allows only change the realization of different algorithms without
affecting other parts. Application protocol encryption algorithm to use depends on the
specific user and application security requirements.
Introduced Version
UR11.1
Enhanced Function
No
3.5.15
ZWF22-03-033 OSPF
Benefits
This feature provides dynamic routing protocol based on OSPF, improves networking
reliability.
Description
OSPF is an interior gateway protocol used for routing between routers belonging to a
single Autonomous System.
OSPF uses link-state technology in which routers send each other information about the
direct connections and links which they have to other routers. Each OSPF router
maintains an identical database describing the Autonomous Systems topology. From
this database, a routing table is calculated by constructing a shortest-path tree. OSPF
recalculates routes quickly in the face of topological changes, utilizing a minimum of
routing protocol traffic.
ZTE UTRAN supports OSPF function, enables RNC exchange routing information with
networking node like routers, makes network routing convergence and kept updated, and
improves network reliability.
Introduced Version
UR11.1
Enhanced Function
None
HSDPA
4.1
4.1.1
Table 4-1
Max. No.
Category
of
HS-DSCH
Codes
Min.
Inter-TTI
Interval
Supported
Supported
carrier
Modulations
Number
MAC
MIMO
Layer
Operation
Peak Bit
Rate
QPSK/16QAM
N/a
1.2Mbps
QPSK/16QAM
N/a
1.2Mbps
QPSK/16QAM
N/a
1.8Mbps
QPSK/16QAM
N/a
1.8Mbps
QPSK/16QAM
N/a
3.6Mbps
QPSK/16QAM
N/a
3.6Mbps
10
QPSK/16QAM
N/a
7.2Mbps
10
QPSK/16QAM
N/a
7.2Mbps
15
QPSK/16QAM
N/a
10Mbps
10
15
QPSK/16QAM
N/a
13.9Mbps
11
QPSK
N/a
0.9Mbps
Max. No.
Category
of
HS-DSCH
Codes
Min.
Inter-TTI
Interval
Supported
Supported
carrier
Modulations
Number
MAC
MIMO
Layer
Operation
Peak Bit
Rate
12
QPSK
N/a
1.8Mbps
13
15
QPSK/16QAM/64QAM
N/a
17.6Mbps
14
15
QPSK/16QAM/64QAM
N/a
21Mbps
15
15
QPSK/16QAM
Activated
23.3Mbps
16
15
QPSK/16QAM
Activated
27.9Mbps
17
15
QPSK/16QAM/64QAM
Inactivated
17.6Mbps
QPSK/16QAM
Activated
23.3Mbps
QPSK/16QAM/64QAM
Inactivated
21Mbps
QPSK/16QAM
Activated
27.9Mbps
18
15
19
15
QPSK/16QAM/64QAM
Activated
35.3Mbps
20
15
QPSK/16QAM/64QAM
Activated
42.2Mbps
21
15
QPSK/16QAM
N/a
23.4Mbps
22
15
QPSK/16QAM
N/a
28.0Mbps
23
15
QPSK/16QAM/64QAM
N/a
35.3Mbps
24
15
QPSK/16QAM/64QAM
N/a
42.2Mbps
27
15
QPSK/16QAM/64QAM
Activated
70.6Mbps
28
15
QPSK/16QAM/64QAM
Activated
84.4Mbps
In U9.3, UE with HS-DSCH physical layer categories 21, 22, 23 and 24 are supported.
UEs of Category 21 and Category 22 support DC-HSDPA, but do not support 64QAM.
UEs of Category 23 and Category 24 support the combination of DC-HSDPA and
64QAM.
In UR11.1, UE with HS-DSCH physical layer categories 19, 20, 27 and 28 are supported.
UEs of Category 19 and Category 20 support combination of MIMO and 64QAM. UEs of
Category 23 and Category 24 support the combination of DC-HSDPA, MIMO and
64QAM, while the peak bit rate can be reached only if the network could activate the
combination of those three functions.
4.1.2
If an operator has limited frequency resources but has to provide the R99 services,
sharing the carrier frequency of R99 and HSDPA allows the operator to provide R99
services and HSDPA services at the same time and profitably develop high-speed data
services through the residual resources of R99. Common resources (including
channelized codes, Node B transmit power, and Iub interface transmission bandwidth) of
the cell can be allocated between R99 services and HSDPA services.
However, the peak rate and throughput provided by the cell are reduced and the
experience of data service users is affected when the R99 services occupy
resources.ZTE RAN equipments support both R99 and HSDPA services simultaneously
in one cell. ZTE RRM algorithm will guarantee appropriate cell common resources
allocation between these two services.
If the operator has more frequency resources than required by the R99 services, a
dedicated carrier frequency can be deployed to provide the HSDPA services. Comparing
with the DCH, HS-DSCH has higher spectrum utilization to get higher peak rate and cell
throughput, improving the subscriber experience of the mobile data service and reducing
the unit cost of the high-speed data service. Normally, the third or above carrier can be
used as HSDPA dedicated carrier to provide data services in hotspot coverage.
The cell can be configured as HSDPA dedicated carrier or HSDPA and R99 hybrid
carrier. The R99 services can not be initiated on HSDPA dedicated carrier. Besides
HSDPA dedicated carrier frequency, R99 capable carrier should also be deployed so as
to support the traditional CS service and low-speed PS service (on DCH). ZTEs RAN
equipments provide different kinds of carriers for users according to services types.
Introduced Version
In UR11.1, this function takes place of features of ZWF23-01-001 HSDPA Common
Carrier with R99 and ZWF23-01-002 HSDPA Dedicated Carrier previously in U9.3
release.
Enhanced Function
No
4.1.3
AMC works on the following principle: Node B in network side selects the optimal
downlink modulation mode, coding method and the number of HS-DSCH Channel
according to the radio channel quality status (CQI report) reported by UE and the
utilization of network resources so as to determine the rate of data transmission, raise
the data throughput of the UE, and reduce transmission delay in condition of radio quality
permission. AMC will increase system capacity and improve communication quality
according to the fading channel modification to implement link real-time balance.
ZTE can support two types of link adaptation technologies (AMC), including inner-loop
link adaptation and outer-loop link adaptation.
Inner-loop link adaptation should be based on the CQI (Channel Quality Indication). The
core principle is that Node B selects the modulation and coding mode and size of the
transmission block according to the CQI. When the UE is at a favorable communication
point (for example, the UE is close to Node B or a direct ray path is available), a
high-order modulation and high-rate channel coding mode (for example, 16QAM and 3/4
coding rate) can be selected to transmit subscriber data accordingly to obtain the higher
transmission rate. When the UE is at a far point of the cell, or in a high-fading or shadow
area, a low-order modulation and low-rate channel coding mode (for example, QPSK and
1/4 coding rate) can be selected to ensure communication quality.
Outer-loop link adaptation is based on the ACK/NACK/DTX feedback by HS-DPCCH.
The CQI has the disadvantages of delay and measurement error. Therefore, the
inner-loop link adaptation only will be insufficient to control the downlink BLER in order to
meet target value under any circumstance. In this case, outer-loop link adaptation is
required.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.4
During code division multiplexing, all available HS-DSCH channel codes can be divided
into several subsets, which are allocated to different users. This mode can support not
only the transmission of a small amount of data (in this case, the transmitted data needs
only some channelized codes of the HS-DSCH in the cell), but also the resource
allocation for the UEs with different HSDPA categories.
Time division can realize the fast scheduling on HS-DSCH channel in a 2ms period and
allocate the cell throughput according to different users requirements of services.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.5
HSDPA Fast Scheduling introduces two enhanced functions: TFRC selection and
Dynamic adjustable BLER target according to the radio conditions.
The feature of TFRC selection can increase resource usage and cell throughput
according to TFRC selection (Transport Formation and Resources Combination) in the
case of satisfaction with the scheduling requirement.
A TFRC respectively indicates TB Size, modulation symbol set and the number of
channel codes. The scheduler selects a new TFRC for the scheduled user every 2ms
TTI.
In this feature arithmetic, TFRC selection will be more accurate using the adjustable CQI.
The usable power, number of HS-PDSCH codes and UE category, etc. has the flexibility
for HSDPA TFRC selection. In the case of single user, fully utilization of codes and power
can increase throughput. In the case of multi-user, accurate configuration of codes and
power can increase cell throughput.
The flexible modulation selection can effectively choose the maximum TB Size which is
corresponding to the different codes combination modulation (QPSK, 16QAM):
For UE category 8, the number of codes by QPSK can be achieved to 10. 16QAM also
can be selected by less than 5 codes.
For UE category 10, the number of codes by QPSK can be achieved to 15. 16QAM also
can be selected by less than 5 codes to improve HSDPA throughput for lack of code
resources.
The feature of Dynamic adjustable BLER target according to the radio conditions can
configure different BLER target values for different users according to the different CQI.
Dynamic adjustable BLER target can reduce the uplink interference and save the
downlink power.
According to the CQI measured and fed back by UE or other resources, NodeB will
decide the following modulation/coding method for the UE downlink transmission. Due to
the measurement error, report delay and incorrect CQI report, this mechanism cannot
duly utilize the channel condition modification to obtain the optimum modulation/coding
method. Therefore, BLER change is so big that the user cannot get the deserved QoS.
Here, the report CQI is incorrect because the threshold for the different CQI value will not
change along the channel condition. In order to resolve the above problems, NodeB will
adjust CQI value according to the decoding result of ACK/NACK to implement the
outer-loop rate control which can effectively track the change of channel condition to
control BLER around the target value.
Introduced Version
U9.1&Before
Enhanced Function
U9.3 introduces the function of Dynamic adjustable BLER target according to the radio
conditions.
4.1.6
transmission
HSDPA HARQ uses the Stop and Wait protocol during the data transmission. ZTEs RAN
equipments support the parallel transmission of multi-HARQ process to continuously
transmit data to a certain user. The time from HSDPA data sending to feedback receiving
of ACK/NACK needs at least six delays of 2ms TTI. So one UE needs at least 6 HARQ to
use the radio channel and achieve the running with full rate.
HARQ uses fast re-transmission combination technology to make full use of every
transmission period. It not only gets the gain from time diversity, but also reduces the
required first transmission power due to the reduction of the first transmitting BLER. It
can improve the system performance and power utilization.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.7
In the HSDPA system, a modulation and coding scheme (MCS) is used to transfer the
downlink data. The MCS must be adjusted to the ever-changing channel conditions, thus
maximizing the channel capacity and throughput. UE measurement and CQI generation
are based on target BLER=10%. Due to the implementation difference among vendors
and measurement error, the reported CQI is not accurate. Therefore, the following
results are caused:
The mechanism cannot acquire the optimal MCS timely and effectively
If the CQI of the UE is overestimated, the transmission block is extremely large and the
downlink BER exceeds by 10%. If the CQI of the UE is underestimated, the transmission
block is extremely small and system throughput is reduced.
To solve the problem, ZTE UMTS Node B adjusts the target CQI according to the CQI
and ACK fed back by the UE. The purpose is to reduce the measurement error of the
CQI, relieve the impact of the implementation difference among the UE vendors, ensure
the QoS of the UE, and raise system throughput.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.8
Besides QPSK modulation, ZTE Node B equipments support 16QAM for HS-PDSCH.
The spectrum efficiency is twice more than that of QPSK. The constellation graph is
below:
Figure 4-1
The number of physical channel bit is 1920 in 2ms TTI for every code channel when
16QAM is used, that is to say channel rate is 960Kbps. The physical layer peak rate is up
to 14.4Mbps when 15 code channels are concurrently used.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.9
HSDPA cell indicator is introduced in SIB5 and SIB5bis. After receiving the indicator, the
UE can display the HSDPA availability in the cell which it is camping on. Accordingly, the
user can choose proper services. For example, the HSDPA data card user will search
the HSDPA carrier to camp first. This cell selection strategy depends on UE.
HSDPA indication is introduced in 3GPP R6. R5 HSDPA UE needs to upgrade to R6 to
support this feature.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.10
4.1.11
4.1.12
U9.1&Before
Enhanced Function
No
4.1.13
4.1.14
4.1.15
4.1.16
4.1.17
Every HSDPA users data is received in HS-DSCH channel even through UE current
situation is macro diversity. The cell that provides HSDPA service for UE is called UE
serving cell.
ZTE RAN equipments can support that while the UE is moving within HSDPA coverage,
it updates HS-DSCH serving cell dynamically and implements the continuous coverage
of HS-DSCH serving cell according to the signal intensity of pilot channel measured by
UE. In case of load balance between co-coverage HSDPA cells with different
frequencies, or RNC performing the HCS handover from micro-cell to macro-cell based
on load or moving speed, blind handover is executed without frequency measurements.
The serving HS-DSCH cell change happens among the cells with same frequency. When
the best cell changes (1D event triggered) and this cell supports HSDPA, RNC will trigger
the serving HS-DSCH cell change procedure. The serving HS-DSCH cell change can
also happen among the cells with different frequencies. When inter-frequency hard
handover meets the handover judgment condition and the target cell supports HSDPA,
RNC will trigger the hard handover together with serving HS-PDSCH cell change
procedure.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.18
When the HSDPA user is moving, if the target cell cannot support HSDPA services or
HSDPA resource is not sufficient to accept the new user, this feature enables UE to
change the channel from HS-DSCH to DCH to keep the service continuity.
When the soft handover is in progress, if the HS-DSCH serving cell will be deleted from
the current active set and there are no cells in the new active set to support HSDPA, the
service will return from HS-DSCH channel to DCH, and then perform the soft handover
procedure.
When the hard handover is in progress, if the target cell can not use HS-DSCH channel,
the services will be configured to DCH at the same time.
When the DCH-borne PS user is moving, if the HS-DSCH in the target cell is available,
ZTE RAN equipments can support the change from DCH channel to HS-DSCH channel
to increase spectrum utilization.
After soft handover, if the new added cell in the active set supports HSDPA, the DCH
channel will be changed to HS-DSCH channel at the appropriate moment.
When the hard handover is in progress, if the target cell can not use HS-DSCH, the
services will be migrated from DCH channel to HS-DSCH.
This feature can be used for intra-RNC handover or inter-RNC handover.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.19
For a UE with ongoing service on HS-DSCH channel, ZTE RAN equipment can hand
over the UE from WCDMA to GSM directly without migrating HS-DSCH channel to DCH
before handover procedure initiates.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.20
It can keep the HSDPA data transmission continuity when HS-DSCH serving
cell is changing in active set.
Description
In order to transmit upper layer RRC signaling, NAS layer signaling and physical power
control information, HSDPA users need to configure DPCH channel, called A-DPCH.
ZTE RAN equipment processes A-DPCH just like common DPCH, and supports
A-DPCH soft/softer handover. Please refer to ZWF21-03-001 Soft and Softer Handover
for more details.
ZTE RAN equipment also supports associated F-DPCH soft/softer handover when using
associated F-DPCH.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.21
4.1.22
Prevents the system from overload and improves the system stability.
Allocates system resource based on service priority for different users and
services under the premise of guaranteeing the system stability.
Description
When Node B and UE support HSDPA, it is possible to allocate HSDPA wireless
resources. The scenarios where the service requires new system resources include RRC
connection, RAB connection setup, RAM modification, SRNC relocation, lur relocation,
intra-RNC handover, and dynamic channel allocation. ZTE RAN equipments will fully
consider the existing resource status in advance to prevent the lack of resources when
the HSDPA services access or the system over load after the services have accessed.
Excessive users sharing the HS-DSCH channel will reduce the average user
services QOS. According to the requirements of services, the maximum number of
services can be limited by HS-DSCH per cell properly.
The HSDPA data throughput is performed for the GBR service, like streaming and
conversation service. It will set an HSDPA cell throughput threshold for the new
HSDPA service.
Downlink Power
The HS-DSCH admission control based on downlink power is performed for the
GBR service only. RNC will forecast based on the changes of download power after
the new HSDPA services have accessed. It will set a total HSDPA downlink power
threshold after the new services have accessed.
U9.1&Before
Enhanced Function
No
4.1.23
If UE is in soft handover state and the overload cell is not the best one in the
active set, the DCH (includes associated channel) link will be deleted in the
overloaded cell
Hand over the UE to cells with the same coverage of different frequency or
different system forcedly (especially DCH services on the DCH or GBR
services on the HS-DSCH).
ZTE RAN equipments will consider basic priority (ZWF21-05-002 RAB QoS Parameters
Mapping) when using admission control. It is possible to make the high priority user and
service to get more system resources to improve the QoS.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.24
From release U9.3, DL HSPA+ capability of cell and UE is considered during HSDPA
load balance.
4.1.25
Slow down the system load by adjusting channel type according to cell load.
When cell load is too high, user can migrate from special HS-DSCH to
common FACH to reduce system load and maintain system stability.
Ensure the service continuity by adjusting channel type according to the target
cell for handover.
4.1.26
Description
HSDPA power control includes HSDPA power allocation and HS-PDSCH Measurement
Power Offset configuration.
ZTE equipments support dynamic HSDPA power configuration modes:
Node B adjusts HSDPA service power fast based on R99 services power
station, in favor of making full use of residual resource by R99 service.
HS-PDSCH Measurement Power Offset is used to calculate the returned CQI value by
UE. RNC configures proper HS-PDSCH Measurement Power Offset based on the total
cell power.
HS-SCCH power control calculates HS-SCCH power of the scheduled user (including
new transmission & re-transmission). The power control based on CQI which can reduce
UE interference will control HS-SCCH transmission power according to the report CQI
and MPO.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.27
HS-SCCH, HS-PDSCH and associated F-DPCH use cell main scramble code.
At most four HS-SCCH channels are supported per cell. Channelized code of
HS-SCCH is allocated in static mode and the SF is 128. Channelized code for
HS-PDSCH is SF=16. When HSDPA and R99 share the same carrier, ZTE RAN
equipments support both static mode and dynamic mode to configure HS-PDSCH
channelized code. In static mode, the number of HS-PDSCH is fixed after a cell is
set up. While in dynamic mode, the number of HS-PDSCH is adjusted dynamically
according to HSDPA user throughout and R99 user flow.
Allocated codes for R99 can be regulated and optimized for HSDPA services. When
ZTE RAN realizes that HS-PDSCH could be allocated with downlink channelized
code through re-allocated downlink channelized code for R99 DPCH, ZTE RAN
adjusts the downlink channelized code allocation for R99 DPCH. And then downlink
channelized code whose SF is 16 is released.
For HS-DPCCH, configure the channelized code whose SF is 256 according to the
number of uplink DPCCH channels.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.28
Description
If the new user fails in admission caused by resource limitation, different congestion
control strategies will be triggered so as to improve the user access probability.
If congestion happens when it is accessing, the following methods could be used to
relieve congestion.
Service pre-emption
Introduced Version
U9.1&Before
Enhanced Function
No.
4.1.29
This attribute improves service QoS and ensures output power of power amplifier will not
be saturated.
Description
ZTE NodeB supports fast power congestion control. The base station will check the
power when the downlink output power reaches the preset threshold, The detection time
is corresponding to the power control response time (not longer than one timeslot time,
namely 0.67ms). The base station judges whether the input power exceeds the preset
threshold. If yes, it reduces the input signals of the power amplifier and ensures that the
output power of the power amplifier is not over its nominal power.
Introduced Version
U9.1&Before
Enhanced Function
No
4.1.30
U9.1&Before
Enhanced Function
No
4.1.31
U9.1&Before
Enhanced Function
No.
4.1.32
4.1.33
ZTEs RAN equipments set attributes for different cells. For example, some cells only
support HSDPA services but dont support R99 services; it means to carry services on
HS-DSCH, not on DCH. It is better to carry different services on different transport
channels. For example, CS services need to be carried on DCH to ensure real time
services and high speed packet data services should be carried on HS-DSCH to make
full use of its higher efficiency.
If network is deployed with two or more carriers, one of which is set to be equipped with
one dedicated HSDPA carrier and one dedicated R99 carrier at least, radio resources
should be allocated into different carriers according to services attributes. If users
access frequency is different from the one which services need, ZTE RAN equipments
provide handover between carriers to retry services into frequency which services need.
For example, when CS service is established in the carrier which only supports HSDPA,
it will be retried to the carrier which supports R99 services. When high speed package
data service is established in the carrier which only supports R99, it will be retried to the
carrier which supports HSDPA.
Introduced Version
U9.1&Before
Enhanced Function
No
4.2
4.2.1
ZTEs UMTS RAN equipments offer 10 HS-DSCH channels, which use SF=16
channelized codes. The peak rate of MAC layer can reach 7.2 Mbps for PS service in
HS-DSCH. In this case, the HSDPA UE capability category must be 7or higher.
With feature of ZWF23-01-013 HSDPA Fast Scheduling, those HS-DSCH channels can
be shared by multiple users in one cell.
Introduced Version
U9.1&Before
Enhanced Function
No
4.2.2
4.2.3
4.2.4
No
4.2.5
4.2.6
Enhanced Function
No
4.2.7
U9.1&Before
Enhanced Function
No
4.2.8
4.2.9
RNC dynamic allocation method is applied in HS-PDSCH code allocation for ZTE Node
B. Relative to HSDPA 2ms TTI scheduling, the signaling delay between RNC and Node
B is so long that R99 must be reserved to enough free codes while RNC is configuring
HS-PDSCH code. For the fast HSDPA scheduling, these free codes probably cause the
waste of SF16 code resources. So, the solution of Node B free code allocation is
introduced.
This feature implements as following steps:
(1) Node B completes the statistics on SF16 channel code allocation. When a channel
code of SF=16 or its sub-code is configured to DPCH by RNC, Node B identifies this
code to be occupation state.
(2) During each DPA scheduling cycle, besides the available HS-PDSCH code
configured by RNC, the scheduler detects free situation of other SF16 codes. In the
next 2ms, this free code should be used and identified to be temporary using.
(3) If the temporary code collides with the code configured by RNC, after Node B
receives these codes, DPA scheduler will be notified to immediately release the
temporary channel code. Due to the short scheduling cycle (2ms), DPCH channel
code configured by RNC has impossibility to be used on HSDPA.
The use of this feature and the function of HS-PDSCH code allocation dynamically by
RNC are controlled by configuration switch. When this feature is applied, the function of
HS-PDSCH code allocation dynamically by RNC will not take effect. RNC notifies NodeB
to set up HS-PDSCH channels through NBAP message after cell establishment, and
RNC will not inform NodeB to re-allocate HS-PDSCH channels subsequently despite the
amount of HS-PDSCH actually used.
Introduced Version
U9.3
Enhanced Function
No
4.2.10
No
MBMS
5.1
5.1.1
5.1.2
Enhanced Function
No
5.1.3
5.1.4
Description
In PTM mode, S-CCPCH channel is used to carry traffic. High downlink transmitting
power for S-CCPCH is required to meet the QoS requirements of all UEs within the cell.
In reality, the total downlink transmitting power of each cell is limited. The excessive
consumption of downlink transmitting power by S-CCPCH would affect the capacity of
the cell.
UE may combine a service data from multiple adjacent intra-frequency cells when the
service is transmitted in PTM mode. So certain multi-path combination gain is acquired. It
reduces the downlink transmitting power consumed by S-CCPCH.
ZTE RAN supports two combining modes: soft combining and selective combining:
Soft combining
The UE combines service data at the physical layer. To implement the soft
combining, the TFC of these transport channels combined must be same, and
the synchronization time difference among combined channels must not
exceed 1 TTI+1 slot.
Selective combining
Selective combining is based on the RLC PDU sequence number. CRC in
RLC PDU is checked to select a best one in multi RLC PDU from different cells.
UE must support RLC re-ordering. Data transmission time difference among
combined cells cannot exceed the RLC re-ordering capability of UE.
It is obvious that the selective combining has lower requirements for system
synchronization than the soft combining, but the latter brings higher gains. According to
simulation result, 6db gains can be obtained in the case of soft combining to three cells
and 3db gains for selective combining. Correspondingly, when system adopts soft
combining and selective combining, MBMS channel number which system can broadcast
simultaneously is more than that without using combining.
When transmitting the same service in PTM mode in adjacent cells, ZTE RAN adjusts the
timing of S-CCPCHs among these cells to keep S-CCPCHs synchronized. Periodically
desynchronizing detection is performed for soft combining. If S-CCPCHs are
5.1.5
Static configuration in OMC: Adopt certain carrier as the preferred carrier for a
specific MBMS service through static configuration.
Dynamic setting: Perform dynamic setting of the preferred carrier based on the
cell load status of different frequency points.
Introduced Version
U9.1&Before
Enhanced Function
No
5.1.6
5.1.7
UEs in idle, FACH or PCH state access to the target cell by cell reselection and
continue to receive MBMS service; UEs in DCH state access to the target cell by
handover and continue to receive MBMS service.
In this scenario, UE must be in DCH state, and continue to receive MBMS service in
the target cell by handover.
MBMS service is transmitted by PTM mode in source cell, and by PTP in target
cell.
When moving to the target cell, UE in idle state requests to establish PTP bearer in
target cell by sending RRC CONNECTION REQUEST message to RNC; UE in
PCH or FACH state triggers the process of establishing PTP bearer through cell
update; UE in DCH state requests to establish PTP bearer by sending MBMS
MODIFICATION REQUEST message to RNC.
Firstly, UTRAN instructs UE to hand over to the target cell with PTP mode
preserved, then instructs UE to release PTP radio bearer and establish PTM
bearer.
For MBMS multicast service or enhanced broadcast service, one scenario is that
MBMS service with PTP or PTM mode is transmitted in source cell, but not in target
cell due to no UE receiving. If the MBMS service adopts PTM mode in source cell,
UTRAN knows whether the MBMS UE is moving, and establishes MBMS PTP
service in target cell during handover process.
If the MBMS service adopts PTM mode in source cell, UTRAN doesnt know
whether a certain UE receiving MBMS service is moving or not, but UTRAN can
inform with system broadcast that the MBMS service adopts PTP bearer in target
cell, then, when a UE moves to target cell, it will request to receive the MBMS
service (for the request process, refer to the above scenario 3), then UTRAN will
establish MBMS PTP service in the target cell.
In addition, UE in DCH state may camp in the cell of non-preferred carrier for MBMS. If
the UE requests to receive MBMS service, it can request to hand over to cell on MBMS
preferred carrier by sending RRC message of MBMS MODIFICATION REQUEST. RNC
will permit UE accessing to the target cell by hard handover when the condition of
inter-frequency handover is met.
Introduced Version
U9.1&Before
Enhanced Function
No
5.1.8
For a new MBMS service transmitted in PTM mode, ZTE RAN establishes a new
SCCPCH for it or transmits the new service on existing SCCPCH together with other
MBMS services. The admission mechanism for the two cases is different.
If a new SCCPCH is set up, admission is based on the following resources. The new
MBMS service is allowed to set up only when all the following factors are allocated
successfully:
If new MBMS service shares the existing S-CCPCH with other MBMS services,
admission is checked only on the last two factors mentioned above.
If admission for MBMS service fails, the cell is regarded to be congested. In this case,
congestion control is activated to free system resources for new MBMS service.
For MBMS service transmitted in PTP mode, it complies with admission control
mechanism of DCH or HSDPA.
Introduced Version
U9.1&Before
Enhanced Function
No
5.1.9
This feature allocates downlink channelized codes for MBMS service. It also supports
dynamically adjusting channelized code of SCCPCH carrying MTCH to reduce
consumption of channelized code for MBMS service and increase the capacity of other
services in cell.
Description
ZTE RAN allocates downlink channelized code (CC) for MBMS services as the following:
MICH channel
MCCH channel
Carried on the S-CCPCH, the MCCH adopts the channelized code of SF=128,
which is configured at OMC.
MTCH channel
The MTCH is carried on the S-CCPCH. A certain number of CCs can be reserved
for the S-CCPCH carrying MBMS traffic at OMC. If a new S-CCPCH needs to be
established during MBMS service RAB setup stage, a codec is allocated from the
reserved MBMS CC. The spreading factor is determined by the bit rate of the
MBMS service. The CC occupied by the MBMS service is released upon the end of
MBMS RAB. The reserved CC is adjusted dynamically among MBMS service and
non-MBMS service. If it is not used by MBMS service, the reserved CC also can be
used by non-MBMS services. This increases capacity of other services in cell.
MSCH channel
Introduced Version
U9.1&Before
Enhanced Function
No
5.1.10
ZTE RAN periodically detects MBMS combining status in the cell and adjusts the
transmitting power of S-CCPCH based on the detection results. When MBMS
services cannot be combined, the transmitting power of S-CCPCH is increased
accordingly to ensure MBMS QoS. When soft or selective combining is available for
MBMS services, it lowers the transmitting power of the S-CCPCH to expand cell
capacity.
Introduced Version
U9.1&Before
Enhanced Function
No
5.1.11
Admission control
MBMS services with various priority levels are granted with different access
thresholds. If necessary, ZTE RAN may restrict the access of low-priority MBMS
services based on actual requirements so as to reserve radio resources (such as
downlink power and so on) for high-priority MBMS services.
Congestion control
In the event of MBMS access failure due to cell congestion, if this MBMS service is
preemption-capable, the RNC may trigger it to preempt other low-priority MBMS or
non-MBMS services to ensure access of as many high-priority UEs as possible.
Load control
In the event of cell overload, the RNC lowers the transmitting power of low-priority
MBMS or non-MBMS services and even forcedly releases the former to ensure
5.1.12
Lower the transmitting power for MBMS services carried in PTM mode
Both of above-mentioned measures are taken based on the priority of MBMS services.
Low-priority MBMS services are handled first until the cell load is restored to normal level.
Once the cell load is light, the RNC restores the transmitting power of previously adjusted
MBMS services and MBMS services deleted during overload control.
For MBMS service carried in PTP mode, it complies with the overload control mechanism
of DCH or HSDPA.
Introduced Version
U9.1&Before
Enhanced Function
No
5.2
5.2.1
5.2.2
This feature enables system to optimize transmission mode of MBMS service according
to the number of UEs receiving MBMS service actually to utilize network resource
properly.
Description
MBMS includes two service bearer modes: PTP and PTM. In PTM mode, one FACH is
set up for carrying MBMS traffic and the downlink transmitting power of the FACH must
be as high as possible to ensure the MBMS service quality for all users under a cell. In
PTP mode, one dedicated radio link is set up for each user. PTP mode uses the perfect
power control and scheduling mechanism of dedicated channel to ensure MBMS service
quality for each user. So few number of PTP radio bearer occupies less radio resources
than PTM radio bear. And PTM mode is economic when several PTP radio bearers
should be set up. By this characteristic, PTP mode is adopted when there are few users
receiving the MBMS service in a cell. When there are a lot of users, PTM mode is
adopted.
For general MBMS broadcast service, the RAN broadcasts service in the whole service
area in PTM mode. For enhanced broadcast MBMS service and multicast MBMS service,
counting is used to collect the statistics of the number of UEs receiving certain MBMS
service in the cell to select the optimal transmission mode:
Transmit MBMS data in PTP mode if there are only few UE expecting to
receive MBMS service
Transmit MBMS data in PTM mode if there are quite a few UEs expecting to
receive MBMS service
When starting MBMS session, ZTE RAN will select the optimal transmission mode for the
MBMS service. During the MBMS service with PTM mode, recounting is performed
through periodically timing or cell load control. With the result of recounting, whether to
change the MBMS bearer mode is decided.
Introduced Version
U9.1&Before
Enhanced Function
No
5.2.3
5.2.4
When a UE in the Idle, FACH, or PCH state moves from the original RNC to the target
RNC, it can activate MBMS service in RNC without the support of Iur interface. While for
UE in the DCH state moves between different RNCs, it may trigger handover or SRNS
relocation in Iur interface. ZTE RAN allows SRNC to notify DRNC the MBMS multicast
service information that the UEs in DCH state joined. As a result, the DRNC registers the
multicast service in the SGSN and users can continue receiving the MBMS service in the
DRNC.
Introduced Version
U9.1&Before
Enhanced Function
No
5.3
5.3.1
Then UE must pass the authentication by the BM-SC before joining MBMS service. The
context information of UE, which is used for billing and selection of service data multicast
path, will be generated in the BM-SC, core network and UTRAN.
Different from the broadcast mode, in the multicast mode, the RNC starts MBMS service
transmitting and receiving only when there are UEs having MBMS activated in the MBMS
service area.
Introduced Version
U9.1&Before
Enhanced Function
No
5.3.2
5.3.3
Description
The ZTE RAN device provides the 32Kbps channel for MBMS PTM service.
Introduced Version
U9.1&Before
Enhanced Function
No
5.3.4
5.3.5
Introduced Version
U9.1&Before
Enhanced Function
No
5.3.6
HSUPA
6.1
6.1.1
Description
The indicator of the HSUPA cell can be broadcasted through the system message SIB5
or SIB5bis. When searching cells, UE can recognize whether a cell supports the HSUPA
service according to the indicator, and select a preferred cell accordingly. For example,
an HSUPA data card user can search the HSUPA cell in a same sector and camp on it.
UE can be configured to select a cell automatically according to the capability of cells.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.2
Table 6-1
Category
E-DPDCHs
Supported
Supported
and Smallest
Modulations
TTIs
Spreading
Factor
Maximum
Maximum
Data Rate
Data Rate
with 10ms
with 2ms
TTI in MAC
TTI in MAC
Layer
Layer
1xSF4
QPSK
10ms
0.716 Mbps
--
2XSF4
QPSK
10ms, 2ms
1.44Mbps
1.40 Mbps
2XSF4
QPSK
10ms
1.44 Mbps
--
2XSF2
QPSK
10ms, 2ms
2.0 Mbps
2.89 Mbps
2XSF2
QPSK
10ms
2.0 Mbps
--
2XSF2+2XSF4
QPSK
10ms, 2ms
2.0 Mbps
5.74 Mbps
2XSF2+2XSF4
QPSK/16QAM
10ms, 2ms
2.0Mbps
11.50Mbps
Introduced Version
For 10ms TTI, HSUPA UE categories 1 to 5 and for 2ms TTI, HSUPA UE category 6 are
supported in U9.1&Before.
Enhanced Function
UE category 6 is supported in UR11.1.
6.1.3
simultaneously. The excellent RRM algorithm provided by ZTE can guarantee proper
allocation of cell common resources between the two types of services
When the frequency resources available for operator are limited and the R99 service
must be provided in the uplink, use the same frequency carrier to deploy the HSUPA and
the R99 for utilizing the attributes of the HSUAP to provide high speed data services. But
the resources occupied by the R99 can reduce the uplink peak rate and throughput of a
cell and affect the QoS of the data services.
When the operator has more frequency resources than what are needed by the R99
service, it is recommended to deploy HSUPA and HSDPA service in separate frequency
carrier. Since the frequency band utilization efficiency of the E-DCH is higher than that of
the DCH, the dedicated carrier can obtain higher uplink peak rate and cell throughput,
improving the QoS of the wireless data service and reducing the cost of high speed data
service.
HSDPA and HSUPA dedicated carrier cannot process R99 services. In order to support
traditional CS service and low speed PS service (carried on DCH), its necessary to
deploy carrier to support R99 besides HSUPA/HSDPA dedicated carrier. ZTE RAN
system can distribute users to different carriers according to the service type.
Introduced Version
In UR11.1, this function takes place of features of ZWF25-01-001 HSUPA Common
Carrier with R99 and ZWF25-01-002 HSUPA Dedicated Carrier previously in U9.3
release.
Enhanced Function
No
6.1.4
Description
MAC-e entity is added in Node B after introducing HSUPA. It is used to implement
HSUPA data scheduling function just as R99 DCH channel data scheduling function
realized by MAC layer in RNC. Node B allocates SG (Scheduling Grant) for each UE in
the cell, and then sends AG (Absolute Grant) in E-AGCH channel or RG (Relative Grant)
in E-RGCH channel to notify UE to use SG. UE can only use the transmitting power in
the range which SG allows and that power has impact on uplink data bit rate of UE.
ZTE Node B supports PF (Proportion Fair) algorithm to realize HSUPA fast scheduling.
This algorithm takes into full account of all kinds of factors such as actual requirement of
different services, radio link condition of users, cell uplink interference and cell load.
Meanwhile, the priority of service and the priority of user should be considered (For SPI,
refer to ZWF25-05-001 QoS Mapping for HSUPA Service), the users with high priority
will obtain more resources.
ZTE RAN supports HSUPA fast scheduling algorithm which can guarantee GBR service
data transmitting rate. It also can support method of Non-scheduled to grant UE
Non-scheduled transmission date capability, that is, configure to the Node B through
NBAP signaling by RNC according to service type in order to ensure the transmission of
high-priority data, such as SRB data.
Because HSUPA scheduler is located in Node B, the cell uplink interference can be
detected real time. According to real time interference condition, Node B can control and
frequently schedule the resource to HSUPA users in every 2ms or 10ms period, and can
make use of resource more efficiently to guarantee the higher throughput in E-DCH
channel.
As a scheduler of HSUPA non-serving cell, ZTE Node B can control the interference
status of non-serving cell through non-serving RG command, so it can avoid allocating
excessive power resources for the UEs in serving cell which imposes immense influence
on the non-serving cell.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.5
6.1.6
ZTE RAN supports HSUPA 1.45Mbps user peak rate. When data services are carried
over the E-DCH channel, the peak rate in MAC layer can reach 1.45Mps in uplink. At this
moment, HSUPA UE category must exceed level 2.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.7
6.1.8
ZTE RAN system supports 2Mbps HSUPA peak rate. When a users data service is
carried on E-DCH, the uplink rate of MAC layer can reach 2Mbps. In this case, the
HSUPA UE capability must be level 4 or higher.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.9
Enhanced Function
No.
6.1.10
6.1.11
All ZTE RAN can support CS service and PS I/B/S service over HSUPA concurrently:
6.1.12
This feature supports up to 3 concurrent PS I/B/S services. The maximal rate of each PS
service is decided by subscription rate in CN. The total concurrent rate of all services
cannot exceed the maximal available rate of HSUPA, which depends on UE capacity,
load of the system and the user radio link environment, etc.
ZTE RAN system supports concurrent multiple PS services over HSUPA. The RAB radio
parameters comply with 3GPP TS 34.108 protocol.
Introduced Version
U9.1&Before
Enhanced Function
No.
6.1.13
6.1.14
6.1.15
ZTE RAN system supports E-DCH intra-frequency hard handover when HSUPA is
introduced. The process is the same as that of DCH. (Please refer to ZWF21-03-002
Intra-Frequency Hard Handover).
If the target cell supports HSUPA, E-DCH serving cell will be changed during
intra-frequency hard handover. Otherwise, E-DCH will be switched to DCH during this
operation.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.16
No
6.1.17
6.1.18
However, most E-DCH capable UEs do not support compression mode and
inter-frequency measurement. ZTE RAN system can define that E-DCH should fall back
to DCH during HSUPA inter-RAT Reselection as an optional function and it can be
configured by ZTE OMC system.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.19
CE resource of Node B
Uplink interference
6.1.20
ZTE RAN system differentiates users and services of different priorities (Please refer to
ZWF21-05-002 RAB QoS Parameters Mapping). The load of low-priority users and
services will be decreased first, therefore high priority users and services may get more
system resources and higher QoS.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.21
6.1.22
Description
After HSUPA is introduced, the cell will be congested if it fails to accommodate the
incoming HSUPA services. ZTE RAN supports the following congestion control
strategies:
DCH rate will be decreased if the incoming HSUPA services are restricted because
of uplink interference.
Service preemption
Service preemption means that ZTE RAN will drop some UEs in connected state
(E-DCH channel or DCH channel) or decrease the DCH rate when the number of
HSUPA services or CE resource is restricted.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.23
Adjust channel type to decrease the system load according to cell load
When the cell uplink is overloaded, the user can be switched to common
RACH from dedicated E-DCH to decrease the system load and guarantee the
system stabilized.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.24
The principle of HSUPA Uplink Outer Power Control is similar with R99. It adjusts
SIRtarget based on service quality, which is used by Inner Loop Power Control, to adjust
UE transmission power. However, the service quality of HSUPA is evaluated by
retransmission times of FP, the more times of retransmission, the worse channel quality.
Consequently, the required SIRtarget is raised and transmission power is increased.
Otherwise, the required SIRtarget falls and transmission power is decreased.
HSUPA Downlink Open Loop Power Control configures E-AGCH, E-RGCH/E-HICH with
proper power offset, guaranteeing that UE correctly receives downlink control message
including E-DCHAG, RG and ACK/NACK, etc. Because the receiving performance of
E-RGCH/E-HICH in macro diversity condition has a soft handover gain relative to that of
E-AGCH without macro diversity, ZTE RAN system dynamically adjusts E-AGCH Power
Offset to save transmission power according to handover status.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.25
Downlink SC
Uplink SC
For a UE, E-DPCCH and E-DPDCH use the same SC as that of uplink DPCCH
Downlink CC
E-AGCH uses CC with SF 256. E-RGCH/HICH uses the same CC with SF 128.
E-AGCH and E-RGCH/HICH CC are statically configured. Because the number of
supported users of each E-AGCH and E-RGCH/HICH is limited, the number of
E-AGCH and E-RGCH/HICH is configured according to the predicted number of
HSUPA users within the cell.
Uplink CC
CC with SF 256 is always used for E-DPCCH. The remaining CC of OVSF code
tree can be used for E-DPDCH. ZTE RAN feature DRBC can configure the
minimized SF for a UE automatically according to practical traffic of the service to
save the Node Bs baseband resource.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.26
cell is in high uplink load, it is impossible for RNC to manage system resource effectively,
then uplink noise probably increases sharply and it causes packet loss or call drop
For this reason, measurement of Received Scheduled E-DCH Power Share (RSEPS) is
introduced in 3GPP R7. RSEPS is defined as a ratio: sum of all scheduled E-DPCCH
and E-DPDCH power for all UEs in a serving E-DCH cell, divided by the corresponding
RTWP of the cell in the same time duration. Both RSEPS and RTWP in the duration of
RSEPS calculated are reported to RNC by Node B.
In admission control and load balance, RSEPS is one of the factors to estimate the uplink
noise of an HSUPA cell.
l
Introduced Version
U9.2
Enhanced Function
No
6.1.27
U9.3
Enhanced Function
None
6.1.28
6.1.29
For the E-RGCH/HICH power control, there may be three power control methods: 1)
Fixed power control; 2) Associated DPCCH closed-loop power control; 3) Associated
CQI/HS-SCCH power control. E-AGCH will implement the method of 1) and 2) at least.
Introduced Version
U9.3
Enhanced Function
No
6.1.30
6.1.31
This feature provides Nominal Bit Rate (NBR) for I/B class services which are similar to
GBR. The feature can avoid user experience degrading due to the cause that I/B class
service users are blocked and cant be scheduled for a long time.
Description
ZTE RAN system supports NBR for I/B class service over HSUPA. RNC provides NBR
parameters to Node B for I/B class service. During HSUPA fast scheduling, Node B
guarantees the lowest bit rate for I/B class service according to the assigned NBR.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.32
user initiates high speed packet data session in an R99 dedicated carrier, and RNC will
directly try to switch it to the carrier supporting HSUPA.
Introduced Version
U9.1&Before
Enhanced Function
No
6.1.33
congestion information, and then RNC will reconfigure the data rate of the user allowed
by UL to decrease the UL data transmission accordingly.
On RNC side, ZTE equipment records the information on the data frame receiving time,
FSN, and CFN of each E-DCH channel. Based on the information, ZTE RNC can detect
the frame loss rate and fame time delay variation of the period, and finally judge whether
congestion occurs at the Iub interface. When congestion is detected at the Iub interface,
the RNC sends the TNL Congestion Indication frames to the Node B. According to the
congestion information, the Node B degrades the grant to the UE and controls the uplink
transmitted bit rate of the UE, and this reduces the data traffics of the Iub interface.
Introduced Version
U9.1&Before
Enhanced Function
No
6.2
6.2.1
The frame alignment time during the data framing of the transmitter decreases
so that air interface latency is greatly reduced
The Round Trip Time (RTT) of HARQ process is reduced so that HARQ
performance as well as user data rate is improved
2ms TTI enables Node B to track cell load status and allocate resource within
2ms. It improves the utilization rate of the system resource
2ms TTI improves the uplink throughput up to 5.76 Mbps for a cell. To achieve
this high performance, the UE must be category 6 or higher
2ms TTI E-DCH channel can provide higher throughput. But it will increase the uplink
noise. And the coverage of 2 ms TTI E-DCH channel is worse than the coverage of 10ms
TTI E-DCH. ZTE RAN realizes the TTI switching between 10 ms TTI and 2 ms TTI based
on the uplink speed of the UE.
If the uplink speed of the UE is lower, ZTE RAN will choose the 10 ms TTI E-DCH
channel. It will reduce the uplink noise and increase the uplink coverage. If the uplink
speed of the UE is higher, ZTE RAN will choose the 2 ms TTI E-DCH channel to improve
the service experience.
Introduced Version
U9.1&Before
Enhanced Function
U9.3 realizes the TTI switching between 10 ms TTI and 2 ms TTI based on the uplink
speed of the UE.
6.2.2
Introduced Version
U9.1&Before
Enhanced Function
No
6.2.3
6.2.4
Introduced Version
U9.1&Before
Enhanced Function
No
6.2.5
6.2.6
SPI, for instance, are configured to highest priority. Node B uses non-scheduling method
to guarantee SRB rate, improving the transmission reliability for RRC signaling and NAS
layer signaling.
Introduced Version
U9.1&Before
Enhanced Function
No
HSPA Evolution
7.1
R7 HSPA+
7.1.1
of 16QAM. Compared with the HS-DSCH in R5, the peak rate of a single user increases
by 50%, reaching 21.6Mbps.
l
Introduced Version
U9.1&Before
Enhanced Function
No
7.1.2
Primary
transport block
HS-DSCH
w1
Tr CH
processing
w2
w3
Spread/scramble
Secondary
transport block
HS-DSCH
Ant1
Ant2
w4
TrCH
proc essing
CPICH 2
w1 w2 w3 w4
Weight Generation
The figure shows the basic principle of HSDPA 2 x 2 MIMO technical solutions. The
channel coding, interleaving, and spreading are performed in MIMO mode. Two transport
blocks transmitting simultaneously are spread and scrambled by the same channelized
code and scrambling code. The scheduler in Node B decides how many transport blocks
(1 or 2) should be transmitted to UE in one TTI. The complex value after spreading is
transferred to 2 antennae in MIMO, and transmitted after weighting processing with
Pre-coding vectors
w1 , w2 , w3 and w4 .
w3 = w1 = 1 / 2
w4 = w2
1 + j 1 j
w2
,
,
2
2
1+ j
,
2
1 j
UE sends PCI (pre-coding index) to Node B according to channel state, and Node B
chooses corresponding
The 3GPP R7 protocols define the categories of the UEs that support MIMO, only
categories 15, 16, 17 and 18 support MIMO. The 3GPP R7 protocols also add the
information elements (IEs) that support MIMO in the report of local cell capability. The
RNC determines whether the RL supports MIMO according to the local cell capability and
UE capability. If the RL supports MIMO, the MAC-hs scheduler of the Node B decides
whether to use MIMO according to the following aspects:
In case of the UE does not fulfill the conditions of MIMO, Node B will transmit data by Tx
diversity of single stream.
Having configured MIMO, there are two options to transmit pilot signal.
Option 1: the two antennae transmit same pilot signal using P-CPICH;
Option 2: one antenna transmits P-CPICH, and the other transmits S-CPICH.
When two antennae transmit same pilot signal using P-CPICH, MIMO will degrade to
STTD. As most of commercial terminals nowadays will forbid equalizer receiver when
working in STTD mode and the performance of UE will degrade greatly, 3GPP
recommends VAM method instead of STTD to realize MIMO networking for legacy and
MIMO UEs. The VAM solution is depicted in the following Figure:
f1
U11
Trch
processing
R99/HS
Ant2
Spread/scramble
U21
P-CPICH
f2
R99/HS
Trch
processing
Ant1
Spread/scramble
P-CPICH
Primary transport block
HS-DSCH
VAM
W1
Trch
processing
U11
W2
U21
Ant2
Spread/scramble
Secondary transport block
HS-DSCH
W3
Trch
processing
U22
W4
S-CPICH
U12
Spread/scramble
In this solution, F1 only bears legacy R99 users and HSPA users. F2 bears MIMO, R99
and HSPA users. S-CPICH is only used for MIMO carrier, i.e.F2, and only P-CPICH
transmits for F1 carrier.
The introduction of VAM will induce the PCI weight restriction problem. As the figure
above, data has to be processed by twice phase offset operation, the first is MIMO
processing, and the second is VAM. In case of single-stream of MIMO, when some
Pre-coding sets are adopted, the phase offset of these two operations are duplicated in
one antenna, which will lead to the transmitting power of this antenna doubles at the
moment, but at the same, the phase offset in another antenna are canceled, which will
lead to no transmitting power in this antenna. To avoid imbalance of transmitting power in
two antennas, if the Pre-coding weight is not restricted, the performance of MIMO in
single stream will degrade evidently. Through the restriction of PCI from UE feedback,
the degradation will be reduced. 3GPP adopts a method that networks perform PCI
restrict when they receive the PCI feedback of UE. In this method, NodeB reports its PCI
restriction capability to RNC, then RNC congigures the Precoding weight set restriction
information elements to UE according to NodeB capability, and UE performs the MIMO
Precoding weight set restriction processing.
Offset to reduce the interference caused by the secondary pilot to the traditional UE and
improve the system performance. The secondary pilot signal is only used for MIMO UE
and it will interfere with the non-MIMO UE. S-CPICH power offset which lead to flexibly
configured S-CPICH power according to the MIMO UEs growing situation can reduce
the interference to the non-MIMO UE. In addition, this configuration information should
notify UE besides Node B, because S-CPICH power offset will affect the channel
estimation and demodulation performance of MIMO UE.
During the real network test, the phase adjustment for VAM matrix will result in a
considerable effect. So, E-VAM (Evolved MIMO fixed) is introduced. In this solution, the
secondary pilot by VAM matrix will implement the phase transformation once again (The
essence is to adjust the phase of VAM matrix without any effect of power balance for PA)
to get the maximum receiving power and CQI will achieve the most value. The input of
offset transformation calculation is based on CQI. CQI-based Phase Offset adaptive
Algorithm (PAA) indicates that the following procedures will implement repeatedly per
period: 1) The selection for the optimum phase offset ; 2) The implementation for the
optimum phase offset . The combination of E-VAM and CQI-based PAA can increase
the throughput in the static multi-user scenario.
Introduced Version
U9.2 supports MIMO function with VAM.
Enhanced Function
In UR11.1, ZTE RAN introduces functions of Pre-coding Weight Set Restriction and
S-CPICH Power Offset. E-VAM (Evolved MIMO fixed) is also introduced.
7.1.3
With increasing the downlink data rate of DL MIMO/64QAM application, HSUPA 16QAM
is introduced in 3GPP R7 to achieve the adaptability between the uplink and downlink
rates. The uplink UE Category 7 can support it.
Having introduced 16QAM modulation, the UL physical layer will produce the changes in
SF selection (modulation method), coding, gain factor, interleaving, rate matching, etc.
For 16QAM, because the legacy rake receiver cannot be satisfied with the receiving
performance in the fading channel, the equalizer should be used for receiving. Generally,
G-Rake, MPC, LMMSE, MUD, etc. can be chose. Rake receiver is applied to Gauss
channel and only the equalizer can be used in fading channel.
The UL data throughput for the single user can be doubled, so 16QAM can promote
sensitivity and provide the high-quality and efficiency network to the operator.
E-DPCCH boosting supported in this feature can improve the HSUPA demodulation
performance in high speed. Having introduced HSUPA, especially 16QAM, the pilot is
required to refer higher SNR in high speed because the traditional DPCCH power control
will result in the lack of channel estimation SNR when the uplink speed is higher. Thus, in
the case of high speed, this feature supports that E-DPCCH can be the boosting of
phase reference signal used for combination channel estimation during E-DPDCH
demodulation.
Introduced Version
UR11.1
Enhanced Function
No
7.1.4
UE2 UE3
UE1
...
UE10
UE1
UE2
UE3
UE1
1 slot
UE1
time
The introduction of enhanced F-DPCH has removed the restriction on F-DPCH timing
offset, i.e. allowing activating several F-DPCHs to use different timing offsets. This is
configured at network side. This feature requires UE to buffer 1 bit TPC command per
slot.
As the enhanced F-DPCH is introduced, F-DPCH slot format as defined in 3GPP R6 is
changed. Originally, it is a fixed offset from TPC field to slot boundary. After changing,
the offset is determined by a parameter of configured F-DPDCH slot format. Assuming
that 30% UEs are in the status of soft or softer handover, the capacity of an enhanced
F-DPCH is increased to 7 UEs in reality.
l
Introduced Version
U9.2
Enhanced Function
No
7.2
7.2.1
st
HS-PDSCH
or the 2
nd
HS-SCCH with type2. If the UE is able to decode the first transmission successfully, it
sends an ACK to Node B; otherwise it buffers the data without sending NACK.
HS-SCCH-less operation can achieve a target of reducing HS-SCCH overhead and
improving DL system capacity.
HS-SCCH-less Operation is suitable for small data packet services, especially VoIP
service. By eliminating HS-SCCH overhead, the system capacity of VoIP over HSPA can
be greatly improved. This feature applies to CELL_DCH state.
Introduced Version
U9.2
Enhanced Function
No
7.2.2
7.2.3
ZWF26-01-007 UL DTX
Benefits
This feature provides UL DTX function. UL DTX brings many benefits: improve user
experience, reduce UE power consumption, increase UE IDLE time, obviously reduce
UL interference, increase the number of online UEs and improve UL capacity.
Description
In R6 and previously protocols of 3GPP, UE transmits uplink DPCCH continuously. But
UL DTX is introduced in R7, it means UE discontinuously transmits uplink DPCCH based
on some pattern automatically. It allows the UE to stop transmission of UL DPCCH in
case there is no transmission activity on E-DCH or HS-DPCCH. A pre-defined DPCCH
activity pattern is used to transmit periodically, it aims at reducing transmission of
DPCCH on one hand, and keeping synchronization between Node B and UE. Once
E-DCH or HS-DPCCH starts transmission, the transmission of uplink DPCCH is
immediately restored to normal status. UL DTX adopts 2 kinds of discontinuous DPCCH
transmission periods: UE_DTX_cycle_2 and UE_DTX_cycle_1, the former is integral
multiple of the latter. This feature applies to CELL_DCH state.
Introduced Version
U9.2
Enhanced Function
No
7.2.4
ZWF26-01-008 DL DRX
Benefits
This feature provides DL DRX function. With DL DRX function, UE power consumption
can be reduced and IDLE time can be increased.
Description
DL DRX is implemented based on UL DTX; it is the supplement of UL DTX function. Note
that DL DRX operation is only possible when UL DTX operation is activated. DL DRX
adopts pre-defined pattern to receive HS-SCCH data. During UL DTX time, DL DRX time
must be consistent with UL DTX time so that UE can be better remained at sleep mode.
7.2.5
7.3
7.3.1
No
7.3.2
and increase peak bit rate in CELL_FACH state and better user
experience.
Description
To break through RACH transmitting capability limitation and improve uplink
performance in CELL_FACH state, enhanced uplink CELL_FACH feature was
introduced in 3GPP R8. The main improvement of Enhanced UL CELL_FACH is that
common E-DCH could be used for uplink data transmitting in CELL_FACH state. This
feature includes the following characters:
Improving random access method to reduce IDLE, CELL_FACH state transfer delayIn
Acquisition Indicator(AI) in AICH channel, the allocated common E-DCH resource
information for UE is added, and UE can use this common E-DCH to initiate DPCCH
transmitting and the following E-DPCCH and E-DPDCH transmitting later.
Using HSUPA to increase peak bitrate in CELL_FACH stateCCCH and DTCH/DCCH
data can be bear on assigned common E-DCH.
Because SRBs bear on HSPA, this feature can decrease channel transfer delay between
CELL_FACH and CELL_DCH.
The deployment of this feature depends on the Enhanced DL CELL_FACH feature, and it
must be combined with Enhanced DL CELL_FACH.
Introduced Version
UR11.1
Enhanced Function
No
7.3.3
of inactivity time, UE can enter into discontinuous reception state. At this time, UE will
try to detect the HS-SCCH channel at the RX burst length frame. If the UE find the DL
HS-DSCH channel, then UE start to receive the data from HS-DSCH channel.
Introduced Version
UR11.1
Enhanced Function
No
7.4
R8 HSPA+
7.4.1
ZWF26-02-004 DC-HSDPA
Benefits
This feature supports FDD DC HSDPA, which is Dual-Cell or Dual-Carrier HSDPA.
HSDPA Dual-Cell and 64QAM can make HSDPA downlink physical layer peak rate
reach 43.2Mbps. DC-HSDPA can not only double the cell rate in cell center, but also
double the cell edge user rate to improve network rate.
Description
DL MIMO and 64QAM increase the user peak rate and cell throughput. However, when
the user is in the cell edge, the user experience cannot be improved. In the case of bad
radio condition, MIMO and 64QAM also cannot be effectively utilized.
DC-HSDPA introduced in 3GPP R8 protocol will configure two adjacent carriers in one
cell to increase the frequency efficiency and the user throughput. If the UEs support
DC-HSDPA, they have two cells including serving cell and secondary serving cell in the
downlink, and one cell in the uplink. Only the serving cell which would be provided with
the same capability to the single-carrier cell has corresponding uplink channel. The
secondary serving cell only includes the physical channels for HSDPA transmission,
such as CPICH, HS-PDSCH and HS-SCCH.
With the joint proportion fair scheduling, DC user scheduling decided by the scheduled
priority and resource of each carrier can be processed in both carriers. In DC-HSDPA,
the single proportion fair scheduling algorithm independently calculates schedule priority
factor in each carrier. The joint proportion fair scheduling will calculate the scheduled
priority factor based on the transport block of two carriers when calculating the history
traffic.
If UE is capable and RAN has the License for the features, 64QAM could be activated
during DC-HSDPA operation in any carrier or both carriers when radio quality is good
enough. Furthermore, DC-HSDPA can be combined with CPC. When the secondary
serving cell is activated, HS-SCCH orders for the activation and deactivation of downlink
DRX will not only be transmitted in the serving cell, but also in the secondary serving cell.
They have the same DRX status. HS-SCCH-less operation is only supported for serving
cell but not for the secondary serving cell. HS-SCCH orders would be transmitted in both
serving cell and secondary serving cell.
If function of DC HSDPA is available in both UE and RAN, and MIMO is not activated or
DC is prior to MIMO in O&M configuration, DC will be activated automatically when
HSDPA channel established. ZTE RNC can dynamically choose primary cell according
to cell-pair configuration of DC in Node B and load situation in both carriers. ZTE Node B
supports dynamically dual carrier inactivity control, which implements the secondary
carrier activation/deactivation in the case of dual carrier to reduce UE batterys power
consumption. In the mode of dual carrier, the secondary carrier will be deactivated when
there is a few data or no data to transmit during a period of time. In this way, HS-SCCH
demodulation is not required to process in the secondary carrier to be used for UE power
saving. Similarly, the secondary carrier will be activated when the data is transmitted in
another carrier. Handover also is supported by ZTE RAN between DC HSDPA area and
non DC HSDPA area to keep service continuity.
DC-HSDPA is applicable to the operators that can provide more frequency resources.
Relative to the users in cell centre, the users in cell edge would be provided more
DC-HSDPA gain. Comparing with two SC-HSDPA carriers, DC-HSDPA can improve the
user throughput and sector throughput. With the increase of the number of users, the
gain will be accordingly reduced.
Introduced Version
U9.3
Enhanced Function
No
7.4.2
Description
As higher spectrum efficiency and higher throughput provided by HSPA, the promotion to
voice call capacity per cell is from 50% to 100% via CS voice over HSPA, which is
compared with CS voice over Rel99 DCH.
CS Call is set up on HSPA in case of UE and the accessed cell both support CS over
HSPA function. In CS voice Radio Access Bearer (RAB) establishment, the
corresponding transport channel and physical channel parameters and resource related
to HSPA will be allocated to set up radio bearer (RB) for CS call.
Due to the HARQ transmission on the uplink and E-DCH scheduler, the voice packets
have inconstant jitter which means that the inter-arrival times of packets is not constant,
but the core network requires that frames are delivered regularly and continuously. ZTE
RAN implements the de-jitter buffer at the RNC to equalize voice data frame before it
enters the circuit-switched CN. Similarly, the jitter introduced on the downlink traffic
should be processed by terminal.
In order to guarantee the QoS of CS Call over HSPA, non-scheduling mode is used
during HSUPA scheduling in the uplink. In the downlink, SPI, GBR and discard time of
Iub can be configured appropriately so that CS call is scheduled with a higher priority
than streaming and background service
ZTE RAN equipment supports that the CS AMR bears on R99 channel or HSPA channel
based on the user priority for the UE that supports CS Voice over HSPA. This feature is
controlled by an RNC level system switch. RAN imports a threshold. If the users priority
is higher than the threshold, the CS AMR service will be beared on R99 channel. And if
the users priority is lower than the threshold, the CS AMR will be beared on HSPA
channel.
Introduced Version
U9.2
Enhanced Function
None
Abbreviation
16QAM
AAL
AAL2
ABR
AC
Access Class
ACK
Acknowledgement
ACL
A-DPCH
AICH
Channel
AISG
AG
Absolute Grant
AGPS
ALCAP
AM
Acknowledged Mode
AMC
AMR
AMR-WB
AMR-NB
ANT
Antenna
APS
ARP
Allocation/Retention Priority
ARQ
AS
Access Stratum
ASC
ATM
AWGN
BBU
BER
BFD
BITS
BLER
BM-SC
BOOTP
Bootstrap Protocol
BSC
BSSMAP
BTS
CAC
CBC
CBE
CBR
CBS
CC
Continuity Check
CC
Chase Combining
CCCH
CCP
CDT
CE
Channel Element
CN
Core Network
COS
Class of Service
CPC
CPEX
Capital expenditure
CPICH
CQI
CS
Circuit Switched
CSTM-1
Channelized STM-1
DCCH
DCH
Dedicated Channel
DC-HSDPA
DF
DHCP
DoS
Denial of Service
DPCCH
DPCH
DPDCH
DPT
DRBC
DRNC
Drifting RNC
DRT
DRX
Discontinuous Reception
DSAR
DSCR
DTCH
DTM
DTX
Discontinuous Transmission
EcN0
the band
E-AGCH
E-HICH
E-DCH
E-DPCCH
E-DPDCH
eNodeB
E-UTRAN NodeB
EPD
E-RGCH
ETWS
E-UTRAN
E-VAM
Evolved VAM
EVC
FACH
F-DPCH
FE
Fast Ethernet
FEC
FIR
FLC
FLD
FP
Frame Protocol
FSN
GA
Geographical Area
GBR
GE
Gigabit Ethernet
GGSN
GMGW
GMSC
Gateway MSC
GPS
GERAN
GSM
GTP
G/U
GSM/UMTS
GWCN
HARQ
HCS
HLR
H-RNTI
HSDPA
HS-DPCCH
HS-DSCH
HS-PDSCH
HS-SCCH
HSUPA
IC
Interference cancellation
IDNNS
IKE
IMA
IMS
IP Multimedia Subsystem
IMSI
IPOA
IP over ATM
IR
Incremental Redundancy
KPI
LA
Location Area
LACP
LCS
Location Services
LMMSE
LMT
LTE
M3UA
MAC
Medium Access
MBMS
MBR
MCCH
MCPPP
Multi-Chasis PPP
MCS
MEP
MEG
MGW
Media GateWay
MICH
MIMO
Multiple-Input Multiple-output
MLPPP
Multilink-PPP
MME
MMS
MOCN
MPC
MPO
MR
Measurement Report
MRR
MSC
MSCH
MSTP
MTCH
MTP3B
MTU
MUD
NACC
NACK
Negative Acknowledgement
NAS
Non-Access Stratum
NAT
NBAP
NBR
NCP
N-ISDN
NITZ
NNSF
NRI
NRT
Non-Real Time
NTP
OAM
OMC
OMCR
OPEX
Operating expenses
OSPF
OVSF
PA
Power Amplifier
PCI
Pre-coding Index
PDP
PDU
PF
Proportional Fair
PHS
PICH
PIR
PLMN
POS
PPA
PPD
PPP
Point-to-Point Protocol
PRACH
PS
Packet Switched
PSTN
PtM
Point-to-Multipoint
PtP
Point to Point
PVC
PWS
QAM
QoS
Quality of Service
QPSK
RA
Routing Area
RAB
RACH
RAN
RANAP
RAT
RB
Radio Bearer
RF
Radio Frequency
RG
Relative Grant
RL
Radio Link
RLC
ROHC
RR
Radio Resources
RRC
RRM
RRU
RNC
RNSAP
RSCP
RSEPS
RSU
RT
Real-Time
RTCP
RTP
RTR
RRU Transceiver
RTT
Round-Trip Time
RTWP
SA
Service Area
SAI
SABP
SCCP
SCCPCH
SCUDIF
SDH
SDP
SF
Spreading Factor
SFN
SG
Scheduling Grant
SGSN
SIB
SIP
SIR
Signal-to-Interference Ratio
SLA
SMLC
SMS
SMS-CB
SNA
SNR
Signal-to-noise ratio
SNTP
SONET
SPI
SRB
SRNC
SRNS
Serving RNS
SR-VCC
SSCF
SSCOP
STM-1
STTD
TB
Transport Block
TC
Traffic Class
TCP
TDM
Time-division multiplexing
TFI
TFO
TFRC
THP
TM
Transparent Mode
TPC
TrCH
Transport Channel
TrFO
TTI
UBR
UBR+
UDI
UE
User Equipment
UEA
3G Encrypt Algorithm
UM
Unacknowledged Mode
UMTS
URA
USIM
UTRAN
VAM
VBR
VC
Virtual Circuit
VLAN
VoIP
Voice over IP
VP
Virtual Path
VSWR
WCDMA
WRR