ZTE UTRAN UR11.1 Optional Feature Descriptiondocshare01.docshare.tips/files/30959/309597685.pdf ·...

UTRAN UR11.1 Optional Feature Description

PDF 文件使用 "pdfFactory Pro" 试用版本创建 www.fineprint.cn

http://www.fineprint.cn



UTRAN UR11.1 Optional Feature Description Version Date Author Reviewer Notes

V1.70 2012/04/05 ZTE Not open to the third party

© 2012 ZTE Corporation. All rights reserved.

ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used

without the prior written permission of ZTE.

Due to update and improvement of ZTE products and technologies, information in this document is subjected to

change without notice.





FIGURES

Figure 1-1 Logical Architecture of CBS System ................................................................... 7

Figure 2-1 An example of DSAR activated for both CS domain and PS domain ................ 14

Figure 2-2 Enhanced Iur-g Handover Procedure ............................................................... 21

Figure 2-3 Handover from UMTS to GERAN ..................................................................... 24

Figure 2-4 Handover from GERAN to UMTS ..................................................................... 25

Figure 2-5 Handover from UMTS to GSM .......................................................................... 26

Figure 2-6 Handover from GSM to UMTS .......................................................................... 27

Figure 2-7 UTRAN to E-UTRAN Inter RAT HO .................................................................. 30

Figure 2-8 E-UTRAN to UTRAN Inter RAT HO .................................................................. 31

Figure 2-9 SR-VCC............................................................................................................ 33

Figure 2-10 Video Call Fall-Back to Voice .......................................................................... 41

Figure 2-11 Schematic Diagram of the Iu Flex Networking ................................................ 49

Figure 2-12 Networking under MOCN Network Sharing ..................................................... 52

Figure 2-13 Networking under GWCN Network Sharing .................................................... 52

Figure 2-14 Dedicated Frequency Sharing Network .......................................................... 54

Figure 2-15 Four operators shared Iub interface ................................................................ 58

Figure 2-16 PA Efficiency with D-PT Technology ............................................................... 68

Figure 2-17 Mechanism of Four-Antenna Receiving Diversity ............................................ 72

Figure 2-18 Logical Connection of Transmit Diversity ........................................................ 74

Figure 2-19 Electrical Tilt Antenna System ........................................................................ 75

Figure 2-20 A-RAKE receiver structure .............................................................................. 80

Figure 3-1 ATM Protocol Stack of IuCS Interface .............................................................. 86

Figure 3-2 ATM Protocol Stack of IuPS Interface ............................................................... 87

Figure 3-3 ATM Protocol Stack of Iur Interface .................................................................. 88

Figure 3-4 ATM Protocol Stack of Iub Interface ................................................................. 89

Figure 3-5 AAL2 QoS Differentiation .................................................................................. 93

Figure 3-6 VLAN Tag ....................................................................................................... 103

Figure 3-7 PPP/MLPPP Protocol Stack ........................................................................... 115





Figure 3-8 Application of IEEE 1588 Clock Synchronization ............................................ 125

Figure 3-9 IP Protocol Stack on Iub Interface................................................................... 126

Figure 3-10 Iub Interface Transmission through the Satellite ........................................... 128

Figure 3-11 IP Protocol Stack on IuCS Interface .............................................................. 129

Figure 3-12 IP Protocol Stack on IuPS Interface .............................................................. 131

Figure 3-13 DS0 Cross Connection ................................................................................. 132

Figure 3-14 IP Protocol Stack on Iur Interface ................................................................. 138

Figure 3-15 LACP ............................................................................................................ 141

Figure 4-1 16 QAM Constellation Graph .......................................................................... 157

Figure 7-1 Basic Principle of 2×2 MIMO Technical Solution ............................................. 240

Figure 7-2 VAM Option with MIMO .................................................................................. 242

Figure 7-3 F-DPCH Multiplexed ....................................................................................... 245

Figure 7-4 Enhanced UE DRX ......................................................................................... 252

TABLES

Table 2-1 Types of Transmit Diversity and Physical Channel Supported by ZTE ............... 73

Table 3-1 Types of AAL Services....................................................................................... 83

Table 3-2 Features of Various ATM Services..................................................................... 85

Table 4-1 HSDPA UE Category Supported by ZTE current version ................................. 146

Table 6-1 HSUPA UE Category Supported by ZTE ......................................................... 207





1 Services and Radio Access Bearers

1.1 ZWF21-02-020 WB-AMR Speech Support

Benefits

This feature can provide high quality of voice which makes the voice more natural, and

provide high quality telephone, voice and conference video services.

Description

AMR-WB, which is the abbreviation of Adaptive Multi-Rate Wideband, is a wideband

voice coding standard adopted by both ITU-T and 3GPP. It is also called G722.2

standard. Since AMR-WB supports 50~7000Hz speech bandwidth and employs 16KHz

sampling, compared with 300 to 400Hz speech bandwidth and 8KHz sampling supported

by AMR-NB, users can feel the voice more natural, more comfortable and more

distinguishable.

ZTE RAN equipment supports all the nine speech rates of WB-AMR sessions, which are

23.85Kbps, 23.05Kbps, 19.85Kbps, 18.25Kbps, 15.85Kbps, 14.25Kbps, 12.65Kbps,

8.85Kbps, and 6.6Kbps, together with the mute rate 1.75 Kbps. The feature also

supports any combination of the above rates. Whether WB-AMR coding is used and what

rates to be used are decided by CN according to user’s signing information and the

terminal capability.

The RAB parameters of ZTE RAN equipment, used to bear sessions of AMR-WB service,

follow the definition in the 3GPP TS 34.108.

Introduced Version

U9.1&Before

Enhanced Function

No





1.2 ZWF21-02-022 PS Signaling RAB for IMS

Benefits

This feature supports signaling transmission of IMS system (using SIP or SDP protocol).

Description

The IMS employs the Session Initiation Protocol (SIP) and the Session Description

Protocol (SDP) to control services. As defined in the 3GPP 25.862, the SIP/SDP

exclusively occupies an RAB. The SIP/SDP does not require high bandwidth, which

generally corresponds to 5% of media stream bandwidth. It has certain requirements for

delay and no packet loss is allowed. Therefore, the data transmission model is similar to

that of interactive services. But IMS signaling needs to be ensured to have a higher QoS

priority than other common traffic classes. Besides the four existing traffic classes, a new

traffic class needs to be defined to transmit SIP/SDP signaling. On the basis of

interactive services, the 3GPP has defined a new parameter to indicate that this RAB

bears SIP/SDP signaling.

For PS-based voice or video services in the IMS, the UMTS uses an interactive PDP

context to bear SIP/SDP signaling and uses another session PDP context to bear

RTP/RTCP stream. These two PDP contexts have the relationship between primary

activation and secondary activation. That is, they have the same PDP address. This

ensures that signaling flow and media stream are consistent in IP routing.

UE initiates the SIP/SDP PDP (primary PDP) activation flow first. The CN assigns an

interactive class RAB and configures signaling indication for it. This indicates that this

RAB bearer is IMS signaling and this RAB requires high priority, low delay, but small

bandwidth. Then, UE initiates the second PDP (secondary PDP) activation flow. The CN

assigns a PS conversational RAB to bear IMS voice or video packet stream. And this

RAB requires high priority and low delay.

ZTE RAN equipment supports the IMS signaling which is compliant to 3GPP TS 34.108.

According to the RAB parameters assigned by the CN, the RNC judges whether an

interactive RAB bears common user data or IMS signaling. If the interactive service

bears IMS signaling, the RNC will provide an extra QoS class for this interactive service.





Introduced Version

U9.1&Before

Enhanced Function

No

1.3 ZWF21-02-025 Cell Broadcast Service

Benefits

This feature is used to support cell broadcast short message service and could be

utilized to deploy text broadcast services like weather forecast, traffic information and etc.

ETWS is expected to be deployed based on CBS system to alarm people in the area

where disaster, for example earthquake, typhoon and tsunami, takes place.

Description

CBS is a basic tele-service defined by UMTS to supply text broadcast service in the

mobile telecommunication system, and is called SMS-CB as well. The main difference

between CBS and SMS lies in that the receiving target of SMS is a specific user in the

network but the target of CBS involves all users in a certain area, including roaming

users. The minimal granularity of address of CBS is a cell in PLMN. The content of CBS

could be but not limited to: service notice, weather forecast, traffic information,

international and domestic news, emergency events, advertising and etc.

The logical architecture of CBS system is shown in Figure 1-1.

Figure 1-1 Logical Architecture of CBS System

Uu Iu

CellBroadcast

Center

(CBC)

UTRAN

RNCNode B

Node BUE

UE

1

RoutingNode(e.g.3G-

SGSN)

IubBc





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 ZWF21-02-A VoIP Package

1.4.1 ZWF21-02-021 PS Conversational RAB for VoIP

Benefits

This feature provides IMS video and voice service, that is, it provides radio access bearer

for PS AMR or WB-AMR services in PS domain. Coded voice and video data is

encapsulated in IP packets.

Description





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.

− Support the establishment of PS IMS signaling RAB to bear SIP/SDP stream.

For details, refer to the function ZWF21-02-022 PS IMS Signaling Bearer.

− Support the reduction of IP header overhead in VoIP packets by means of the

PDCP header compression algorithm. For details, refer to the function

ZWF21-06-020 Robust Header Compression.

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 ZWF21-06-020 Robust Header Compression

l 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

plan unable to work well. First, a radio channel has path loss and must bear 10-1~10-3 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 ZWF23-02-005 PS Conversational RAB for VoIP over HSDPA

Benefits

This feature supports IMS video and voice services over HSDPA.

Description

This feature supports PS session RAB over an HS-DSCH channel to support AMR or

WB-AMR services in an IMS subsystem. Coded voice and video data is encapsulated in

an IP packet and transmitted. The SIP/SDP data stream and RTCP data stream of VoIP

service are characterized with bursts. The DCH bearer which employs semi-static

configuration mode is not good for the effective use of system resources. The effective

multiplexing and fast scheduling of the HS-DSCH are better for VoIP service bearer. The

spectral efficiency of the HS-DSCH is higher than that of DCH. It also helps improve the

VoIP service capacity of the system.

For VoIP service information, please refer to the function ZWF21-02-021 PS Session

VoIP Service Bearer.

Introduced Version

U9.1&Before

Enhanced Function

No





1.4.4 ZWF25-02-005 PS Conversational RAB for VoIP over HSUPA

Benefits

This feature supports IMS video and voice services over HSUPA.

Description

This feature supports PS session RAB over an E-DCH channel to support AMR or

WB-AMR services in an IMS subsystem. Coded voice and video data is encapsulated in

an IP packet and transmitted. The SIP/SDP data stream and RTCP data stream of VoIP

service are characterized with bursts. The DCH bearer which employs semi-static

configuration mode is not good for the effective use of system resources. The effective

multiplexing and fast scheduling of the E-DCH are better for VoIP service bearer. The

spectral efficiency of the E-DCH is higher than that of a DCH. It also helps improve the

VoIP service capacity of the system.

For VoIP service information, please refer to the function ZWF21-02-021 PS Session

VoIP Service Bearer.

Introduced Version

U9.1&Before

Enhanced Function

No

2 Radio Network Functionality

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 ZWF21-01-018 Domain Specific Access Restriction (DSAR)

Benefits

This feature enables operator to efficiently control access to a specific Core Network

domain under critical conditions (e.g. emergency situations, situation of overload, etc.) to

avoid performance problems due to the user traffic’s exceeding the network capacity.

Description

A normal UMTS UE is assigned an access class (AC) randomly from 0 to 9; this is stored

in USIM card. A special UE may also be assigned an AC from 11 to 15; these would be

typically used by emergency services (for example, fireworks, ambulance). AC with 10 is

used for emergency calls. A mapping between AC and Access Service Class (ASC) is

indicated in SIB 5 or SIB 5bis. The ASC determines certain parameters for an RACH

procedure and controls the priority of the access to the RACH. A lower ASC has a higher

priority to access to the channel.





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

x ooxoAC9

x ooxoAC8

ox oxoAC7

x ooxoAC6

oxoxoAC5

oxoxoAC4

oxox oAC3

oxoxoAC2

oxox oAC1

oxox oAC0

10987654321

x ooxoAC9

x ooxoAC8

ox oxoAC7

x ooxoAC6

oxoxoAC5

oxoxoAC4

oxox oAC3

oxoxoAC2

oxox oAC1

oxox oAC0

10987654321

Timer (minute)Timer (minute)

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 ZWF21-01-020 27.2Kbps High Speed Signaling RB

Benefits

This feature helps to reduce the time delay for CS/PS service setting up, and shorten

SMS services reception. It improves user experience.

Description

This feature enables the system to use the 27.2 kbps Signaling Radio Bearer (SRB)

when it establishes the RRC connection, and recovers the 3.4Kbps SRB after RAB is

established. If 27.2k SRB is set to apply on OMC, ZTE RAN will employ 27.2kbps SRB to

speed up transferring the NAS signaling messages (including location update message,

authentication message, and call setup message) between the UE and the CN.

Compared with 13.6kbps SRB, the 27.2 kbps SRB can reduce the call setup time delay

by several hundreds of ms and shorten the SMS service reception in different scenarios.

Introduced Version

U9.2





Enhanced Function

No

2.1.4 ZWF21-01-022 Deferred SIB11/12

Benefits

When numbers of neighboring cells have been configured, reading and storing these

neighboring cells information after cell reselection or channel type switching procedure

will take a longer time. And this may result in service outrage. Deferred SIB11/12 feature

can decrease servcie outrage and enhance user experience.

Description

Due to SIB11, SIB11bis or SIB12 should be read and stored by the UE before sending

message or acting on received message on FACH after the process of cell reselection or

channel type switching, in case that a lot of neighbouring cells are configured (over 20

neighboring cells for example), this will cause the obvious interruption of services. To

solve this problem, in 3GPP R7 specification, UE is allowed to send messages through

RACH or receive messages through FACH before reading and storing SIB11/12

information.

UTRAN broadcasts through SIB3 to notice if the network supports this feature. If the

feature is applied, UE’s switching to CELL-DCH status must notify the UTRAN that

SIB11/11bis/12 are not read and stored. After switching to a non CELL-DCH status, UE

needs to complete SIB11/11bis/12 reading and storing.

This feature complies with TS 25.331 CR2557R2.

Introduced Version

U9.3

Enhanced Function

No





2.1.5 ZWF21-01-025 Ciphering Algorithm UEA2

Benefits

Besides UEA1, an alternative encryption algorithm is offerd to make the network safer.

Subscriber class differentiated Ciphering service can be realized.

Description

This feature realizes UEA2, which is known as f8 and is specified in 3GPP R7. The

algorithm f8 is used to protect the confidentiality of the data and signaling sent between

the UE and the RNC.

The followings are the differences between UEA2 and UEA1:

− UEA1 is KASUMI based algorithm and UEA2 is SNOW 3G based algorithm.

− KASUMI is a Blockcipher with 64-bit block, 128-bit key. SNOW 3G is a 32-bit

word-oriented stream cipher generator with 128-bit key and 128-bit IV.

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

l Enhanced Function

No

2.1.6 ZWF21-01-026 Integrity Protection Algorithm UIA2

Benefits





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:

− UIA1 is KASUMI based algorithm and UIA2 is SNOW 3G based algorithm.

− KASUMI is a Blockcipher with 64-bit block, 128-bit key. SNOW 3G is a 32-bit

word-oriented stream cipher generator with 128-bit key and 128-bit IV.

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.


U9.3

l Enhanced Function

No

2.2 Mobility Management

2.2.1 ZWF21-03-012 Transmitted Power Based Handover

Benefits





This feature is used to guarantee user’s 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 hasn’t

reached the threshold which can trigger the coverage based handover, but UE’s uplink

transmitting power or Node B’s 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

can’t guarantee UE’s 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 ZWF21-03-013 Quality Based Handover

Benefits

This feature guarantees user’s communication quality, and reduces the call drop rate.

Description





In the real network, there may exist such a scenario: the quality of pilot signal hasn’t

reached the threshold which can trigger the coverage based handover, but the UE’s

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 can’t guarantee

UE’s QoS anymore. To avoid call drop, it is necessary to hand over UE to other

inter-frequency cell.

ZTE RNC equipment detects certain user’s uplink connection. Once the quality of the

connection can’t 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 ZWF21-03-014 Enhanced Iur-g

Benefits

This feature supports the enhanced Iur-g interface between GERAN BSC and 3G RNC.

By employing this interface, inter-RAT handover procedure is able to be optimized, so

the time delay of the handover is shortened, the success rate of the handover is

increased, and user experience is improved. Meanwhile, the delay of handover from 3G

to 2G can be reduced.

Description

The handover between controllers includes two phases: handover preparation and

handover execution. Typically, inter-RAT handover preparation needs 600ms, which

increases the delay of handover and the possibility of resource block, namely the

handover failure and call drop rate are increased.





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.

Figure 2-2 Enhanced Iur-g Handover Procedure

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 ZWF21-03-021 Hierarchical Cell Structures

Benefits

This feature supports building hierarchical cell coverage in areas with high subscriber

density to realize higher system capacity, more efficient mobility management and more

efficient radio resource management (RRM) strategy.

Description

The hierarchical cell structure (HCS) describes a wireless system in which cells of at

least two layers (such as macro cells and micro cells) are overlaid. Macro cells provide

continuous coverage, whereas micro cells absorb traffic. In general, different cells use

different frequencies. Low-mobility and high-rate UEs should camp on micro cells, while

high-mobility and low-rate UEs should camp on macro cells as much as possible so as to

reduce handover and improve the spectral efficiency and system capacity. The essential

aim of HCS is to improve network capacity and QoS.

The feature supports informing the UE whether the cell adopts HCS networking, which

priority level is chosen in HCS cell (the range is from 0 to 7, 0 is the lowest, and 7 is the

highest), and the reselection parameters in other cells in cell system information

broadcast so that the UE can camp on micro cell to absorb more traffic according to cell

reselection algorithm which is defined in 3GPP TS 25.304.

This feature also supports the detecting of user’s moving speed by RNC through

monitoring the number of times that UE changes its best cell in a certain period. If the

number is larger than a threshold, it is reasonable to consider the UE is at a high speed.

At this moment, once the UE is connected with a micro cell which uses HCS architecture,

RNC will automatically hand over it to an HCS Marco cell to reduce the handovers. On

the other hand, if the number of times is smaller than a threshold, it is reasonable to

consider the UE is static. At this moment, once UE is connected with a macro cell which

uses HCS architecture, RNC will initiate inter-frequency measurement. In the case that

micro cell can supply a better coverage, RNC will hand over the UE to an HCS micro cell

to absorb traffic and thus the capacity of the network is enhanced.





Introduced Version

U9.1&Before

Enhanced Function

No

2.2.5 ZWF21-03-022 IMSI Based Handover

Benefits

This feature supports handover mechanisms based on user’s IMSI number.

Description

IMSI-based handover can limit the handover target cell range according to UE’s IMSI.

The scope of authorized cells based on the IMSI information on the network side can be

configured. The IMSI information is resolved through the Common ID on lu interface

during service setup or handover, and UE is not allowed to access or handover to

unauthorized cells.

ZTE RAN equipment supports that when a UE tries to access an unauthorized cell, if

there is an authorized adjacent cell with different frequency or GSM cell that has the

same coverage with the cell the UE want to access, inter-frequency hard handover flow

or inter-system handover flow will be triggered to connect the UE to an authorized cell.

Introduced Version

U9.1&Before

Enhanced Function

No

2.2.6 ZWF21-03-023 Inter-RAT PS Handover

Benefits





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 Handover from UMTS to GERAN

BSSMAP BSSMAP

PS Handover Request ACK

RANAP RANAP

Iu Release Complete

BSSMAP BSSMAP

PS Handover Request

RANAP RANAPRelocation Command

BSSMAP BSSMAP

PS Handover Complete

RANAP RANAPRelocation Required

UE Node B RNC PS CN BSC

RRC

Handover from UTRAN Command RRC

RANAP RANAP

Iu Release Command

First correctly received RLC/MAC block

(XID Resp., RAU req. or Cell Update)

（PS handover）





Figure 2-4 Handover from GERAN to UMTS

RANAP RANAPRelocation

RequestBSSMAP BSSMAP

RANAP RANAP

BSSMAP BSSMAP

PS Handover Required Ack

BSSMAP BSSMAP

BSSMAP BSSMAPClear Complete

RANAP RANAP

Relocation Complete

UE Node B RNC PS CN BSC

RRC Handover to

UTRAN Complete RRC

RR RR

RANAP RANAPRelocation

Detect

PS Handover Required

Relocation Request ACK

PS Handover Command

Clear Command

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 ZWF21-03-024 DTM Handover

Benefits

This feature guarantees the CS service continuity combined with PS service during

Inter-RAT moving. It improves user experience.

Description





When a user is establishing CS service and PS service simultaneously and moving

between inter-RAT adjacent cells, CS service and PS service are handed over to

inter-RAT cell in parallel via DTM (Dual Transfer Mode) mechanism. The message flow

of DTM handover is shown as below, without the message within CN:

Figure 2-5 Handover from UMTS to GSM

BSSMAP BSSMAP

RANAP RANAP

Iu Release Complete

BSSMAP

RANAP RANAP

UE RNC CS CN PS CN BSC

RRC RRC

RR RR

RANAP RANAP

Iu Release Command

RANAP RANAP

Relocation Required

Relocation Required

BSSMAP BSSMAP

B SSMAP

PS Handover Request

BSSMAP BSSMAP

Handover Request Ack

Handover Request

PS Handover Request Ack

RANAP RANAP

RANAP RANAP

( L3 information : DTM handover Comma nd)

Command

(Target BSS to Source BSS Transpatent container: DTM handove r Command)

Relocation CommandHandover f rom UTRAN Command

( DTM handover Comma nd)

BSSMAP BSSMAPHandover Detect

BSSMAPHandover Detect

7 . Handover Complete

BSSMAPBSSMAPHandover Complete

PS Handover CompleteBSSMAP BSSMAP

RANAP

Iu Release Complete

RANAP RANAP

Iu Release Command

RANAP

BSSMAP

Relocation





Figure 2-6 Handover from GSM to UMTS

BSSMAP BSSMAP

PS HandoverRequired

RANAP RANAP

Relocation Request Ack.

BSSMAP BSSMAPPS Handover

Required Ack

RANAP RANAPRelocation Complete

RRC

Handover to UTRAN Complete

RRC

RRDTM Handover Command

RR

RANAP RANAPRelocation Detect

BSSMAP BSSMAPHandover Required

RANAP RANAPRelocation Request

RANAP RANAPRelocation Request

RANAP RANAP

Relocation Request Ack.

BSSMAP BSSMAPHandover Command

RANAP RANAPRelocation Detect

RANAP RANAPRelocation Complete

UE RNC CS CN PS CN BSC

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 doesn’t search the target cell’s 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 ZWF21-03-026 Target cell Load based inter-RAT HO

Benefits





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 cell’s 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 ZWF21-03-110 Handover with LTE

Benefits

This feature guarantees PS service continuous when user moving between UMTS

coverage and LTE coverage.





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 UTRAN to E-UTRAN Inter RAT HO

UETarget

eNodeB

Forward Relocation Request

Handover from UTRAN Command

Relocation Required

SourceRNC

Handover request

Handover Request Acknowledge

SourceSGSN

TargetMME

Handover Initiation

Forward Relocation Response

Relocation Command

E-UTRAN access procedure

Handover to E-UTRAN CompleteHandover 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.





Figure 2-8 E-UTRAN to UTRAN Inter RAT HO

UETargetRNC

Forward Relocation Request

Handover from E-UTRAN Command

Handover Required

SourceeNodeB

Relocation Request

Relocation Request Acknowledge

SourceMME

TargetSGSN

Handover Initiation

Forward Relocation Response

Handover Command

UTRAN access procedure

Handover to UTRAN CompleteRelocation 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.





Figure 2-9 SR-VCC

13. Handover Command

1. Measurement reports

3. Handover Required

2. Decision for HO

5a. PS to CS Req

17a. Reloc/HO Complete

17b. SES (HO Complete)

17c. ANSWER

12. PS to CS Resp

18a. Reloc/HO Complete

18c. Update bearer

HSS/HLR

17e. UpdateLoc

5b. Prep HO Req

8b. Prep HO Resp

8c. Establish circuit

6a. Forward Reloc Req 6b. Reloc /HO Req

5c. Reloc /HO Req

8a. Reloc /HO Req Ack

7b. Forward Reloc Resp 7a. Reloc /HO Req Ack

11. Release of IMS access leg

10. Session transfer and update remote leg

9. Initiation of Session Transfer (STN-SR or E-STN-SR)

UE Source E-UTRAN

SourceMME

MSC Server/MGW

TargetMSC

Target RNS/BSS

SGW IMS (SCC AS)

TargetSGSN

14. HO from EUTRAN command

17d. PS to CS Complete/Ack

18b. Forward Reloc Complete/Ack

16. HO Detection

4. Bearer Splitting

15. UE tunes to UTRAN/GERAN

17f. TMSI Reallocation

Introduced Version

UR11.1

Enhanced Function

No.

2.3 Radio Resource Management

2.3.1 ZWF21-04-005 AMR Rate Controlling

Benefits





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 ZWF21-04-024 User Differentiated Power Control

Benefits





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 ZWF21-05-016 Video Call Prohibited in Specific Area

Benefits

This feature enables the system to suspend the video call service for a specific cell.

Description

The UMTS network provides the video call service. In some areas with security control or

areas with privacy protected, the video call service is prohibited and it is necessary to

suspend the service in the network layer.





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 ZWF21-05-020 RAB Negotiation & Re-negotiation

Benefits

This feature enables the system to select the QoS service for the user according to the

load of the RAN, which heightens the success rate of service access and lowers call drop

rate.

Description

The RAB QoS negotiation and re-negotiation require the cooperation between RNC and

CN. When the CN configures the RAB QoS, CN assigns the MBR (maximum bit rate)

and GBR in the RANAP message to RNC. And a new IE (Alternative RAB Parameter

Values) is adopted in the RAB assignment and relocation request message. CN will

assign another set of QoS parameter in this IE. In general, the QoS parameter in this IE

is smaller than in the normal RAB parameter. RNC will choose the QoS in these two sets

based on the current system load. If the system load is heavy, RNC will choose the QoS

set assigned in Alternative RAB Parameter Values IE to reduce the resource

consumption. When the resources of the system are scarce, the RNC selects the QoS of





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:

− The renegotiation is triggered by the network

When the PDP context is activated, if the network loads change or the service

changes, the CN triggers a QoS modification process to modify the E2E QoS

parameters and then the RAB reassignment process modifies the RAN radio

bearer.

− The renegotiation is triggered by the RNC

The RNC may initiate RAB modification request to the CN according to the

load of a cell. When the load of the access network is very high, the RNC

provides services at lower bit rates through negotiation; when the load of the

access network is very low, the RNC provides services at high bit rates

through negotiation. By defining parameters in Alternative RAB Parameter

Values in the RAB assignment message, the CN specifies whether the RNC

can execute negotiation and operate at negotiable bit rates.

Introduced Version

U9.1&Before





Enhanced Function

No

2.4.3 ZWF21-05-022 Service-Based Handover

Benefits

This feature supports handover strategies from UMTS to GSM according to CN

configuration so that operators can control service distribution between two networks

according to load situation or user priority.

Description

This feature decides whether to hand over and when to hand over service to GSM

according to the attribute “service handover” in RAB assignment message:

− Handover to GSM should be performed: it means that it is necessary to hand

over to GSM as soon as possible after the service is set up successfully.

− 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

enabling/disenabling per cell are introduced in U9.3.

In UR11.1 ZTE RAN can abbey the indication of “E-UTRAN Service Handover”.

2.4.4 ZWF21-05-024 Video Call Fallback to Speech

Benefits

The GSM system does not support the CS video call defined by the 3GPP. When a user

moves from the UMTS system to the GSM system, this feature can automatically make

the video call fall back to the voice service, and then implement the inter-system

handover, thus reducing the call drop rate of the video call service.

Description

In the initial network construction, the UMTS system usually cannot provide complete

coverage. If the GSM adjacent cells exist at the edge of the UMTS network or areas with

poor UMTS coverage, it is necessary to switch the user from the UMTS to the GSM

system so that the services can be provided continuously.





Figure 2-10 Video Call Fall-Back to Voice

UE Node BServing RNS

Serving RNC

CN

RRCRRC 7. DCCH : Radio Bearer Reconfiguration Complete

NBAPNBAP 4. Radio Link Reconfiguration Ready

NBAPNBAP 5. Radio Link Reconfiguration Commit

RRCRRC6. DCCH : Radio Bearer Reconfiguration

RANAP RANAP8. RAB Assignment

Response

RANAP RANAP2. RAB Assignment

Request[Modification]

NBAPNBAP 3. Radio Link Reconfiguration Prepare

RANAP RANAP1. RAB Modification

Request

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 User Plane Process

2.5.1 ZWF21-10-001 Cell ID & RTT Positioning

Benefits

This feature supports location service based on cell ID. Cell ID positioning does not

require additional hardware and investment is little. It provides large coverage and rapid

positioning delay, suitable for location service with low requirement on accuracy.

Description

When a location request is received from CN, a proper location method is selected

according to the requirement on accuracy. After UE position is calculated, the result is

reported to CN.

According to the reporting method involved in the location request, the RNC reports

service area (SA) or geographical area (GA) to CN.

− 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,





location calculation is achieved by UE and UE reports the calculation result to network

side. For the A-GPS, the location result is reported with ellipsoid point with altitude and

uncertain Ellipsoid.

ZTE RNC completes location calculation with their built-in Iu-PC interfaces and SMLC

function, helping the operators reduce the cost for purchasing additional SMLC devices.

The accuracy of A-GPS positioning has an advantages of 5 to 50 meter over the cell

ID+RTT methods.

According to the location request from the CN, the RNC can report the measurement

results immediately or when SA where UE resides changes.

Additional GPS antenna and the feeder are needed because they are not included in

RNC and Node B equipment.

Introduced Version

U9.1&Before

Enhanced Function

No

2.5.3 ZWF21-10-003 Emergency Call Re-direct to GSM

Benefits

If location service is not provided in UMTS system, or accuracy of location service in

UMTS system is not high, this feature makes use of location service in 2G network to

give the location information of a user in an emergency call. With the location information,

emergency assistance could be provided in time by some rescue organization.

Description

Emergency call is always requested by a user in certain emergency situations. If the

location of a user in emergency is identified, assistance would be provided without delay.

When location service is not provided in UMTS system or the accuracy of location





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 network’s 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 ZWF21-10-004 LCS Classified Zones

Benefits

This feature enables operators to acquire the information of specific areas when a UE

enters or leaves these areas so that operators can deliver user-location-based services.

Description

ZTE RAN equipment can specify areas (usually a cell or a set of cells) in OMC. When a

UE enters or leaves these areas, the RNC automatically reports location information of

the UE to the CN by SA method.

With this feature, operators can deliver user-location-based services such as alarm

messages to UEs when they enter these areas.

Introduced Version

U9.1&Before





Enhanced Function

No

2.5.5 ZWF21-10-005 LCS over Iur

Benefits

Increase the precision of location service, including CellID based LCS, CellID+RTT

enhanced LCS, UEB AGPS LCS, LCS Classified Zones

Description

Generally the realization of LCS is limited in the scenario, where the best cell of the

active set of the UE is only in the SRNC, and the measurement of RL of inter Iur can’t be

done. The feature LCS over Iur supports UE’s LCS even when some RLs in DRNC .

If the best RL in the active set is in DRNC, LCS information and NodeB measurement

result are exchanged through Iur between SRNC and DRNC,

− Cell ID LCS, Cell ID+RTT enhanced LCS

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

− LCS Classified Zones

Supporting Iur direct neighbor cell reported as LCS Classified Zones

Introduced Version

UR11.1





Enhanced Function

No

2.6 RAN Management

2.6.1 ZWF21-20-017 Intelligent Carrier Power Off/On

Benefits

This feature enables the system to close some carrier frequencies in the multi-carrier

sector when the traffic volume is very low, thus reducing power consumption of

equipments and the operator's OPEX.

Description

The load of the telecom system varies greatly within a day. During peak traffic hours in

the daytime, the system needs multiple carrier frequencies (for example, S333) to carry

services; at night, one carrier frequency (S111) is enough. When the traffic volume is

very low, the system still uses multiple carrier frequencies to carry services. Though the

load of each carrier frequency is not very high, each carrier frequency needs common

channels such as the pilot channel. The power of the common channels covers 20% of

the transmitting power of the overall carrier frequencies.

The intelligent carrier power off/on technology of the ZTE RAN can automatically monitor

the network service status. When the traffic volume is relatively low, the RAN

automatically closes idle carrier frequencies. If the RAN finds that the traffic volume

increases to such a threshold that the current working carrier frequencies cannot handle

the extra services, it starts the closed carrier frequencies.

When the traffic volume is very low and it is necessary to close some carrier frequencies,

the intelligent carrier power off/on technology can gradually reduce the maximum

transmitting power of a cell until the RF units on the redundant carrier frequencies are

switched off. In this way, the small traffic in the closed cell can hand over to the adjacent

cell smoothly.





Introduced Version

U9.1&Before

Enhanced Function

No

2.7 Enhanced RAN Functionality

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.





Figure 2-11 Schematic Diagram of the Iu Flex Networking

Compared with traditional networks, the networking based on the Iu Flex technology has

the following advantages:

− Load sharing and disaster recovery

The capacity of an RNC has been increased, even higher than that of an MSC

Sever or SGSN. In traditional networking, the actual capacity of RNC has been

restricted since only one MSC Server/SGSN is allowed to connect to one RNC.

With all MSC Servers/SGSNs forming a pool area, the capacity of all CN

nodes in pool area are combined to connect to more RNCs. Network load is

shared among MSC Servers/SGSNs. And the CN nodes in pool area back up

for each other. If one is down, the traffic of the CN node is transferred to other

CN nodes.

− Reducing signaling load of mobility, increasing the actual capacity of the

network

If there are too many subscribers, equipment capacity will be a limitation and

Area 1

RANnode

Area 5

RANnode

Area 6

RANnode

Area 7

RANnode

Area 8

RANnode

Area 2

RANnode

Area 3

RANnode

Area 4

RANnode

PS pool-area 2PS pool-area 1

CS pool-area 2CS pool-

area 1

MSC 3MSC 2

MSC 1

MSC 6MSC 5

MSC 4

SGSN 6

SGSN 2

SGSN 1

SGSN 5SGSN 4

SGSN 3

MSC 7





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.

− If there is no NRI information or CN nodes have problems or the CN load is

high, the RNC will reselect a CN node to establish a signal and traffic

connection so as to achieve load-sharing and redundancy protection.

− 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.

− Configuration of Preferred Pool Area (PPA) supported, the CN equipment in

PPA pool will be selected with a higher priority to serve UE. This feature can

increase the flexibility of Iu Flex configuration.

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 ZWF21-30-A RAN Sharing Package

2.8.1 ZWF21-30-100 Basic RAN Sharing Support

Benefits

This feature allows multiple operators to use the same UTRAN resources to provide their

own services. In this way, the operator can shorten the network construction, save the

investment on site acquisition, site construction, transmission construction, and wireless

network devices, and greatly decrease the cost in network construction and operation.

Description

ZTE RNC can be connected to one or more CN equipments belonging to multiple

operators, allowing multiple operators to share many kinds of UTRAN resources and

equipments including RNC cabinet and boards, OMC devices, Node B cabinets,

baseband processing boards, RF units and feeder cable system, and other RAN

auxiliaries (including power and transmission lines of the Iub/Iur interface).

ZTE RAN supports two UTRAN network sharing modes defined by the 3GPP:

− Multi-Operator Core Network (MOCN)





Figure 2-12 Networking under MOCN Network Sharing

Radio Access N etw orkOperator X

C N O perator A

C NOperato r B

C NO perator C

RNC

Iu

N ode B No de B

In this network sharing mode, different operators construct CN devices

separately. All CN devices are connected to the same RNC and share the

RAN resources.

− Gateway Core Network (GWCN)

Figure 2-13 Networking under GWCN Network Sharing

Radio Access NetworkOperator X

SharedMSC/SGSN

SharedMSC/SGSN

SharedMSC/SGSN

RNC

Iu

CNOperator A

CNOperator B

CNOperator C

RNC RNC

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 ZWF21-30-101 RAN Sharing with Dedicated Carrier

Benefits

This feature enables operators to use their own frequency when they share the UTRAN

network. It can prevent the capacity competition of radio resources among several

operators.

Description

If different operators have their own frequency resources, the ZTE RAN equipment

enables the operators to share the UTRAN network with their respective frequencies. All

the UTRAN equipment and resources will be shared except the frequency. The

frequencies of different operators can be deployed in one Node B, sharing the cabinet,

power, and baseband processing boards. According to the operator’s requirements,

these operators can share the FR devices (power amplifier, feeders, and antenna), or

deploy them separately. The frequencies of different operators can also be deployed in

different Node Bs and connected to the same RNC through the Iub interface. Different

operators can share the RNC cabinet, power source, and processing boards in the

control plane and user plane.





Figure 2-14 Dedicated Frequency Sharing Network

Frequency one

Frequency two

Shared RNC

Frequency one

Frequency two

Shared Node B

MNCone

MNCtwo

Operator one

Operator 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 needn’t 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 operator’s cells and user’s 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 ZWF21-30-102 Shared Networks Access Control

Benefits

This feature provides admission control for the UE which is in the DCH status and is in

the shared network or on the boundary of the shared network and unshared network,

according to the subscription relation with the operator. It ensures the user to enjoy the

service of the authorized network during moving.

Description

ZTE RAN supports the access control in Shared Network Area (SNA). Each SNA is

identified by an SNAC. The SNAC is unique in a PLMN. One SNA may contain one or

more location areas (LA), and one LA may belong to several SNAs.

The serving area for user is configured in the CN. From the CN, RNC can get the SNAC

of each LA under the RNC, and the SNA authorized to each user. In the case of Iur

interface handover, SRNC can get the SNA of each DRNC cell through the Iur interface.

The RNC retains the SNAC of each user and configures the adjacent cell list of

intra-frequency 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 ZWF21-30-116 Operator Specific Function Control

Benefits

Operators of the shared RAN can purchase optional features separately and can

configure some key features operation parameter separately.

Description

Most optional features can be switched on/off based on PLMN ID. Also dozens of

operating parameters related to HSPA, MBMS, Handover and etc. can be configured

based on PLMN ID to realize the differentiated service strategy for operators using the

shared equipment. This feature is realized through license control.

ZTE RAN equipment supports many optional features which could be purchased and

activated based on network deployment strategy. Those features could be categorized

into three groups, each with different management methods in network sharing scenario.

− RNC Level functions applied to single subscriber

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.

− Cell Level functions applied to all subscribers in each cell

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.

− Other functions applied to a physical equipment

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 ZWF21-30-117 Operator QoS Priority

Benefits

QoS priority can be configured based on PLMN so that each operator can have individual

QoS strategy.

Description

PLMN based QoS priority configuration is introduced. And the QoS priority will be

implemented in the RRM algorithm including access control, congestion control and

overload control. The QoS priority also will be effective in HSPA packet scheduling and

transmission resource allocation. Therefore, more system resource will be able to be

allocated to subscribers and services of operator with priority. For each operator, QoS

priority of subscribers and services still can be defined separately as descript in the

feature of “ZWF21-05-003 Differentiated Service”.

Introduced Version

U11.1

Enhanced Function





No

2.8.6 ZWF21-30-118 Operator Specific Iub/Iur Transmission

Benefits

Operators of the shared RAN can flexibly deploy transmission network.

Description

The feature supports transmission reservation for different operators to ensure their

usage.

For Iu and Iur interface, transmission network can be deployed separately to different

operators and signaling flow and media data flow can be handled separately. Multiple

signaling points and IP addresses are supported by ZTE RNC, which could be used to

connect with different UMTS nodes, e.g. RNCs, MSCs and SGSNs, in different

transmission networks belong to different operates.

For Iur and Iub interface, transport links between shared RNCs or Node Bs also can be

divided into logical transport paths, which could be occupied by different operators for

separation and reservation of transmission resource. Logical transport paths can be

mapped to both logical and physical transport links.

Figure 2-15 Four operators shared Iub interface

RNC Node B

ANI+Path+PLMN1

ANI+Path1+PLMN2

ANI+Path1+PLMN3

ANI+Path1+PLMN4

ANI+Path+PLMN1

ANI+Path1+PLMN2

PathGroup

ANI+Path1+PLMN3

ANI+Path1+PLMN4

ANI+Path+PLMN_MIX ANI+Path+PLMN_MIX

Transmission resource of logical transport paths among different operators can be

completely reserved to ensure usage of each operator or dynamically shared to improve

transmission efficiency, or combination of partitioning and sharing. For shared





transmission resource, QoS differentiation can be implemented as the feature of

“ZWF21-30-117 Operator QoS Priority”.

Introduced Version

U11.1

Enhanced Function

No

2.8.7 ZWF21-30-119 Operator Specific RNC Resource

Benefits

Capacity can be logically separated in shared RNC equipment and purchased by

operators who share the RAN.

Description

Processing resource can be logically separated in ZTE RNC, which means RNC capacity

of CS traffic volume and PS throughputs can be separated and reserved to different

operators.

Introduced Version

U11.1

Enhanced Function

No

2.8.8 ZWF21-30-120 Operator Specific FM/PM/CM

Benefits

This feature provides the cell-level FM (Fault Management)/PM (Performance

Management)/CM (Configuration Management) for specific operator

Description





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 network’s 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 ZWF21-30-121 Operator Specific CE Resource

Benefits





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. ZTE’s

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 doesn’t 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 ZWF21-30-122 Extended GSM Neighboring Cells

Benefits

Configuration of more number of GSM neighboring cells is possible in RAN sharing

scenario for better supporting of inter- RAT mobility.

Description

Operators who share a 3G radio network usually have their own GSM network as well.

So comparing with UMTS neighboring cell, including intra-frequency and inter-frequency,

more number of GSM neighboring cells of different operators could exist. ZTE RNC

supports configuration of up to 96 GSM neighboring cells for better supporting of inter-

RAT mobility from shared UTRAN network to different operators’ GSM network.

Information of maximum 32 inter-RAT neighboring cells can be sent to UE according to

3GPP protocols. ZTE RNC can filter no more than 32 inter-RAT neighboring cells for UE

mobility function based on PLMN and neighbor cell priority. In the UE idle state, only

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 ZWF21-30-200 Multi PLMN Support

Benefits

This feature supports the configuration of multiple PLMNs to a UTRAN, which is used in

the following scenarios:

− If an operator owns several PLMNs, by using this feature he can deploy

different cells with different PLMNs at the airports, piers, coach terminals and

tourist spots where many inter-operator roaming users enter, hence the

probability of the network to be selected by the roaming users will get higher,

which means to attract more roaming users to reside in the network and to

increase the operators’ revenue.

− If a UTRAN is shared by different operators, different PLMNs can be used to

distinguish from different operators.

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 RAN Sharing Enhanced Features

2.9.1 ZWF21-30-103 RAN Sharing with Shared Carrier

Benefits

This feature provides the possibility for multi-operator to share the same 5MHz UMTS

carrier to build a shared UTRAN. It is useful when the UMTS frequency license is not

enough or different operators want to pool their frequency license to increase spectrum

efficiency.

Description

ZTE RAN equipment supports the broadcasting of multi-PLMN IDs in one cell. UEs with

3GPP R6 capability will be able to read system information of the shared carrier cell to

choose a right PLMN to register.

In scenario of RAN sharing with shared carrier, ZTE RNC supports bellowing methods to

route a UE signaling and service access to its right CN nodes.

− 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 UEs without 3GPP R6 RAN sharing capability, PLMN ID cannot be

indicated by UEs themselves. ZTE RNC choose CN nodes from different

operators based on following criteria:

If UE is identified by TMSI with specific NRI, ZTE RNC will route this UE’s

connection to one CN node with the same NRI.

If UE is identified by TMSI with unspecific NRI, ZTE RNC will try to use





re-routing function defined in 3GPP R6 which also needs support of CN nodes,

randomly choosing a CN node to establish this UE’s connection and waiting

for CN’s response. If the chosen CN node doesn’t authorize access of the

subscriber, CN will answer a NACK message to RNC, and RNC will continue

trying other CN nodes until the right node gives an ACK response.

If UE is identified by IMSI, or CN nodes don’t support re-routing function, ZTE

RNC will select a CN node based on the configuration of relation of IMSI

segment and operators.

− 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 operator’s

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 subscriber’s 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 operator’s 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 ZWF21-40-005 Multi-RRU for One Cell

Benefits

This feature is used in areas which have special requirements on coverage. It combines

multiple RRUs into one cell which replaces networking of multiple cells so as to reduce

the interference among cells, avoid the handover caused by moving among cells and

decrease call drop rate of the network.

Description

Multi-RRU for one cell means the signal of multi-RRU is for one cell logically, i.e. it is one

cell in the point of view of the RNC. In the downlink, every RRU that constitutes a logical

cell has common cell primary scrambling code, common pilot signal, synchronous signal

and other common channel signals. And base band unit will send same data to multi

RRUs with the same logical cell. In the uplink, uplink IQ data of multi RRUs will be input

and processed in the same base band unit.

In the coverage of a highway and a high speed railway, multi-RRU for one cell can be

adopted, and when user hands over from one RRU coverage area to another, it is not

necessary to report complicated measurement result, establish radio link or transmit

deleting command between the UE and the Node B or between the UE and the RNC.

Only multi-path process of base band module is needed to reduce call drop rate. In a

gym, shopping mall, the underground garage and the dense urban area, there are a lot of

overlapped areas among cells. In the case of these complicated radio environments,

multi-RRU for one cell can be adopted to reduce interference among cells, handover

times and call drop rate.

Introduced Version

U9.1&Before





Enhanced Function

No

2.10.2 ZWF21-40-006 Dynamic Power Track

Benefits

This feature is used to improve power amplifier (PA) efficiency, reduce OPEX of base

station and enhance equipment stability.

Description

The efficiency of PA is usually evaluated on the condition when output power is close to

the maximum value. However, the load of base station varies greatly with time. For

example, in the rush hours of daytime, transmitting power of base station is close to the

maximum to meet the traffic of telecommunication, and the efficiency of PA is the highest.

Late at night, the traffic will drop close to zero so the efficiency of PA is low. For

improving PA efficiency on the condition of low traffic in order to reduce the total power

consumption of base station, ZTE Node B equipment supports D-PT (Dynamic Power

Track) technology:

− 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





Figure 2-16 PA Efficiency with D-PT Technology

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 ZWF21-40-008 Multi-Carrier Dynamic Power Sharing

Benefits

This function, which is applicable to the situation of uneven load and fast change

between each carrier in multi-carrier instance, can increases utilization of power amplifier

and increase downlink capacity.

Description

The principle of multi-carrier dynamic power sharing is described as follows. In

dual-carrier WCDMA system, the cell serving R99 has some remaining carrier power

which will be applied to HSDPA scheduling in another carrier. In this instance, the cell

5 10 15 20 25 30 35 40 45 50 555

10

15

20

25

30

35

output power(W )

PA

effi

cien

cy(%

)

P A effic iency & output power

fixed voltage P A effic iencyadjus ted voltage P A effic ienc y





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:

− Keep identical with dual-carrier power configuration algorithm, namely the

scheduler reports -1,0,1 respectively and the super scheduler distributes the

power according to the report.

− 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 ZWF21-40-020 Extended Cell Range to 80Km

Benefits

This feature can be used for several specific scenes, such as ocean, desert, meadow

and plain. Traffic is low because of sparse population in this area. Expanding coverage of

single cell can reduce the number of base stations deployed in wide area and the

investment on Node B.

Description

In and before the R6 of 3GPP protocol, the value range of propagation delay field is

0~765 chips (corresponding to transmission path of 60Km). This value determines the

searching scope of uplink multi-path time delay signal in Node B. So in and before R6

UMTS, only coverage radius which is no more than 60Km is supported. However, some

scenarios may need larger coverage, such as ocean, desert, meadow and plain.

ZTE RAN equipment adopts extended definition of the propagation delay (maximum

3069 chips) in 3GPP R7 protocol. It breaks through the coverage limit of 60Km, reaching

about 80Km. And the following coverage Enhanced Function techniques are adopted by

ZTE to meet the requirement on radio propagation quality for services.

1. Optimize path loss

i. Adjust the mounting height of antennae to increase the horizon range

ii. Lower the carrier band to reduce path loss

2. Improve the sensitivity

i. High-gain directional antennae

ii. Tower mounted amplifiers

iii. Reduce the noise coefficient of the receivers





iv. Adopt BBU+RRU distributed base station to reduce antenna feed

3. Improve the processing gain

i. Adopt low-speed AMR code rate

ii. Reduce the rate of data service

4. Improve the baseband processing capability

i. Enhance the cell search capability

5. Reduce the fading margin

i. Multi-antenna receiving diversity

ii. Transmit diversity

iii. Adopt high power amplifier or amplifier overlap technique to increase

transmitting power

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 ZWF21-40-021 Four Antennas Reception

Benefits





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.

Figure 2-17 Mechanism of Four-Antenna Receiving Diversity

RF process

RF process

Symbol level

process

RF Unit1 (RRU） Base Band Unit（BBU）

UE

Reflector

Antenna 1

Antenna 4

MRC

RF processAntenna 2

RF processAntenna 3

Fingerdemodulation

Multi-path detection and assignation

RF Unit 2(RRU）

Four-antenna receiving diversity is implemented through two RF units. Each RF unit

inputs two channels of antenna signals, which are processed by the two independent RF

channels of the RF units and then are sent to the BBU of the Node B, and then performs

the multi-path detection, Rake receiving, Maximal Ratio Combining and subsequent

processing.

Introduced Version

U9.1&Before

Enhanced Function

No





2.10.6 ZWF21-40-022 Transmit Diversity

Benefits

This feature is to increase the effective coverage of the system and improve the terminal

receiving capability.

Description

Transmit diversity is to transmit a signal through multiple antennae. In a fading

environment, transmit diversity enables a terminal to receive multi-path signals and

improve the signal quality, thus improving the performance of the wireless

communication system effectively. ZTE RAN equipment supports open-loop transmit

diversity, including Space-Time Transmit Diversity (STTD) and Time Switched Transmit

Diversity (TSTD), and closed-loop transmit diversity (Mode 1).

Table 2-1 Types of Transmit Diversity and Physical Channel Supported by ZTE

Physical Channel Type

Open-loop Transmit Diversity

Closed-loop Transmit Diversity

TSTD STTD Mode 1

P-CCPCH – X –

SCH X – –

S-CCPCH – X –

DPCH – X X

F-DPCH – X –

PICH – X –

MICH – X –

HS-PDSCH – X X

HS-SCCH – X –

E-AGCH – X –

E-RGCH – X –

E-HICH – X –

AICH – X –





Two-path transmit channel is needed in the case of configuration of transmit diversity in

Node B, and the logical connection is shown in the 错误！未找到引用源。.

Figure 2-18 Logical Connection of Transmit Diversity

R

DF

RTR+PA

RRU/RSU

T R

DF

RTR+PA

RRU/RSU

ANT2

R&T

ANT1

R&T

BBU

T

In open-loop transmit diversity mode, the terminal doesn’t 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 ZWF21-40-023 AISG Interface

Benefits

This function supports adjusting the down tilt angle through the remote or local control

software. Compared with the traditional antenna system, it has many advantages:





− Adjust the down tilt angle of the electrical tilt antenna without switching off the

power. Detect the down tilt angle real time.

− High-accuracy tilt avoiding frequency interference and Tx interference.

− 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.

Figure 2-19 Electrical Tilt Antenna System

O&M

Downtilt anglemº

Downtilt angle nº

Software of Electrical Tilt

Antenna

Node B

Electrical Tilt Antenna

Eelectrical tilt antenna control unit integrated in 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:

− Equipped with standard AISG (Antenna Interface Standards Group) interfaces

− Realize automatic angle adjustment of local antennae

− Control automatic angle adjustment of remote antennae remotely

− One RRU can control a maximum of three electrical tilt antennae to control the

motor

− Perform configuration and network management through LMT or OMC

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.


l Benefits

This feature can satisfy the requirement for 120Km coverage.

Description

The ZTE RAN product adopts Enhanced technology of high-sensitivity receiving,

transmit diversity, and 4-channel-Rx antenna (refer to ZWF21-40-020 80km Remote

Coverage), and improves the baseband hardware and algorithms, using the cell





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 ZWF21-40-026 High Speed Mobility Access

Benefits

This feature enables the system to provide multi-media UMTS service for users moving

at a speed of 450km per hour, for example, a user in the super highway and high speed

railway.

Description

For users moving at a high speed, the Doppler frequency offset is usually very large. The

base station must correctly estimate the frequency difference between the receiver and

the transmitter, and correct the frequency offset. Meanwhile, the base station receiver

must quickly respond to the fast frequency offset variation and compensate the variation.

The baseband frequency offset compensation algorithm of the ZTE base station can

effectively estimate and compensate the frequency offset during the random access

process and save preamble detection resources and be flexibly applied to the settings of

coherent integration parameters. The baseband frequency offset compensation

algorithm can estimate and compensate the frequency offset of a dedicated channel and

quickly follow the frequency offset variation.

Introduced Version

U9.1&Before





Enhanced Function

No

2.10.10 ZWF21-41-001 Uplink Interference Cancellation (MUD)

Benefits

This feature supports to reduce the interference and increase SNIR (Ratio of signal &

noise to interference power).

Description

The user in WCDMA uplink is identified by the scrambling code. Affected by the channel

fading, etc, the orthogonality between different users and between different code

channels for the same user will be broken differently to cause the existence of the mutual

interference. There are more uplink users, the interference to a certain target user is

bigger.

The interference cancellation technique will cancel the interference as possible between

different users and between different code channels for the same user with the purpose

of decreasing the interference by the target user and decreasing SNIR in order to

improve the uplink system capacity.

The feature “Control/Dedicated Channel Parallel Interference Cancellation” supported in

ZTE RAN system will implement the interference cancellation of

DPCCH/HS-DPCCH/E-DPCCH/E-DPDCH to maximize the interference cancellation

gain.

DPCCH interference cancellation supports all users’ DPCCH interference cancellation

including DPCCH pilot field, and non-pilot field which provides erasing technique to

effectively avoid the negative gain. After that, the antenna data will proceed with the data

channel demodulation which would benefit from DPCCH interference cancellation.

HS-DPCCH interference cancellation supports all users’ HS-DPCCH interference

cancellation including CQI field, and ACK/NACK field which provides erasing technique

to effectively avoid the negative gain. After that, the antenna data will proceed with the





data channel demodulation which would benefit from HS-DPCCH interference

cancellation.

E-DPCCH/E-DPDCH interference cancellation primarily contains:

− Supporting to proceed with E-DPCCH/E-DPDCH interference cancellation

including 2ms/10ms E-DPCCH/E-DPDCH for the users who have finished

right E-DPDCH decoding. The I.C. gain can be stably and reliably obtained by

the interference cancellation system.

− 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.

− Supporting the demodulation of the previous transmission in the case of 2ms

E-DPDCH re-transmission. The re-demodulation to the previous transmission

which can wait for a long time can obtain the obvious gain.

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 ZWF21-41-002 Advanced Receiver A-Rake

Benefits

This feature is applied in HSUPA 16QAM modulation to fulfill the receive performance

requirements especially for the fading channel performance that cannot be achieved by

legacy rake receiver.

Description

When 16QAM modulation introduced in 3GPP R7 to raise HSUPA air-interface data rate

is applied in HSUPA, the legacy RAKE receiver which is dissatisfied with the receiving

requirement can be used to demodulate in AWGN and cannot reach the peak rate of

16QAM due to the decrease in demodulation performance in the fading channel.

Therefore, Node B shall use the A-RAKE technique of advanced receiver which can

increase the link performance in the case of high transmission rate for single user.

Essentially, A-RAKE receiver structure which is the same as RAKE receiver is shown in

below.

Figure 2-20 A-RAKE receiver structure

Channel delay Spreading waveform correlator



Finger 1

Finger 2

Finger N

( )tr z

*1w

*2w

*Nw

1d

2d

Nd

( )1dy

( )2dy

( )Ndy

Finger Process





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


Benefits

This feature can satisfy the requirement for 240Km coverage.

Description

The ZTE RAN product adopts Enhanced technology of high-sensitivity receiving,

transmit diversity, and 4-channel-Rx antenna (refer to ZWF21-40-020 80km Remote

Coverage), and improves the baseband hardware and algorithms, using the cell

preamble processing technology. The base station can cover a distance up to 240km.

When configured with remote coverage, only one carrier sector is allowed in one base

band hardware board,

To provide 200km remote coverage, the height of antenna should be 2095m (2.1GHz

frequency band) or 2060m (900MHz frequency band).

Introduced Version

UR11.1





Enhanced Function

No

2.10.13 ZWF21-42-001 Flexible Frequency Configuration

Benefits

In GU frequency refarming scene, operator can get more GSM frequency resource in

whole network.

Description

ZTE RAN product support flexible frequency separation range configuration from 2MHz

to 2.6MHz between GSM and UMTS system with algorithm optimization.

By means of smaller frequency separation configuration, operator can get more

frequency resource to deploy GSM whole network and improve frequency utilization, and

get more negative impacts on G/U network performance and KPI, especially to UMTS

uplink capacity in 2.2M frequency separation configuration even with carefully network

planning and optimization.

Introduced Version

U9.3 supports frequency separation range configuration from 2.2MHz to 2.6MHz.

Enhanced Function

In order to take full advantage of the bandwidth spectrum 6 MHz, UMTS carrier

bandwidth uses 3.8MHz and GU center frequency separation is 2MHz. Only

R8860E/RSU60E can support 2MHz separation configuration in UR11.1.





3 Transport Network Functionality

3.1 ZWF22-02-A ATM Package

3.1.1 ZWF22-02-001 ATM Transmission stack

Benefits

This feature supports using ATM as transmission protocol in UTRAN as well as between

UTRAN and CN.

Description

The Asynchronous Transfer Mode (ATM) is a cell-oriented asynchronous transfer mode.

The ATM protocol combines the benefits of both circuit switching and packet switching.

On one hand, it features Simple Handling of circuit switching, supports real-time

transparent transmission of service and data without complicated data handling and

adopts end-to-end communication protocol; on the other hand, it is characteristic of

packet switching, for example, it supports variable bit rate service, and adopts statistical

time division multiplex for services transmitted on links. ATM adaptation layer (AAL)

provides different QoS services for upper service so as to use ATM as transmission

bearer for different services. Types of AAL services are shown in Table 3-1.

Table 3-1 Types of AAL Services

Service Types Type A Type B Type C Type D

Bit Rate Constant Variable

Connection Type Connection oriented Connectless

Types of AAL AAL 1 AAL 2 AAL 3 AAL 4

AAL 5

Examples of Services

Circuit simulation

Video Connection oriented data

Connectless 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.

− Constant Bit Rate (CBR)

It can provide constant rate traffic service (Type A), be most strict to the QoS

parameter link transmission delay, package loss and jitter. It is suitable for real

time services or those that need constant bandwidth.

− Variable Bit Rate (VBR)

VBR can be classified into two sub-groups: Realtime-VBR (RT-VBR) and

Non-Realtime VBR (NRT-VBR). The RT-VBR is primarily used to describe

realtime services with variable data stream and strict requirements, for

example, interactive compressed video (such as video conference). The

NRT-VBR is used where timing transmission is required, for example, e-mail,

which allows for certain extent of delay and change,

− Available Bit Rate (ABR)

ABR is designed for sporadic information transmission with given bandwidth

scope. The ABR is the only service type with which the network offers speed

response to senders. In the event of network congestion, senders are

requested to lower transmission rate. Suppose the senders observe these

requests, the cell loss rate can be very low in ABR-capable communication.

The acting ABRs can be regarded as mobile passengers waiting in a queue: If

there are vacant seats (space), they are assigned to these seats without delay;

otherwise, they have to wait (unless some minimum bandwidth is available).

− Unspecified Bit Rate (UBR)

It does not make any commitment or give response to the congestion. The

UBR is quite applicable to transmission of IP datagram. In the event of

congestion, UBR cells are discarded, but neither feedback nor request for

lowering transmission rate is transmitted to senders.

− Unspecified Bit Rate Plus (UBR+)





UBR+ is also called Guaranteed Frame Rate (GFR), an additional ATM

service type. The difference between UBR and UBR+ is that UBR+ can

provide minimum bandwidth guarantee, which is defined by parameter of

Minimum Cell Rate (MCR).

The concept of minimum bandwidth guarantee is from ABR, but UBR+ and

ABR are different because the guarantee of UBR+ is performed simply by

tagging cells which exceed the minimum bandwidth. When these cells with tag

pass through the nodes of the network, they might be discarded if some nodes

are congested, or they might be all transmitted. So UBR+ is perfect to transmit

burst packets data with minimum bandwidth guarantee. In addition, UBR+ is

featured with Partial/Early Packet Discard (PPD/EPD) mechanism, and it is

capable of discarding the whole data frame when some cell in the frame is

damaged to increase the transmission efficiency of packet data. UBR+ is used

in AAL5, and can be used to bear traffic data on Iu PS or O&M data on Iub.

ZTE RAN equipment supports set ATM link as CBR, rt-VBR, nrt-VBR, ABR, UBR or

UBR+ type to provide different QoS to upper layer. The Table 3-2 lists the features of

various ATM services

Table 3-2 Features of Various ATM Services

Feature CBR rt-VBR nrt-VBR ABR UBR UBR+

Bandwidth guarantee Yes Yes Yes Optional No Yes

Applicable to realtime communication

Yes Yes No No No No

Applicable to non-realtime communication

No No Yes Yes Yes Yes

Any feedback on congestion

No No No Yes No No

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, 错误！未找到引用

源。 , 错误！未找到引用源。, 错误！未找到引用源。.

Figure 3-1 ATM Protocol Stack of IuCS Interface

Physical Layer

ATM

AAL5

SSCOP

SSCF-NNI

MTP3B

RANAP

ATM

AAL5

SSCOP

SSCF-NNI

MTP3B

SCCP Q.2150.1

Q.2630.1/2

ATM

AAL2

Iu UP

Transport Network User Plane

Transport Network Control Plane


Control Plane User Plane

Radio Network Layer

Radio Network Layer





Figure 3-2 ATM Protocol Stack of IuPS Interface

Physical Layer

ATM

AAL5

SSCOP

SSCF-NNI

MTP3B

RANAP

SCCP

ATM

AAL5

Iu UP





Radio Network Layer

Radio Network Layer

IP

UDP

GTP-U





Figure 3-3 ATM Protocol Stack of Iur Interface

Physical Layer

ATM

AAL5

SSCOP

SSCF-NNI

MTP3B

RNSAP

ATM

AAL5

SSCOP

SSCF-NNI

MTP3B

SCCP Q.2150.1

Q.2630 .1/2

ATM

AAL2

Iur FP





Radio Network Layer

Radio Network Layer





Figure 3-4 ATM Protocol Stack of Iub Interface

Physical Layer

ATM

AAL5

SSCOP

SSCF-UNI

NBAP

ATM

AAL5

SSCOP

SSCF-UNI

Q.2150.2

Q.2630 .1/2

ATM

AAL2

Iub FP





Radio Network Layer

Radio Network 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





In U9.2, ZTE supports UBR+

3.1.2 ZWF22-02-002 PVC Cross Connection

Benefits

This feature supports part of ATM switching capability, achieving cross connection of

RNC and Node B with other network equipments by using ATM protocol, and supports

chain-type topology network.

Description

In scenarios over an ATM network, RNC and Node B need to terminate and handle lub,

lur and lu cell stream carried on ATM cells as the termination node in the ATM network.

Apart from that, ZTE RNC and Node B equipment can also work as an ATM switch to

perform VC-/VP-granularity switching and forwarding of accessed cell stream and

implement PVC cross connection.

Exchange relationship of different VC and VP link is configured statically by OMC.

Introduced Version

U9.1&Before

Enhanced Function

No

3.1.3 ZWF22-02-003 Dynamic AAL2 Connections

Benefits

This feature supports dynamically establishing and releasing AAL2 connection and

allocating bandwidth resource of transmission link in Iub, Iur and Iu CS interface,

according to the process of service calling with the transmission of ATM.

Description





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 ZWF22-02-004 Permanent AAL5 Connections

Benefits

This feature supports statically configuring AAL5 connection in Iub, Iur and Iu interface

with the transmission of ATM, and is used for bearing control plane signal, operation and

maintenance data of Node B and transmission of Iu PS service data.

Description

3GPP defines AAL5 as bearer mode of Iu PS data and application layer protocol of all

ground interfaces with the transmission of ATM. Every AAL5 link is defined by unique

(VPI, VCI) group, whose link parameter is configured statically in background OMC.

ZTE RAN equipment supports configuring AAL5 bearing SAAL signal link in UNI (used

for Iub interface) and NNI (used for Iu and Iur interface) mode to support protocol

message transmission of NBAP, RNSAP, RANAP and ALCAP application layer. ZTE

RAN equipment supports adopting IPOA mode to configure AAL5 bearing IP protocol as

transmission channel of IuPS user data and Iub interface for transmitting operation and

maintenance data of Node B.

According to the difference of specific scenarios, different AAL5 connection can

configure different ATM service types flexibly to guarantee the reliable transmission of

signal link. CBR is suggested to be selected in ATM service types of AAL5 signal link.

For adjusting to data service featured with sudden burst, VBR or UBR is suggested to be

selected in ATM service types of AAL5 data link.

Introduced Version

U9.1&Before

Enhanced Function

No

3.1.5 ZWF22-02-005 AAL2 Quality of Service Separation

Benefits





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.

Figure 3-5 AAL2 QoS Differentiation

Tolerant class

Conversational class(C)

Streaming class(S)

Interactive class(I)

Background class(B)

ITU-T Qos classes

( Path Type)

UMTS Qos classes

Stringent class

CBR or rt-VBR UBR or nrt-VBR

ATM forum service categroies

PVC typeReal-time PVC

PRI:

C-highS-low

Unreal-time PVCPRI:

I-highB-low

Common PVCPRI:

C&S-highI&B-low

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 ZWF22-02-006 ATM Link Redundancy

Benefits

This feature supports redundancy protection for ATM transmission link to avoid service

interruption caused by the failure of some physical link to enhance the reliability and

stability of system.

Description

Redundancy protection mechanism of ATM link in ZTE RAN equipment can be used in

physical link layer and logical link layer.

In physical link layer redundancy protection mechanism of ATM link includes:

− Support APS protection (compliant to ITU-T G.841 protocol) based on

SDH/SONET technique for optical access; redundancy protection 1+1 mode or

redundancy protection 1:1 mode can be adopted; when main link has some

problem, the time of handover to spare link is less than 50ms.

− Support physical link protection of IMAB+DTB for E1/T1 access. When

multiple DTBs are used, multiple links in IMA group can adopt the principle of

load sharing to implement cross-board configuration. When some DTB

interface board has problem or some relay links are cut off, IMA group still can

be used with merely bandwidth reduced.

In logical link layer redundancy protection mechanism of ATM link includes:

− 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.

− Load sharing mechanism of multiple next hops as in IP routing technique for

AAL5 link (PS service) bearing user plane data to achieve load sharing and

redundancy protection.





− Protection mechanism is guaranteed by SS7 for the signal link of Iu/Iur

interface. If some links have problem, SS7 will implement routing reselection.

− 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 B’s operation and

maintenance channel in Iub interface.

ZWF21-20-010 Equipment Redundancy supported by ZTE RAN equipment also can

provide redundancy protection for ATM interface board.

Introduced Version

U9.1&Before

Enhanced Function

No

3.1.7 ZWF22-02-008 Inverse Multiplexing over ATM, IMA

Benefits

This feature adopts Inverse Multiplexing technologies to bind multiple E1 or T1 into one

link so as to make the ATM links support higher bandwidth and meet the requirement on

high-speed services. Meanwhile, redundancy protection can be available in multiple

low-speed links to enhance the reliability of transmission.

Description

Inverse Multiplexing is a technology that reversely multiplexes one ATM connection

based on cells into several physical connections of transmission and multiplexes cells

transmitted on these connections into a single cell stream. Through binding multiple

low-speed links, the bandwidth for transmission of ATM can be expanded. When the rate

of accessing network for user or the rate between two ATM elements is within two

traditional multiplexing levels (for instance, between E1 and E3), IMA can multiplex

several low-speed connections into a logical high-speed connection.





IMA function supported by ZTE RAN equipment abides by AF-PHY-0086.001 criterion of

ATM forum, and is backward compatible with all features in IMA protocol criterion 1.0.

Meanwhile, ZTE RAN equipment supports TC (UNI) bearer. That means multi-path

binding and multiplexing is not implemented and ATM bearer is based on single relay

link.

When there are several low-speed links, OMC can configure whether to use the IMA and

which low-speed link to be combined to use the IMA. When several low-speed links are

combined to use the IMA, if part of these links have problem, other links still can

guarantee that the IMA group provides service for upper layer, though the transmission

bandwidth of the whole IMA group will be affected. If RNC and Node Bs are connected

directly by E1/T1, RNC could detect broken E1/T1 links and automatically adjust

available bandwidth of an IMA group for admission control. If E1/T1 links are converged

by additional transmission equipment in front of RNC, which means IMA groups are

ended before reaching RNC, the state of E1/T1 links could be monitored by Node B and

available bandwidth of an IMA group could be sent to RNC for admission control.

Introduced Version

U9.1&Before

Enhanced Function

No

3.2 ZWF22-03-A IP UTRAN PACKAGE

3.2.1 ZWF22-03-001 IP Transmission Stack

Benefits

Instead of ATM, IP is used as the transmission protocol inside the UTRAN or between

the UTRAN and the CN, to meet the rapid increasing requirements on traffic because of

the introduction of HSPA and rapid development of data service.

Description





The IP can be deployed as the replacement of ATM transmission protocol in UTRAN

network in the 3GPP R5 standard. To ensure the reliable transmission of No. 7 signaling

in IP network with the QoS guarantee, 3GPP recommends that the transport layer of

radio network control plane adopts Sigtran protocol cluster. The Sigtran protocol cluster

referred in IP UTRAN includes the Stream Control Transport Protocol (SCTP) and MTP3

User Adaptation layer (M3UA). In the transport layer of radio network user plane, for

Iu-PS interface data transport adopts GTP-U protocol over UDP, for Iu-CS interface data

transport adopts RTP/RTCP protocol, while only SR of RTCP is used to cooperate with

peering CN for the purpose of RTP transmission monitoring, for Iub and Iur interface data

transport adopts UDP protocol directly.

ZTE RAN equipment supports the full IP protocol stack on Iub, Iur, IuCS and IuPS

interfaces. IP transmission can be deployed independently on each kind of interface.

For planning of IP address of radio layer, ZTE RNC usually use different IP for control

plane and use plane. While in control plane or user plane, the same IP could be used for

Iu, Iur and Iub interface to save IP address resource if necessary, or different IP could be

used for different interface to adapt transmission strategy, which is the insulation of

convergence layer and access layer or different domain. Either same or different IP could

be used in ZTE Node B for control plane and use plane of Iub interface.

Introduced Version

U9.1&Before

Enhanced Function

In U9.3, ZTE RNC support to set different IP for Iu, Iur and Iub interfaces in user plane.

In U9.3, ZTE RNC supports MTU up to 1620, including MAC and PPP.

3.2.2 ZWF22-03-002 Static Route

Benefits

This feature supports configuring IP route information of the UTRAN by OMC.

Description





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:

− Direct route generated automatically by interface IP address

If the IP address and mask are configured for IP interface board of RNC

equipment, the system will generate automatically a direct route for the

corresponding sub-net of the interface IP.

− Static route based on next-hop IP address

The static route of next-hop IP address can be configured manually by OMCR.

Each static route supports several next hops.

− Static route based on IP UNNUMBER

The configuration of the static route can be configured manually by OMCR

based on IP UNNUMBER technology which does not require the network

interface to bind the IP address, but use an existing network interface IP to

generate the route. This configuration of static route is applicable only to the

P2P links. Its main advantage is to save IP address resources. Therefore, it is

very applicable for IP over ATM and IP over E1/T1 of lub interface.

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 ZWF22-03-005 IP Traffic Shaping

l 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.


U9.3

l Enhanced Function

None





3.2.5 ZWF22-03-009 IEEE 802.1ag/ITU-T Y.1731

Benefits

This feature provides Ethernet OAM function to facilitate the operations management

and fault locating. This feature is used to identify at the Ethernet layer Ethernet virtual link

(EVC, Ethernet Virtual Connection) connectivity, effectively detect, identify. It enables

users to sign in accordance with the Statute of the service level (SLA) to provide a

completely independent and service layer OAM mechanism.

Description

Ethernet is mainly used for LAN, so its OAM capability is weak, and only has network

element management function; it is difficult to support the Public Telecommunications

Network Management. This feature provides the OAM functionality based on IEEE

802.1ag/ ITU-T Y.1731. In IP UTRAN, when networking is based on Ethernet technology,

this feature is used to detect connectivity between network nodes and to locate the

fault. Under normal circumstances RNC / NodeB are all MEP(Maintenance End Point)

equipment.

This feature provides the following functions based on Ethernet.

− Ethernet connectivity check.

This is an active OAM functions, it can be used in a MEG(Maintenance Entity Group)

in detecting any connectivity between a pair of MEP, can be used to detect wrong

connection between two MEG, and can also be used to detect error connection of a

MEP in a MEG, and other defects. Connectivity check message can be applied to

the fault management, performance monitoring or protection switching.

− Ethernet loopback.

It is used to detect the connectivity between a MEP and a MIP(Maintenance

Intermediate Point), or between a MEP and another MEP or many MEPs, similar to

the PING function.

− Ethernet link trace.

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 indicate

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.

− ITU-T Y.1731 also defines performance management,

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 ZWF22-03-011 VLAN for Node B

Benefits

This feature supports dividing Node Bs and other equipments in the same physical

network into different logic network (Virtual Local Area Network, VLAN). In this way, the

packet is restricted to save transmission bandwidth, and the system security is

enhanced.

Description

ZTE Node B supports VLAN function which complies with IEEE 802.1Q standards. The

common Ethernet frame can become the Ethernet frame supporting 802.1Q by adding 4

bytes, which is as follows:





Figure 3-6 VLAN Tag

CRCDA SA Type Data

Standard Ethernet Frame

Priority(4bits)

TCITCI

DA SA Type Datatag

TPID(0x8100)

CFI(1bit)

VLAN ID(12bits)

TCITCI

Ethernet Frame with IEEE802.1Q Tag

CRC

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.

− Canonical Format Indicator (CFI):1bit which partitions the frame structure

when the bus Ethernet exchanges data with FDDI or token ring network.

− 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 ZWF22-03-012 VLAN for RNC

Benefits

This feature supports dividing RNCs and other equipments in the same physical network

into different logic network (Virtual Local Area Network, VLAN). In this way, the packets

are restricted to save transmission bandwidth, and the system security is enhanced.

Description

The ZTE RNC supports division of VLANs in compliance with the IEEE 802.1Q and

802.1P.

Each Ethernet interface of RNC can have multiple sub-interfaces, with each

sub-interface corresponding to a VLAN. When receiving a packet with VLAN tag, RNC

can identify the sub-interface to which the packet belongs according to the VLAN ID.

When sending a packet, it identifies the ID of the sub-interface of the peer end NE

through route query, marking the VLAN ID corresponding to the sub-interface, puts

packets in a transmission queue according to the COS in the header of the packet. The

packet with the highest priority will be transmitted first.

Introduced Version

U9.1&Before

Enhanced Function

No

3.2.8 ZWF22-03-014 IP Header Compression

Benefits

This feature can be used to reduce the consumption of IP headers and improve the

utilization ratio of transmission bandwidth.

Description





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 ZWF22-03-017 QoS based Route

Benefits

This feature supports setting different IP transmission paths for different services based

on service type. For different services, different QoS levels are provided, and the

transmission cost is saved.

Description

For all-IP networking, taking the transmission network cost as well as provided QoS level

into account, the operator can set different transmission paths for different services. ZTE

supports three QoS-based IP route transmission scenarios:

− 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 ZWF22-03-018 IP Fast Reroute

Benefits

This feature provides the functions including the rapid detection and the protection of IP

route, decreasing the influence on real-time service (such as the voice service) due to IP

transmission failure and handover.

Description

The IP network does not have intermittent fault recovery function for the sub-second level,

while the traditional route structure has limited fault detection capability on the real-time

applications (such as the voice service). The requirements on fast fault detection and

correction function are getting stricter due to the application of the IP voice and other

real-time services. It is critical to prevent the route network from long-time interruption.

ZTE RAN equipment supports BFD (Bidirectional Forwarding Detection) technology,

which makes it possible to detect errors in forwarding path in a very short period and

trigger the switch to standby route or transmission channel by monitoring the availability

of transmission paths which correspond to each next-hop in the static route in real time.

So the troubleshooting time can be reduced to less than a second.

Introduced Version





U9.1&Before

Enhanced Function

Node B supports BFD based IP fast reroute in UR11.1 release.

3.2.12 ZWF22-03-021 Transmission SLA Monitoring

Benefits

This feature enables to diagnosis and test IP transmission network to get to know the

QoS indexes ,such as time delay, jittering, and response time.

Description

ZTE RNC supports the SLA detection function. By exchanging the ECHO and REPLY

packets of the SLA between base stations, ZTE RNC can detect the performance

indexes (time delay, jittering, packet loss rate, bandwidth, and throughput) of the IP

transmission channel in Iub, Iur and Iu interfaces. The SLA detection adopts a tunneling

technology. ZTE RNC can encapsulate the detection packets into the ICMP or UDP

packets (depending on the attributes of the device in the commercial network).

− 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 ZWF22-03-023 IEEE 802.3ah Support

Benefits

The transmission equipments are usually traditional Ethernet switch or PTN devices.

OAM functions defined in 802.3ah and supported by RNC can monitor the faults of

Ethernet devices quickly.

Description

This feature supports the OAM function defined in 802.3ah. The OAM information bears

by OAMPUD which includes the control and status maintenance information that can be

used to measure or monitor the activated OAM links. The OAMPDU exists only in

pear-to-pear links and will not be forwarded by devices such as bridge and switch.

The functions are listed as follows.

− Discovery/Handshake

− Remote fault notification.

− Remote loopback.

− Link monitoring.

Introduced Version

U9.2





Enhanced Function

No

3.2.14 ZWF22-03-030 IP Anti-DOS Attack

Benefits

IP attacks to the base station are shielded and prevented, it avoid excessive CPU load as

well as ensure system performance. It enhances the operator's network availability and

security.

Description

DOS, Denial of Service, could be a method to attack a computer or network so that it

cannot provide normal services. The most common DOS attack against a computer

network bandwidth and connectivity attacks.

ZTE Node B supports IP Anti-Dos Attack function, which keeps monitoring CPU load and

network access from potential Dos attacks. When CPU rate is too high and still huge of

network access requests, Node B will stop response new request of network include

ICMP and so on. Then it is prevent DOS attack from source.

Introduced Version

U9.3

Enhanced Function

No

3.3 Optional Transmission Interfaces

3.3.1 ZWF22-02-051 ATM Over E1

Benefits

This feature supports ATM over E1.





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 ZWF22-02-052 ATM over T1

Benefits

This feature supports ATM over T1.

Description

T1 physical interface complies with the 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 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.





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 ZWF22-02-054 ATM over Optical STM-1/OC-3

Benefits

This feature supports ATM over optical STM-1/OC-3.

Description

ZTE RAN provides STM-1 interface connected to SDH network and OC-3 (also called

STS-3) interface connected to SONET network. The actual mode of optical interface is

configured by OMM. Transmission complies with ITU-T G.957/G.958 standards.

Transmission media is single-mode fiber meeting ITU-T G.652/G.653 criterion, operating

wavelength is 1310nm, and transmission rate is 155.520Mbps.

Introduced Version

U9.1&Before

Enhanced Function

No

3.3.4 ZWF22-02-055 ATM over Channelized STM-1/OC-3

Benefits

This feature supports ATM over channelized STM-1/OC-3. Numerous EI/T1 interfaces

can be combined into one ATM connection to improve RNC interface integration.





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 ZWF22-02-056 ATM over Fractional E1

Benefits

This feature supports ATM over fractional E1. The spare timeslots can be used for other

purpose such as transmission of 2G so as to share transmission resource when 2G/3G

co-sited.

Description

Fractional E1 physical interface supported by ZTE RAN meets the definition in the

af-phy-0130.000. The transmission rate of each timeslot on E1 is 64Kbps. E1 timeslots

used to carry data can be further divided and used to carry data according to n × 64Kbps.





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 can’t 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 ZWF22-02-057 ATM over Fractional T1

Benefits

This feature supports ATM over fractional T1. The spare timeslots can be used for other

purpose such as the transmission of 2G so as to share transmission resource when

2G/3G co-sited.

Description

Fractional T1 physical interface supported by ZTE meets the definition in the

af-phy-0130.000. The transmission rate of each timeslot on T1 is 64Kbps. T1 timeslots

used to carry data can be further divided and used to carry data according to n × 64Kbps.

ZTE supports the carry of TC (UNI) link on n × 64K timeslot subset of one T1 trunk line so

that one T1 can be subdivided into several independent ATM transmission channels (TC

group). For ATM over Fractional T1, only the TC mode is used for each T1 to carry the

ATM transmission and the multiple Fractional T1 links can’t 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.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 don’t 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.

Figure 3-7 PPP/MLPPP Protocol Stack

IP

E1HDLC

PPPHDLC

PPPMLPPP/MCPPP

HDLCPPP

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 ZWF22-03-055 IP over Optical GE

Benefits

This feature supports IP over optical GE, providing higher transmission bandwidth and

farther transmission distance by optical fiber.

Description

Optical GE transmission supported by ZTE RAN equipment complies with IEEE 802.3z

standards. The transmission media include long-wave single-mode or multi-mode fiber

(meets 1000Base-LX criterion), short-wave multi-mode fiber (meets 1000Base-SX

criterion), the data rate can reach 1000Mbps.

ZTE RAN equipment supports GE mode, IEEE 802.3 standard Ethernet frame structure

and VLAN frame structure which meets IEEE802.1Q and 802.1P criterions.

Introduced Version

U9.1&Before

Enhanced Function

No

3.3.10 ZWF22-03-056 IP over Optical FE

Benefits

This feature supports IP over optical FE in Node B, providing higher transmission

bandwidth and farther transmission distance by optical fiber.





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 ZWF22-03-057 IP over Optical STM-1/OC-3

Benefits

This feature supports IP over optical STM-1/OC-3.

Description

ZTE RAN provides connections to the SDH network through the STM-1 interface and

provides connections to the SONET network through the OC-3 interface (also referred to

as STS-3 interface). The transmission line complies with the ITU-T G.957/G.958

standards. The transmission media is ITU-T G.652/G.653 single mode optical fiber; the

working wavelength is 1310nm; the transmission bit rate is 155.520Mbps.

By mapping the PPP packet into the payload of the SDH/SONET frame, it realizes IP

transmission over STM-1/OC-3 link or Packet over SONET/SDH (POS), which is

compliant to RFC1662 standard.

Introduced Version

U9.1&Before

Enhanced Function





No

3.3.12 ZWF22-03-060 IP over Optical STM-4/OC-12

Benefits

This feature realizes IP transmission over the STM-4/OC-12 link of an optical port.

Description

ZTE RNC provides connections to the SDH network through the STM-4 interface and

provides connections to the SONET network through the OC-12 interface (also referred

to as STS-12 interface). The transmission line complies with the ITU-T G.957/G.958. The

transmission medium is ITU-T G.652/G.653 single mode optical fiber; the working

wavelength is 1310nm; the transmission bit rate is 622Mbps.

By mapping the PPP packet into the payload of the SDH/SONET frame, the ZTE RNC

realizes IP transmission borne over the STM-4/OC-12 link or Packet over SONET/SDH

(POS), which is compliant to RFC1662 standard.

Introduced Version

U9.1&Before

Enhanced Function

No

3.3.13 ZWF22-03-061 IP over Channelized STM-1/OC-3

Benefits

This feature realizes IP transmission over the channelized STM-1/OC-3 link. It can save

a large number of E1/T1 electrical interfaces and improve the integration of the RNC

interface.

Description





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 ZWF22-03-062 IP over Fractional E1

Benefits

This feature realizes the IP transmission over some timeslots of an E1 link. The spare

timeslots can be used for other purposes, for example, the spare timeslots can be used

for 2G network transmissions so as to share transmission resources when 2G and 3G

co-sited.

Description

The Fractional E1 port of ZTE RAN satisfies the definition of the af-phy-0130.000. Each

timeslot of the E1 link is equivalent to the 64Kbps transmission capability. The 30 (31)

timeslots in each E1 link can be further divided to realize the n*64Kbps data

transmission.





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 ZWF22-03-063 IP over Fractional T1

Benefits

This feature realizes the IP transmission over some timeslots of a T1 link. The spare

timeslots can be used for other purposes, for example, the spare timeslots can be used

for 2G network transmission so as to share transmission resources when 2G and

3Gco-sited.

Description

The Fractional T1 port of the ZTE RAN satisfies the definition of the af-phy-0130.000.

Each timeslot of the T1 link is equivalent to the 64Kbps transmission capability. The 24

timeslots in each T1 link can be further divided to realize n*64Kbps data transmission.

ZTE RAN realizes IP transmission over the Fractional T1 link 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 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 ZWF22-03-065 IP over Electric FE/GE Auto-negotiation

Benefits

This feature supports IP over FE/GE. It makes use of IP network which is featured with

low cost, convenient deployment and strong expansion capability to satisfy the demands

of business development and capacity expansion in the future, providing higher

transmission bandwidth, and satisfies the rapid development requirement of the data

service.

Description

FE transmission supported by ZTE RAN equipment complies with IEEE 802.3u standard.

The physical interface adopts 100BASE-T (RJ45). MAC layer supports IEEE 802.3

standard Ethernet frame structure. The transmission media is twisted pair, the data rate

can reach 100Mbps.

Electric GE transmission supported by ZTE RAN equipment complies with IEEE 802.3ab

standards. The physical interface adopts 1000BASE-T (RJ45). MAC layer supports IEEE

802.3 standard Ethernet frame structure. The transmission media is twisted pair, the data

rate can reach 1000Mbps.

ZTE RAN equipment supports GE modes including 1000Mbps forced and

10/100/1000Mbps auto-negotiation.





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 Optional Synchronization Sources

3.4.1 ZWF22-01-018 Synchronization via Wireline

Benefits

This feature supports synchronizing RNC or Node B from BITS or transmission line to

satisfy the requirement of high-precision frequency synchronization.

Description

ZTE RNC and Node B can use the BITS as the external clock reference source. The

electric feature of the BITS clock must conform to ITU G.703, and the quality of the BITS

clock must conform to ITU G.812. The RNC supports 2048 kHz, 2048 kbps, and 1544

kbps BITS reference inputs.

The RNC can also extract and trace line clocks from physical transmission interfaces

providing synchronous timing information. These interfaces include E1, T1, STM-1, and

POS interfaces.

The Node B can also extract and trace line clocks from Iub interface providing

synchronous timing information. These interfaces include E1, T1 and STM-1 interfaces.

The output of timing information from these service interfaces should meet the

synchronization requirements given in ITU G.823/G.824.

The Node B can also output 2.048 Mbps clock signals via E1 interfaces. The clock

conforms to ITU-T G.703 and is provided as a clock reference to other Node Bs, BTSs,

or equipment located in the same site.





Introduced Version

U9.1&Before

Enhanced Function

No

3.4.2 ZWF22-03-010 IEEE 1588

Benefits

This feature supports synchronizing Node B from IP transmission network via IEEE 1588

V2 protocol. It solves the problem that the Node B cannot synchronize to BITS clock

source or transmission line as well as avoiding the high investment on GPS.

Description

As an asynchronous network, the clock synchronization between RNC and Node B isn’t

needed in UMTS. But the frequency deviation may be out of scope after long time

running because the high-precision clock can’t be provided in the Node B, and the UE

handover between different Node Bs may be influenced. So the Node B should be

synchronized to the high-precision clock to guarantee network KPI. The accuracy of

frequency synchronized is 0.05ppm.

ZTE supports IEEE1588 network time synchronization protocol (also called Precision

Time Protocol), which synchronizes clock to a distributed system consisting of one or

more nodes by network communication. This protocol adopts the master-slave

synchronization mode. The slave port can obtain synchronization information from the

master port to implement high-precision clock synchronization.

IEEE 1588 clocks can be used for clock synchronization when FE or GE transmission is

used on the Iub interface. The IEEE 1588 clock synchronization function is completed by

RNC and Node B together. The RNC serves as Master that provides exact clock source.

The Node B serves as Slave that extracts the clock information and performs the clock

synchronization. The clock precision may be influenced by the delay and the jitter of the





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:

− One trip transport delay <= 20ms

− Transport delay variation <=7ms

− Frame loss rate <=0.05%

ZTE also supports clock synchronization from the switch via IEEE 1588 protocol. The

switch serves as Master that provides high–precision 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.

Figure 3-8 Application of IEEE 1588 Clock Synchronization

Introduced Version

U9.1&Before, UTRAN supports frequency synchronization

Enhanced Function

Node B Master

RNC

RNC Master

Slave

Node B

Switch

Switch

Slave

GPS Network





From U9.3 ZTE Node B supports clock synchronization from the switch via IEEE 1588

protocol.

3.5 Other TN Related Functionality

3.5.1 ZWF22-01-003 Iub Interface over IP

Benefits

This feature uses IP transmission network to support Iub interface between RNC and

Node B for providing higher traffic bandwidth with lower cost.

Description

Full functions defined in 3GPP Iub protocols are supported when IP transmission is

applied to connect RNC with Node B.

Figure 3-9 IP Protocol Stack on Iub Interface

Physical Layer

Data Link

IP

SCTP

NBAP

Data Link

IP

Iub FP





Radio Network Layer

Radio Network Layer

UDP





IP transmission is based on various physical media. ZTE supports different IP

transmission network interfaces, for example, E1, T1, SDH (STM-1, CSTM-1, STM-4),

FE/GE. See details in corresponding document.

Introduced Version

U9.1&Before

Enhanced Function

No.

3.5.2 ZWF22-01-004 Iu/Iub interface via satellite

Benefits

This feature supports Iub/Iu interface via satellite to cover the scenarios with poor

transmission resource, such as island or peak. The feature applies to not only scenarios

of satellite transmission, but also scenarios with big transmission delay or higher bit error

rate on Iub/Iu interface.

Description

The Node B sends data to RNC through the links of the satellite, as shown in the

topology below:





Figure 3-10 Iub Interface Transmission through the Satellite

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

channel and the BER of an optical channel (10-10). In 3GPP TS 25.104, the BER of an air

interface is required to be smaller than 10-3, 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 can’t be guaranteed fully.

Introduced Version

U9.1&Before

Enhanced Function

In U9.3, Iub over satellite support 400ms delay.

3.5.3 ZWF22-01-007 IuCS Interface over IP

Benefits

This feature uses IP transmission network to support IuCS interface between RNC and

CS domain CN equipment for providing higher traffic bandwidth with lower cost.

Description

Full functions defined in 3GPP IuCS protocols are supported when IP transmission is

applied to connect RNC with CS core equipments.

Figure 3-11 IP Protocol Stack on IuCS Interface





Physical Layer

Data Link

IP

SCTP

M3UA

SCCP

RANAP

Data Link

IP

Iu UP





Radio Network Layer

Radio Network Layer

UDP

RTP/RTCP*




Introduced Version

U9.1&Before

Enhanced Function

No.

3.5.4 ZWF22-01-008 IuPS Interface over IP

Benefits

This feature uses IP transmission network to support IuPS interface between RNC and

PS domain CN equipment for providing higher traffic bandwidth with lower cost.

Description





Full functions defined in 3GPP IuPS protocols are supported when IP transmission is

applied to connect RNC with PS core equipments.

Figure 3-12 IP Protocol Stack on IuPS Interface

Physical Layer

Data Link

IP

SCTP

M3UA

SCCP

RANAP

Data Link

IP

Iu UP





Radio Network Layer

Radio Network Layer

UDP

GTP-U




Introduced Version

U9.1&Before

Enhanced Function

No.

3.5.5 ZWF22-01-009 DS0 Cross Connection

Benefits





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 DS0 Cross Connection

TDM

TDM

T1/E1/C-STM-1

Timeslots for 3G

Timeslots for 2G

Timeslots switched Timeslots switched

2G BTS

3G Node B

2G BSC

3G RNC

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 ZWF22-01-010 IP/ATM Hybrid Transmission

Benefits

This feature supports ATM and IP protocol which are simultaneously used as the

transmission on Iub interface. For operator, the benefits brought by hybrid transmission

are as follows:

− Adequately utilize the existing TDM transmission network, carry real-time

traffic (such as voice) on ATM to guarantee the QoS, and save the cost of

upgrade to the high quality IP network carrying all services.

− 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 ZWF22-01-011 Transmission Path Protection on Iub

Benefits





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

In hybrid transmission network of ATM over E1 and IP over Ethernet, transmission

network uses different physical connections, E1 and Ethernet, and different

transport protocols, ATM and IP. ZTE RAN equipment support SSCOP link for ATM

and SCTP Association for IP simultaneously. Because both SSCOP and SCTP are

end-to-end reliable connections between RNC and Node B, the link status can be

monitored in time and can be used to trigger physical connection handover between

ATM and IP. ATM over E1 connection can be used for NCP/CCP/ALCAP, common

transport channels and real time services (including SRB), and Ethernet connection





is configured with SCTP Association for redundancy protection only in normal

status. When RNC detects SSCOP link fails, signal link can be handed over to

SCTP Association.

In hybrid transmission network of IP over E1 and IP over Ethernet, transmission

network uses different physical connections, E1 and Ethernet, but same transport

protocol (IP). Each IP connection use dedicated IP address. ZTE RAN equipment

supports SCTP dual homing configuration in which the Association of IP over E1

has a higher priority than IP over Ethernet in Node B and two virtual IP addresses

are configured for first Hop and second Hop in RNC. RNC and Node B can use IP

routing realize signal link redundancy protection.

− Service

Possibly ongoing services boned on dedicated or common channels will be

dropped during physical connection handover, but new services will not be

impacted and can access RAN network normally.

In hybrid transmission network of ATM over E1 and IP over Ethernet, traffic services

in User Plane are boned in AAL2 path in ATM protocol, and in UDP packet in IP

protocol. Both AAL2 path and UDP are not connection oriented, so link failure can

not be detected in time. ZTE RAN equipment uses the same method as in Control

Plane to hand over traffic services between ATM over E1 and IP over Ethernet

based on link status of SSCOP and SCTP Association.

In hybrid transmission network of IP over E1 and IP over Ethernet, ZTE RAN

equipment supports periodical monitoring on common transport channels.

Synchronization failure of FP (Frame Protocol) will trigger physical connection

handover. Routing strategies are controlled by Node B. IP address in Radio Link

Setup Response message sent by Node B indicates which physical connection

should be used for traffic services.

− O&M

RNC can configure multiple routing links of different priorities to realize OMCB

channel’s 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 operator’s

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 path’s 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.





In a multi-path protection group, operators can configure the corresponding transmission

path priority in the admission control. System will select a transmission path which has

highest priority in CAC process.

When the equivalent bandwidth of path is 0, the new call will be switched to low-priority

transmission path.

When the equivalent bandwidth of path is reduced, CAC will determine whether the call

can be accepted in this path; if not, the case will be transferred to another path control.

When the equivalent bandwidth of path is increased, the transmission path will be able to

accept more calls.

Protection among the transmission paths is divided into ATM transmission path

protection, IP transmission path protection and the ATM & IP transmission path

protection.

Introduced Version

U9.2 supports dual-path protection

Enhanced Function

U9.3 supports multi-path protection

3.5.8 ZWF22-01-012 Iur Interface over IP

Benefits

This feature uses IP transmission network to support Iur interface between RNC and

other RNC equipment for providing higher traffic bandwidth with lower cost.

Description

Full functions defined in 3GPP Iur protocols are supported when IP transmission is

applied to connect RNC with other RNC equipments.





Figure 3-14 IP Protocol Stack on Iur Interface

Physical Layer

Data Link

IP

SCTP

M3UA

SCCP

RNSAP

Data Link

IP

Iur FP





Radio Network Layer

Radio Network Layer

UDP




Introduced Version

U9.1&Before

Enhanced Function

No.

3.5.9 ZWF22-03-016 UDP mux

Benefits





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 ZWF22-03-019 RTP mux

Benefits

This feature can effectively reduce the requirement of the IP transmission bandwidth in

IU-CS, thereby reducing the cost of the transmission resource.

Description

In IP UTRAN, IUUP frame in IuCS user plane is carried on RTP protocol. For typical CS

traffic, the payload is small; after the package in RTP/UDP/IP and link layer, the

overhead of the frame is too large compared to the payload, wasting much of the IuCS

bandwidth





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

Subflow1

Subflow2

Subflow3

Link1

Link2

Link3

Link A

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 ZWF22-03-022 Transmission CAC based on SLA-PM

Benefits

After SLA function is configured in IP network, transmission CAC strategy can be

adjusted by the SLA monitoring results (jitter, delay and packet loss rate). This function

can automatically change the transmission bandwidth for CAC by tracking the real-time





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 doesn’t 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 ZWF22-03-027 IPsec Support in Node B

Benefits

The feature is used to provide high-quality communications-security for our customers,

which consists of Data origin authentication, data integrity, data content confidentiality

and anti-replay protection. These services of IP protection can provide an end to end

network security solution.

Description

IP Security (IPsec) refers to a series of open protocols defined by IETF to provide high

quality, interoperable, and security for IP packets. By means of facilities including

encryption and data origin authentication,

It is a common security policy for flexible solutions. IPSec protocol consists of follow:

− AH (Authentication Header): AH provides connectionless integrity, data

authentication and replay protection initiated.

− ESP (Encapsulating Security Payload): ESP can also provide encryption.

− 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 System’s 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





4 HSDPA

4.1 ZWF23-01-A HSDPA Introduction Package

4.1.1 ZWF23-01-003 HSDPA UE Category Support

Benefits

This feature supports different HSDPA UE categories. Different UE categories are

defined to support different data rate capability.

Description

ZTE RAN equipment supports all HSDPA UE categories defined in 3GPP TS 25.306

which describes the terminal capability for HSDPA. HS-DSCH physical layer categories.

See Table 4-1.

Table 4-1 HSDPA UE Category Supported by ZTE current version

Category

Max. No. of

HS-DSCH Codes

Min. Inter-TTI Interval

Supported Modulations

Supported carrier

Number

MIMO Operation

MAC Layer

Peak Bit Rate

1 5 3 QPSK/16QAM 1 N/a 1.2Mbps








9 15 1 QPSK/16QAM 1 N/a 10Mbps

10 15 1 QPSK/16QAM 1 N/a 13.9Mbps

11 5 2 QPSK 1 N/a 0.9Mbps





Category

Max. No. of

HS-DSCH Codes

Min. Inter-TTI Interval


Supported carrier

Number

MIMO Operation

MAC Layer

Peak Bit Rate

12 5 1 QPSK 1 N/a 1.8Mbps

13 15 1 QPSK/16QAM/64QAM 1 N/a 17.6Mbps

14 15 1 QPSK/16QAM/64QAM 1 N/a 21Mbps

15 15 1 QPSK/16QAM 1 Activated 23.3Mbps

16 15 1 QPSK/16QAM 1 Activated 27.9Mbps

17 15 1 QPSK/16QAM/64QAM 1 Inactivated 17.6Mbps

QPSK/16QAM 1 Activated 23.3Mbps

18 15 1 QPSK/16QAM/64QAM 1 Inactivated 21Mbps

QPSK/16QAM 1 Activated 27.9Mbps

19 15 1 QPSK/16QAM/64QAM 1 Activated 35.3Mbps


21 15 1 QPSK/16QAM 2 N/a 23.4Mbps

22 15 1 QPSK/16QAM 2 N/a 28.0Mbps





ZTE RAN equipment supports automatically recognize and activate corresponding

HSPA+ functions based on UE category.

Introduced Version

U9.1&Before supports UE with all HS-DSCH physical layer categories below 14. UEs of

Category 13 and Category 14 support 64QAM but not MIMO.

Enhanced Function

In U9.2, UE with HS-DSCH physical layer categories 15, 16, 17 and 18 are supported.

UEs of Category 15 and Category 16 support MIMO but not 64QAM. UEs of Category 17

and Category 18 support 64QAM and MIMO, but the two technologies cannot be used

simultaneously.





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 ZWF23-01-004 Flexible HSDPA Deployment

Benefits

This feature supports flexible deployment of dedicated HSDPA carrier or R99 and HSDPA in the same carrier.

Deployment of R99 and HSDPA in the same carrier will use the spare resources of R99 for high data speed services. The HSDPA can make full use of the remaining resources in cells to improve resource utilization and reduce the OPEX.

Deployment of dedicated HSDPA carrier supports higher downlink peak rate and cell throughout of PS service on HSDPA dedicated carrier.

Description

The HSDPA deployment supports two ways:

− One carrier supports R99 and HSDPA simultaneously.

− Dedicated carrier constructs a HSDPA network.

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). ZTE’s 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 ZWF23-01-011 HSDPA Adaptive Modulation and Coding

Benefits

This feature provides a link adaptation technology which can realize real time balance of

the link according to the change of the fading channel to increase system capacity and

improve communication quality.

Description





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 ZWF23-01-012 HSDPA Multiplex

Benefits

This feature supports HS-PDSCH code division multiplexing and time division to share

HSPA channel and improve the channel utilization to the largest extent.

Description

The HS-PDSCH is shared by all HSDPA users in the cell. Node B will divide the

resources to different UEs. ZTE RAN equipments can support the following multiplexing

methods:

− Code Division Multiplexing

ZTE UMTS Node B allows up to four UEs to be scheduled within a 2ms TTI in

a cell. However, the number of channelized codes allocated to a UE is limited

by UE HSDPA category.

− Time Division Multiplexing

The same HS-DSCH channel can be allocated to the different HSDPA users

according to 2ms TTI.

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 user’s requirements of services.

Introduced Version

U9.1&Before

Enhanced Function

No





4.1.5 ZWF23-01-013 HSDPA Fast Scheduling

Benefits

This feature can provide many kinds of scheduling algorithm. It will use a 2ms period to

schedule terminal channel and service. It will implement the fast scheduling on radio

resources among different users to improve the throughput of the whole cell.

Description

HSDPA introduces a new functional entity MAC-hs which is moved from RNC to NodeB

to finish the data scheduling. Based on the channel quality information, terminal

capability, QoS category and the current available NodeB power/code resources, NodeB

will implement the fast scheduling with a 2ms period for the terminal data services.

ZTE RAN equipments support Proportional Fair (PF) scheduling algorithms.

NodeB schedule should consider the channel quality and history flow of user. The cell

throughput and the user fairness should be considered simultaneously.

The PF algorithm can help realize larger throughput rates and better service fairness.

ZTE RAN equipments can support the following Enhanced Functions based on PF

scheduling algorithm.

− Support configurable Fair Factor

By configuration of different fair factors, the PF algorithm will approach to fair

service time algorithm (more and more fair) or Max C/I (less and less fair, but

will gain the highest cell throughput). It can meet different operator’s

requirements.

− Support Service PRI and User PRI

Service PRI and User PRI will be performed by SPI (Schedule Priority

Indicator). It will be mapped by RAB parameter from CN (Please refer to.

ZWF23-05-001 HSDPA QoS Mapping). SPI is an input during Node B

scheduling.





− Support Service GBR

Node B will consider the GRB parameter during scheduling to provide the

wireless bearer for the real time service like streaming or conversation

services.

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 ZWF23-01-014 HSDPA HARQ

Benefits

This feature provides a fast inner-loop ARQ error re-transmission mechanism in NodeB.

Relative to the outer-loop ARQ mode of RLC in RNC, it can obviously reduce

air-interface data transmission delay and increase data peak rate.

Description

HARQ (Hybrid Automatic Repeat request) is an integration of ARQ and FEC (Forward

Error Correction) to introduce the error re-transmission mechanism in the physical layer

and get the combination gain through the combination of re-transmission data.

ZTE RAN equipments can support the following HARQ strategies:

− Chase Combining (CC)

The retransmission consists of the same set of coded bits as the initial





transmission

− Incremental Redundancy (IR)

It consists of PIR (Partial Incremental Redundancy) and FIR (Full Incremental

Redundancy). PIR indicates that the check bit is different and the system bit is

fixed between re-transmission and the first transmission. The re-transmission

data can be self-decoded. FIR will transmit check bit with priority. It cannot

make self-decoding due to the incomplete system bit.

HSDPA HARQ uses the Stop and Wait protocol during the data transmission. ZTE’s 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 ZWF23-01-015 HSDPA CQI Adjustment

Benefits

This feature supports adjusting the CQI from different UEs, improving the available level

of CQI and the performance of scheduling algorithm.

Description





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

− The BLER is fluctuated greatly

− The UE cannot acquire due to QoS

− System throughput is reduced

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 ZWF23-01-016 HSDPA 16QAM

Benefits

This feature offers 16QAM modulation technology for HS-PDSCH channel to improve peak rate and spectrum efficiency for HSDPA subscribers.

Description





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 16 QAM Constellation Graph

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 ZWF23-01-021 HSDPA Cell Indicator in Idle Mode

Benefits

This feature indicates whether HSDPA is supported in the cell to make UE select the

suitable cell.

Description





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 ZWF23-01-022 HSDPA 1.8Mbps Peak Bit Rate

Benefits

This feature can support 5 SF16 HS-DSCH channels to reach 1.8Mbps HSDPA peak

rate per subscriber or per cell.

Description

ZTE’s UMTS RAN supports 5 SF16 HS-DSCH channels. When the UE uses an

interactive service or background service in an HS-DSCH, the peak rate in the MAC layer

can be as high as 1.8 Mbps. The HSDPA UE capability level is 3 to 10 or 12.

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.1.11 ZWF23-01-023 HSDPA 16 Users per cell

Benefits

This feature provides the possibility to support maximum 16 HSDPA subscribers in a

single cell simultaneously.

Description

ZTE’s UMTS RAN equipments can allocate channel resources and complete data

scheduling for 16 HSDPA subscribers per cell, then 16 HSDPA subscribers can be

supported simultaneously.

Introduced Version

U9.1&Before

Enhanced Function

No


Benefits



Description

ZTE’s UMTS RAN equipments offer 5 HS-DSCH channels, which use SF=16

channelized codes for one UE. When the UE uses PS service in an HS-DSCH, the peak

rate in the MAC layer can reach 3.6 Mbps. In this case, the HSDPA UE category is 5 to

10.



Introduced Version





U9.1&Before

Enhanced Function

No

4.1.13 ZWF23-02-001 PS Interactive/Background Service over HSDPA

Benefits

This feature provides interactive/background RABs over HSDPA channels. This feature

makes it possible to bear more services and provide higher service speed than over DCH

channel.

Description

HSDPA service using high-order 16QAM modulation, AMC, HARQ and fast scheduling

will provide higher channel rate to share with multi-users and is suitable for the

interactive/background data services. The higher peak rate will effectively improve user

experience.

ZTE RAN equipments can support the peak rate (configuring corresponding functions)

up to physical layer 14.4Mbps (MAC layer 13.976Mbps). In fact the biggest rate provided

to user is decided by UE category, MBR in CN, system load, radio environment and so

on.

Radio parameters in RAB for interactive/background PS data services are fully compliant

to 3GPP TS 34.108.

Introduced Version

U9.1&Before supports 13.976Mbps MAC peak data speed

Enhanced Function

No





4.1.14 ZWF23-02-002 PS Streaming Service over HSDPA

Benefits

This feature provides streaming packet data services with a guaranteed quality of service

and a higher data rate than that provided by DCH.

Description

This feature supports streaming RABs over HS-DSCH channels for packet data services,

for example, streaming media.

HS-DSCH provides the service to all UEs using this channel and will be suitable for

bearing the data service with strong burst. ZTE equipments support data scheduling

algorithm based on GBR (i.e. ZWF23-01-013 HSDPA fast scheduling) and make the

streaming services bear on HS-DSCH.

The guaranteed bit rate of a streaming RAB is assigned by CN and assured by RAN. But

in case of bad radio condition, it is possible for streaming RAB to excessively consume

system resource as RAN has to guarantee GBR. This case is avoided when streaming

RAB is carried on DCH and E-DCH via RAN limiting the maximum uplink/downlink

transmission power. As for streaming RAB carried on HS-DSCH, ZTE RAN monitors

current downlink power of each streaming RAB. If the power is high enough, ZTE RAN

initiates GBR negotiation or hand over the user to another carrier. In this way, resource

consumption of streaming RAB is limited in bad radio condition. After GBR is

re-negotiated to be downgraded, GBR will not be upgraded unless the UE moves to

another cell. If RAB re-negotiation process cannot be initiated and there is no other

carrier for handover, the GBR service could be dropped due to bad radio condition and

resource consuming limitation.

Radio parameters in RAB for streaming PS data services are fully compliant to 3GPP TS

34.108.

Introduced Version

U9.1&Before

Enhanced Function





In release U9.2, limit resource consumption of streaming RAB carrier on HS-DSCH is

supported.

4.1.15 ZWF23-02-003 RAB Combination for CS over DCH and PS over HSDPA

Benefits

The RAB combination is used for concurrent services of CS and PS domain and is used to support simultaneous voice or video call services in CS domain and packet data service in PS domain.

Description

This feature supports the following concurrent services in CS domain and I/B/S services

in PS domain:

− Concurrent services of multi-rate AMR speech services in CS domain and

I/B/S services in PS domain.

− Concurrent services of video call in CS domain and I/B/S services in PS

domain.

Note: Supporting one CS service combining with three PS services at most.

In the case of combination of CS services and PS services on HSDPA, the maximum

rate of user is determined by UE category, MBR subscription in CN, system load, radio

environment and so on.

The supported RB combinations are compliant to 3GPP TS 34.108.

Introduced Version

U9.1&Before

Enhanced Function

No.





4.1.16 ZWF23-02-004 RAB Combination for Multiple Packet Data Services over HSDPA

Benefits

This feature supports using HSDPA channel to bear multiple RABs for several PS

services. The RAB combination provides the bearer for multiple PDP context applications.

RAB combination supports multiple packet data services such as receiving MMS while

packet data services are going on. The IMS-based streaming services and VOIP also

need to use multiple PDPs simultaneously.

Description

ZWF23-02-004 HSDPA supports a maximum of three concurrent PS interaction services,

background services, and streaming services. The maximum rate of each PS service

depends on the rate configured in the CN. Additionally, the sum of all service rates

cannot exceed the maximum rate of HSDPA. The peak rate depends on the UE

capability level, system load, and local wireless environment.

ZTE’s UMTS RAN allows HSDPA to carry multiple concurrent PS services. The RAB

parameters comply with the 3GPP TS 34.108 protocol.

Introduced Version

U9.1&Before

Enhanced Function

No.

4.1.17 ZWF23-03-001 HS-DSCH serving cell change

Benefits

This feature makes it possible to keep service continuity and ensure communication

quality when user is moving among HSDPA cells.

Description





Every HSDPA user’s 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 ZWF23-03-002 HS-DSCH handover to/from DCH

Benefits

When the UE roams between HSDPA cell and R99 cell, the migration between the

HS-DSCH and DCH occurs to keep service continuity.

Description





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 ZWF23-03-003 HS-DSCH inter-RAT Reselection

Benefits

This feature keeps service continuity and ensures communication quality during user moving from WCDMA cell to GSM cell.

Description





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 ZWF23-03-004 HSDPA Soft/Softer Handover of A-DPCH

Benefits

This feature supports A-DPCH soft/softer handover when HSDPA users are moving

among cells with same frequency.

− It enhances reliability of signal data transmission.

− It can keep the UE synchronization in different cells because of the multi-path

effect of A-DPCH active set.

− 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 ZWF23-03-005 HSDPA over Iur

Benefits

This feature offers HSDPA data frame transmission over Iur interface between RNCs. It

improves high speed data service experience when the subscriber is moving between

RNCs.

Description

ZTE’s UMTS RAN equipments offer HSDPA channel parameters configuration of DRNC

and subject Node B when HSDPA subscriber is moving in cells that belong to different

RNCs. As a result, it enables HSDPA data frame transmission over Iur interface to make

sure HS-DSCH data transmission does not fall back to DCH channel in case of

inter-RNC handover.

Introduced Version

U9.1&Before

Enhanced Function

No

4.1.22 ZWF23-04-001 Admission Control for HSDPA Service

Benefits

− 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.

− Number of HSDPA Services

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.

− HSDPA Data Throughput

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.

− Power and Codes Allocation for Associated DPCH/F-DPCH

HSDPA users need to use associated DPCH (or associated F-DPCH). It is

considers about the occupation of cell download channel code and base station CE

resource based on associated DPCH (or associated F-DPCH).

ZTE RAN equipments will consider basic priority (ZWF21-05-003 Differentiated Service) 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.23 ZWF23-04-002 Overload Control for HSDPA Service

Benefits

This feature reduces load and maintains the system stability when the system is in overload status. It can divide the priority of HSDPA service to allocate different users and services properly.

Description

Overload control of the HSDPA is measured by transmitting power of cells. When the

downlink power reaches the threshold, it will trigger the load control as following:

− Reduce the DCH-borne service rates

− 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).

− Migrate I/B services to the CELL FACH state forcedly

− Drop calls forcedly

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 ZWF23-04-003 Load Balance for HSDPA Service

Benefits

When WCDMA has several frequency bands or is deployed together with GSM network, ensure that the load is properly allocated to different layers so that the service quality and stability of the system can be improved.

Description

After HSDPA is supported, ZTE RAN balances the load of service over HSDPA in

different carriers when different frequency or different band or different system covers

same area; the procedure of load balance of HSDPA is the same as the description in

ZWF21-04-011 Load Balance,

Before release U9.2, downlink power of a cell is a main factor to be taken into account for

HSDPA load balance, as well as whether HSDPA is supported by cell and UE.

As for a service without GBR carried on HSDPA, such as best effort service, downlink

power of a cell is not able to reflect the HSDPA load of such kind of service. So in release

U9.2, HSDPA throughput of cell is introduced as one of the factors in HSDPA load

balance, so that HSDPA load balance for non-GBR service over HSDPA is supported.

As HSPA+ such as MIMO and R8 dual-cell HSDPA is introduced, the peak throughput of

a single user gets improved greatly. But these features may be deployed only in part

carriers. In this case, in order to bring high bit rate service to user, RAN will re-direct to

carrier mapping with UE’s HSPA+ capability during load balancing. For example, when

an MIMO UE camps on a carrier without MIMO capability, RAN will redirect the UE to a

carrier supporting MIMO during PS data requesting.

Introduced Version

U9.1&Before

Enhanced Function

HSDPA load balance for non-GBR service over HSDPA is supported in release U9.2.





From release U9.3, DL HSPA+ capability of cell and UE is considered during HSDPA

load balance.

4.1.25 ZWF23-04-004 Dynamic Channel Type Transfer for HSDPA Service

Benefits

According to user service requirement and system resource utilization, it supports choosing transmission channel and dynamic migration between channels. This feature can make full use of radio resource of system, ensure the stability of system and service QoS.

Description

After introducing HSDPA, ZTE RAN equipments can select DL HS-DSCH, DCH or FACH

channel and relative configuration parameters for users according to services

requirement and system state.

ZTE RAN equipments support dynamic migration between different channels in order to

satisfy services requirement and system resource in the following factor state:

− Save system resource by adjusting channel type dynamically according to I/B

real-time service data flow.

When DL service data flow is too large

When DL service data flow is too small, trigger the migration from HS-DSCH to

FACH

When there is no DL service data flow, trigger the migration from HS-DSCH to

PCH or idle

When PCH UE sends the data, trigger the migration from PCH to HS-DSCH

When UE needs to send data in PCH state, trigger the migration from PCH to

HS-DSCH

− 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 service quality by adjusting channel type according to DL channel

quality.

− When UE in HS-DSCH channel moving to cell margin to touch off 1F event, it

shows the channel quality is bad, and then touch off the migration from

HS-DSCH to DCH.

− Ensure the service continuity by adjusting channel type according to the target

cell for handover.

When DL is FACH, UL must be RACH; when DL is HS-DSCH, UL is DCH or E-DCH.

Introduced Version

U9.1&Before

Enhanced Function

No

4.1.26 ZWF23-04-005 Power Allocation for HSDPA

Benefits

− It enhances the user capacity of HSPDA system.

− It enhances the utilization of radio resource.

Description

HSDPA power control includes HSDPA power allocation and HS-PDSCH Measurement

Power Offset configuration.

ZTE equipments support dynamic HSDPA power configuration modes:

− RNC static configuration

− Once the maximum transmit power is defined by RNC, it will never

change.





− RNC dynamic configuration

− The maximum power is adjusted by RNC dynamically; the following events

will touch off RNC to adjust the total HSDPA power:

When system congests due to HSDPA power limitation, the total HSDPA

power can be enlarged.

When system congests due to R99 power limitation, the total HSDPA power

can be reduced.

The total HSDPA power can be reduced when cell overloads.

− Free configuration by Node B

− 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 ZWF23-04-006 Code Allocation for HSDPA

Benefits

It enhances the user capacity of HSPDA system.





It enhances the utilization of system resource.

Description

After introducing HSDPA into network, ZTE RAN equipments support the following

HSDPA code resource management:

− Downlink Scramble Code

HS-SCCH, HS-PDSCH and associated F-DPCH use cell main scramble code.

− Uplink Scramble Code

HS-DPCCH uses the same scramble as UE uplink DPCCH scramble.

− Downlink Channelized 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.

− Uplink Channelized Code

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 ZWF23-04-007 Congestion Control Strategy for HSDPA

Benefits

− It enhances the user capacity of HSDPA system.

− It enhances the utilization of system resource.

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.

− Channelized codes re-allocation for HSDPA services

− Data rate decrease on DCH channel

− Service pre-emption

− Transmitting power re-allocation for HSDPA services

Introduced Version

U9.1&Before

Enhanced Function

No.

4.1.29 ZWF23-04-011 Fast Power Congestion Control

Benefits





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 ZWF23-05-001 QoS Mapping for HSDPA Service

Benefits

This feature implements the QoS mapping for HSDPA user to support the scheduling based on user and service priority.

Description

The RNC determines the priorities of MAC-hs by QoS of services, then configures it to

Node B and controls MAC-hs to provide services with different priorities to the

subscribers. Service QoS and the mapping of the priorities of MAC-HS can be flexibly

configured by OMC-R according to the requirements of customers.

According to services and customer priority allocated by RAB, the RNC and Node B

equipment support HSDPA SPI (Scheduling Priority Indicator). The higher the SPI is, the

more probable to get scheduling opportunity and scheduling resource.

Introduced Version





U9.1&Before

Enhanced Function

No

4.1.31 ZWF23-05-002 HSDPA Flow Control

Benefits

This feature implements the download link data flow control mechanism between RNC

and NodeB. This mechanism can avoid the data loss caused by the congestion of NodeB

processing capability or the congestion in Iub interface due to the massive data

transmission from RNC.

Description

The data rate of HSDPA user in Uu interface is determined by various aspects, such as

wireless environment, user quantity and transmitting power of cell. All these aspects

change dynamically, therefore Node B scheduler needs flow control to ensure that

downlink data from RNC to UE can match with Uu interface real time rate and excessive

data is in Node B.

ZTE Node B can transmit Capacity Allocation Frame on Iub interface to notify RNC to

adjust some UE’s data transmission rate. The UE’s downlink rate from RNC won’t

exceed the rate of Capacity Allocation Frame. ZTE RNC equipments also support

sending Capacity Request Frame to Node B to trigger schedule resource allocation when

it is necessary, such as that some UE does not have Capacity Allocation Frame for a

long time.

ZTE’s RAN equipments support HS-DSCH transmission channel congestion detection

mechanism in 3GPP TS25.435. It uses FSN (Frame Sequence Number) and DRT (Delay

Relative Time) in HS-DSCH to detect Frame loss ratio and delay changes between data

frames nearby, and determines whether there is congestion in Iub interface. When

congestion is detected and removed, RNC adjusts downlink data transmission rate

according to Congestion Status cell sent by Node B on HS-DSCH.

Introduced Version





U9.1&Before

Enhanced Function

No.

4.1.32 ZWF23-05-003 HSDPA Nominal Bit Rate for I/B Service

Benefits

This feature offers Nominal Bit Rate, which is similar to GBR for I/B services. The feature

can avoid user experience degrading due to the cause that I/B class service users are

blocked and can’t be scheduled long time.

Description

When interactive services and background services are carried on HS-DSCH in ZTE’s

UMTS RAN, downlink NBR can be configured. The RNC configures the GBR for the

interactive/background service according to the NBR and sends the configuration to the

Node B. When performing HSDPA quick scheduling, the Node B provides minimum GBR

for the interactive/background service.

Introduced Version

U9.1&Before

Enhanced Function

No

4.1.33 ZWF23-05-020 Directed Retry between HS-DSCH and DCH

Benefits

This feature can set up service on an appropriate carrier when R99 and HSDPA use separated carriers.

Description





ZTE’s RAN equipments set attributes for different cells. For example, some cells only

support HSDPA services but don’t 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 user’s

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 Other HSDPA Related Functionality


Benefits



Description






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.



Introduced Version

U9.1&Before

Enhanced Function

No


Benefits


rate in physical layer per subscriber or per cell.

Description


channelized codes. When the UE initiates PS service in HS-DSCH, the peak rate in

physical layer can reach 14.4Mbps (in the MAC layer can reach 13.976 Mbps). In this

case, the HSDPA UE capability category must be 10 or higher.



Introduced Version

U9.1&Before

Enhanced Function

No






Benefits



Description

ZTE RAN system supports channel allocation and packet scheduling for 32 HSDPA

users within a cell, thereby maximum 32 HSDPA users are simultaneously supported in

one cell.

Introduced Version

U9.1&Before

Enhanced Function

No


Benefits



Description



one cell.

Introduced Version

U9.1&Before

Enhanced Function





No


Benefits



Description



one cell.

Introduced Version

U9.2

Enhanced Function

No


Benefits



Description

Based on utilizing interference cancellation (MUD), ZTE RAN system supports channel

allocation and packet scheduling for 192 HSDPA users within a cell, thereby maximum

192 HSDPA users are simultaneously supported in one cell.

Introduced Version

UR11.1





Enhanced Function

No

4.2.7 ZWF23-01-041 F-DPCH & SRB over HSDPA

Benefits

This feature enables F-DPCH to decrease the occupancy of channelized codes in downlink for HSDPA associated channels to improve cell throughout of multi users.

When ZTE’s UMTS RAN equipments offer F-DPCH, it means that all downlink services

and Signaling Radio Bearer are carried on HS-DSCH.

Description

ZTE’s UMTS RAN equipments support F-DPCH (Fractional DPCH) in 3GPP R6.

F-DPCH does not carry any service data or signaling besides uplink inner loop power

control information (TPC commands). F-DPCH uses channelized code with SF=256.

TPC command per slot per user is 2 bits, and every slot of the channel with SF=256 can

transmit 20 bits data in a frame, which means at most 10 users can share one F-DPCH.

When F-DPCH replaces associated channel for HSDPA users, downlink channelized

code consumption for associated channel is saved, so more channelized codes will be

left for HS-DSCH when there are more HSDPA users in cell and the cell throughout is

also be improved.

Because F-DPCH carries neither service data nor signaling, as a result, when F-DPCH

replaces associated channel, RRC signaling and NAS layer signaling need to be carried

by HS-DSCH. ZTE’s UMTS RAN equipments support SRB over HS-DSCH., and all

SRBs are multiplexed to one MAC-d Flow. Proper QoS parameters are configured for

SRB, such as that ARP and SPI are set to the highest priority; Node B scheduler ensures

SRB transmission in a similar way as GBR; the reliability of the RRC signaling could be

ensured.

This feature offers RRC signaling and NAS layer signaling transmission over HS-PDSCH.

It can speed up the signaling flow in the Uu interface remarkably, and reduce the call

delay of subsequent service establishment.

Introduced Version





U9.1&Before

Enhanced Function

No

4.2.8 ZWF23-01-042 HSDPA HS-DPCCH ACK/NACK enhancement

Benefits

This feature can reduce the peak transmitting power of UE that supports HSDPA, and

improve coverage of HS-DSCH channel for a cell.

Description

ZTE’s UMTS RAN supports the HS-DPCCH ACK/NACK enhancement function in 3GPP

R6. Before and after the HS-DPCCH sends the ACK/NACK message, 3GPP introduces

the PRE-AMBLE and POST-AMBLE respectively in R6. Due to this enhancement

function, the demodulation performance of ACK/NACK of the HS-DPCCH is improved for

Node B; the transmitting power of the HS-DPCCH is reduced for UE.

Introduced Version

U9.1&Before

Enhanced Function

No

4.2.9 ZWF23-04-021 Fast Dynamic Code Allocation

Benefits

This feature quickly feedbacks the available HS-PDSCH code to increase code utilization

and improve HSDPA downlink throughput.

Description





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 ZWF23-04-021 Code Sharing between Cells

Benefits

This feature helps to fully utilize the HSDPA code resource license of a cell and improve

the peak rate of the cell.

Description

Generally, operator purchases the HSDPA code license of each cell according to the

number of code. For example, 5 codes, 10 codes, or 15 codes as a set, the code is

SF=16 HS-DSCH channelized code. If the number of codes is different, the peak bit rate

is also different. Therefore, the operator may purchase the HSDPA code license

according to the development of the data service, rather than buying the entire 15-code

license so as to effectively reduce the operation cost.

Presume that the operator purchases the HSDPA license of each cell by 5 or 10 codes.

Since the transient load of each cell in a base station is different, there will be a case that

the data requirement of one cell is very high and exceeds the peak bit rate of 5 or 10

codes, while the data requirement of other cells is very low and the 5 or 10 codes cannot

be used thoroughly.

With this feature, the HSDPA code license can be shared among different cells. In above

scenario, the light load cell may lend its code license to the heavy load cells. As a result,

the transient available HSDPA codes of a single cell exceed the number of codes

authorized to it, but will not exceed the threshold of 15 HS-DSCH channelized codes per

cell. The total number of HS-DSCH channelized codes used by all cells does not exceed

the total number of codes license authorized to all cells.

The ZTE UTRAN device allows the code resources to be shared among all R99 and

HSDPA cells which share the same carrier in a Node B, that is, the HS-DSCH

channelized code license of these cells can be used accumulatively.

Introduced Version

U9.1&Before

Enhanced Function





No

5 MBMS

5.1 ZWF24-01-A MBMS Introduction Package

5.1.1 ZWF24-01-001 MBMS Services

Benefits

MBMS is introduced in 3GPP R6, which is used to transmit multimedia data by broadcast

or multicast method. Compared to CBS services, MBMS is able to provide not only text

message with low-rate, but also high rate multimedia services with rich video and audio.

Description

ZTE RAN supports both streaming and background MBMS (through PS domain CN)

services, with a maximum rate of 256Kbps in single channel. MBMS can be used to

transmit video clips, audio tracks, multimedia and text. It is suitable for services such as

mobile TV, music radio and mobile advertisement.

ZTE RAN supports both MBMS bearer modes: PTP and PTM. Broadcasting in the whole

cell, PTM mode adopts the Forward Access Channel (FACH) to carry service data. PTP

mode uses the Dedicated Channel (DCH) or HS-DSCH and only transmits data to single

users.

ZTE RAN can provide MBMS services of various types and rates concurrently. The

provided rate is determined on which feature(s) is configured:

ZWF24-10-001 MBMS 16Kbps Channel Rate









ZTE RAN supports concurrent transmission of several MBMS services, or MBMS + CS

services, or MBMS + PS services. Multi-service concurrent reception by UE depends on

UE’s capability. If UE cannot receive concurrently more than one service, it’s up to UE to

select one of the services to receive.

Introduced Version

U9.1&Before

Enhanced Function

No

5.1.2 ZWF24-01-002 MBMS Broadcast Mode

Benefits

This feature supports MBMS services in broadcast mode. When broadcast mode is

indicated from core network, all users in a cell belonging to MBMS service area can

receive this MBMS services. MBMS broadcast service is transmitted in MBMS service

areas whether there’s user receiving the service or not. MBMS broadcast mode suits for

deploy some free notice service.

Description

ZTE RAN supports MBMS broadcast mode. Whether the MBMS adopts the broadcast

mode is subject to the service provider. Core Network (CN) informs the RNC of the

MBMS service mode through the RANAP signaling. If CN instructs the RNC to establish

MBMS service in broadcast mode, RNC establishes MTCH in all cells belonging to the

MBMS service area, and maps it into the FACH over S-CCPCH. The service is

transmitted in PTM mode. MBMS service parameters are broadcasted on the MCCH of

these cells.

Introduced Version

U9.1&Before





Enhanced Function

No

5.1.3 ZWF24-01-004 MBMS Scheduling Information

Benefits

This feature supports the discontinuous MBMS reception by UE (DRX), and helps UE to

reduce power consumption.

Description

To realize DRX of MBMS service for the UE, ZTE RAN supports using the MBMS

point-to-multipoint Scheduling Channel (MSCH) to transmit the data scheduling

information of the MBMS PTM service.

Through the MSCH, the RNC indicates when each MTCH channel will send data, how

long the transmission will last, and when the next data packet will be sent. In this way, UE

needn’t monitor the MTCH from which it receives service data. The MSCH is mapped to

an FACH channel and to the same S-CCPCH with the MTCHs, whose scheduling

information is carried on this MSCH.

Introduced Version

U9.1&Before

Enhanced Function

No

5.1.4 ZWF24-01-006 Selective and Soft Combining for PTM MBMS

Benefits

This feature supports combining service data when the services are transmitted with

PTM mode in multiple intra-frequency adjacent cells. In this way, the receiving

performance of UE is improved, and the transmitting power of Node B is reduced. So

capacity of cell is improved.





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





de-synchronized, they will be re-synchronized to ensure strict synchronization

requirements of soft combining.

Introduced Version

U9.1&Before

Enhanced Function

No

5.1.5 ZWF24-01-007 Frequency Layer Convergence and Dispersion

Benefits

This feature supports transmission of MBMS services among multiple carriers with the

same coverage. It is used to allocate MBMS traffic among carriers properly. The

influence between MBMS service and other service is eliminated.

Description

When transmitting MBMS service in the sector covered with multi carriers, RAN generally

selects one of the carriers as the preferred carrier for a certain MBMS service. This

MBMS service can only be transmitted on the preferred carrier to save radio resource,

and other cells in non-preferred carrier only indicate the preferred frequency information

in the control message on MCCH. For a UE in Idle, FACH or PCH state and resides in

cells of non-preferred carrier, it accesses to the cell in preferred carrier by cell reselection

according to the frequency convergence indicator. It is known as the Carrier

Convergence (FLC).

When FLC occurs, UE will reserve the frequency information where UE has camped

before accessing to the preferred frequency. If FLD is indicated in preferred frequency

cell, UE searches the frequency after the MBMS service ends, and attempts to return to

the original carrier through cell reselection. This process is known as the Carrier

Dispersion (FLD).

ZTE RAN supports two types of preferred carrier policies:





− 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 ZWF24-01-008 Iub Transmission Optimization

Benefits

With this feature, only one transmission bearer is set up on lub interface when the same

MBMS services are transmitted in multiple cells in a Node B. It is to save transmission

bandwidth of Iub interface.

Description

If several cells of one Node B transmit the same MBMS service in PTM, ZTE RAN

supports binding of each transmission bearer in Iub interface to the same transmission

resource (AAL2 Channel or IP port). In this way, the RNC only transmits one MBMS data

package on the shared transmission bearer to Node B to save lub interface transmission

bandwidth. Upon receiving the data, Node B duplicates and distributes the data to all

cells.

Introduced Version

U9.1&Before

Enhanced Function

No





5.1.7 ZWF24-01-021 MBMS Mobility

Benefits

This feature keeps service continuity for a UE moving among cells. It also supports that a

UE in DCH state can hand over to the preferred carrier to receive MBMS service.

Description

When UE which receives MBMS service is moving among the adjacent cells, the bearer

type of MBMS service may be different in source cell and target cell. ZTE RAN supports

the following scenarios:

− PTM mode is adopted in both source cell and target cell

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.

− PTP mode is adopted in both source cell and target cell

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.

− PTP mode is adopted in source cell, and PTM in target cell

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.





− MBMS service is transmitted in source cell but not in target cell.

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 doesn’t 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 ZWF24-01-031 MBMS Admission Control

Benefits

This feature prevents system resources from being consumed excessively when new

MBMS service accesses. So the system stability will not be influenced.

Description





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:

− Downlink transmitting power in cell

− Downlink channelized code

− CE resources in base band board

− Total throughput of MBMS

− Number of MBMS services

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 ZWF24-01-032 Code Allocation for MBMS

Benefits





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

It adopts the CC of SF=256, which is configured at OMC. It is recommended to

consecutively allocate the code occupied by the MICH, P-CPICH, P-CCPCH, AICH

and PICH to save downlink channelized code resources.

− 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

Each MSCH is mapped to a FACH respectively. FACH carrying MSCH is

multiplexed with FACH carrying MTCH. It means MSCH and MTCH shares one

SCCPCH. So scheduling information about MTCH is indicated on this MSCH.

For MBMS service transmitted in PTP mode, it complies with the allocation mechanism

of DCH or HSDPA channelized code.





Introduced Version

U9.1&Before

Enhanced Function

No

5.1.10 ZWF24-01-033 MBMS Power Allocation

Benefits

This feature allocates transmitting power for MBMS service. It supports dynamic

adjustment of SCCPCH transmitting power that carries MBMS service so as to increase

the capacity of cell.

Description

ZTE RAN allocates transmitting power statically for MICH and S-CCPCH carrying MCCH

or MTCH.

ZTE RAN dynamically adjusts transmitting power of the S-CCPCH carrying MTCH as the

following:

− Based on cell load

When the cell is congested or overloaded due to insufficient transmitting power,

ZTE RAN will lower the S-CCPCH transmitting power of some low-priority MBMS

services to recover the cell from overload or congestion.

− Based on the S-CCPCH combining status between adjacent cells

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 ZWF24-01-034 Priority Handling for MBMS

Benefits

With this feature, downlink transmitting power is allocated for MBMS service according to

MBMS service priority. It is helpful for operators to realize strategy of service

differentiation.

Description

ZTE RAN supports the handling of different MBMS services in RRM policies including

admission control, congestion control and load control based on the Traffic Class, ARP

and bearer priority (corresponding to different transport channels):

− 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





normal cell load and maintain high-priority MBMS services.

In ZTE RAN, Priority Handling for MBMS is helpful for operators to realize strategy of

service differentiation.

Introduced Version

U9.1&Before

Enhanced Function

No

5.1.12 ZWF24-01-035 MBMS Overload Control

Benefits

This feature enables to recognize a cell is overload and relieve the cell from overload to

ensure stability of system.

Description

If a cell is overloaded, ZTE RAN downgrades cell load caused by MBMS service as the

following:

− Lower the transmitting power for MBMS services carried in PTM mode

− Delete some 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 FDD MBMS Enhanced Features

5.2.1 ZWF24-02-002 MBMS Enhanced Broadcast Mode

Benefits

This feature supports MBMS service in enhanced broadcast mode. It means system

determines whether to use broadcast or not based on the number of UEs receiving such

MBMS service in a cell to lower resource consumption of channelized codes and power.

Description

ZTE RAN supports the MBMS enhanced broadcast mode. The difference of enhanced

broadcast and common broadcast modes lies in: In enhanced broadcast mode, RNC

decides the transmission mode based on the number of users in a cell. In common

broadcast mode, service will be transmitted whether there are UEs receiving MBMS

service or not. When there are few users receiving MBMS service, a part of radio

resources will be wasted in the common broadcast mode, while this problem can be

avoided in enhanced broadcast mode.

Introduced Version

U9.1&Before

Description

No

5.2.2 ZWF24-02-003 MBMS Bearer Type Selection and Transition

Benefits





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:

− No MBMS data transmission if there is no UE expecting to receive MBMS

service in a cell

− 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 ZWF24-02-004 MBMS PTP over HSDPA

Benefits

This feature supports MBMS service over HS-DSCH in PTP mode and utilizes HS-DSCH

whose frequency efficiency is higher than DCH to improve capacity of MBMS service.

Description

When ZTE RAN transmits MBMS services in PTP mode as mentioned above in

ZWF24-01-010 MBMS Bearer Type Selection and Transition, it will allocate HSDPA

resources for UE to carry MBMS service through radio bearer setup procedure if the UE

is HSDPA capable.

Introduced Version

U9.1&Before

Enhanced Function

No

5.2.4 ZWF24-02-005 MBMS over Iur

Benefits

This feature realizes the mobility of the MBMS multicast service between the RNCs and

ensures that the MBMS multicast service can be received consecutively when the UE

moves.

Description





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 Other MBMS Related Functionality

5.3.1 ZWF24-01-003 MBMS Multicast Mode

Benefits

This feature can support MBMS service in multicast mode. When adopting multicast

mode, only UE who has subscribed for the MBMS service can receive this MBMS service.

Multicast mode is suitable to apply high-level MBMS service for certain users. In

multicast mode, MBMS service will be transmitted only when the number of UE who is

going to receive the service is not zero. That can avoid wasting radio resource.

Description

ZTE RAN can support MBMS multicast mode. Whether MBMS service adopts the

multicast mode is subject to the service provider. The CN informs the RNC of the Radio

Access Bearer (RAB) setup type through the RANAP signaling.

If a UE wishes to receive MBMS multicast service, it must subscribe to the MBMS service

provider in advance, and moreover, UE also needs to register in the Broadcast

Multicast-Service Center (BM-SC) to join certain MBMS service prior to MBMS activation.





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 ZWF24-10-001 MBMS 16Kbps Channel Rate

Benefits

This attribute provides the 16Kbps channel in the PtM mode.

Description

The ZTE RAN device provides the 16Kbps channel for MBMS PtM service.

Introduced Version

U9.1&Before

Enhanced Function

No


Benefits

This attribute provides the 32Kbps channel for the MBMS PTM service.





Description

The ZTE RAN device provides the 32Kbps channel for MBMS PTM service.

Introduced Version

U9.1&Before

Enhanced Function

No


Benefits

This feature can support 64Kbps channel rate in PTM mode.

Description

ZTE RAN supports channel configuration of 64Kbps to carry MBMS services in PTM

mode, with radio parameters compliant with 3GPP TR 25.993.

Introduced Version

U9.1&Before

Enhanced Function

No


Benefits


Description


mode, with radio parameters compliant with 3GPP TR 25.993.





Introduced Version

U9.1&Before

Enhanced Function

No


Benefits


Description


mode, with radio parameters compliant with 3GPP TR 25.993

Introduced Version

U9.1&Before

Enhanced Function

No

6 HSUPA

6.1 ZWF25-01-A HSUPA Introduction Package

6.1.1 ZWF25-01-003 HSUPA Cell Indicator in Idle Mode

Benefits

This feature indicates whether the cell supports HSUPA in system broadcast message

so that UE can camp on a suitable cell.





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 ZWF25-01-004 HSUPA UE Category Support

Benefits

This feature can support the following HSUPA UE categories as shown in Table 6.

Description

ZTE RAN supports the following HSUPA UE categories defined in the 3GPP protocol.

The categories show the different UE capability to support HSUPA service. For details,

please refer to 3GPP TS 25.306.

Table 6-1 HSUPA UE Category Supported by ZTE

Category

Maximum Number of E-DPDCHs

and Smallest Spreading

Factor


Supported TTIs

Maximum Data Rate with 10ms TTI in MAC

Layer

Maximum Data Rate with 2ms

TTI in MAC Layer

1 1xSF4 QPSK 10ms 0.716 Mbps --

2 2XSF4 QPSK 10ms, 2ms 1.44Mbps 1.40 Mbps

3 2XSF4 QPSK 10ms 1.44 Mbps --





4 2XSF2 QPSK 10ms, 2ms 2.0 Mbps 2.89 Mbps

5 2XSF2 QPSK 10ms 2.0 Mbps --

6 2XSF2+2XSF4 QPSK 10ms, 2ms 2.0 Mbps 5.74 Mbps

7 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 ZWF25-01-005 Flexible HSUPA Deployment

Benefits

This feature supports flexible deployment of dedicated HSUPA carrier or R99 and HSUPA in the same carrier.

Deployment of the same carrier is utilized for R99 and HSUPA in uplink, and uses

characteristic of HSUPA Fast Scheduling to develop high-speed data service, improve

the gain of frequency spectrum, and lower the cost of network operation.

Deployment of HSUPA in dedicated carrier to provide higher peak uplink data rate and

throughput of a cell.

Description

Carrier frequency sharing between the HSUPA and R99 means that the cell can provide

uplink R99 service and HSUPA service simultaneously and can allocate common

resources properly between the R99 and the HSUPA. These common resources include

E-AGCH that supports the E-DCH, E-RGCH, and E-HICH, transmitting power of these

downlink channels, transmitting bandwidth of the Iub interface, and uplink interference of

the cell.

The HSUPA is generally deployed with the HSDPA together. ZTE RAN can enable the

HSUPA function in an HSDPA cell to support uplink R99 and HSUPA service





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), it’s 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 ZWF25-01-013 HSUPA Fast Scheduling

Benefits

This feature enables Node B to realize fast scheduling for transmitting uplink date of

multi-HSUPA UEs in a cell.





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 ZWF25-01-014 HSUPA HARQ

Benefits

This feature can support a fast ARQ (Automatic Retransmission Request) mechanism in

inner loop. Compared with ARQ of outer loop in RLC layer of RNC, it can decrease data

transmission delay obviously in Uu interface and increase the maximum date rate.

Description

ZTE RAN supports HSUPA HARQ (Hybrid Automatic Retransmission Request), which is

the same method to HSDPA HARQ (please refer to ZWF23-01-014 HSDPA HARQ).

HARQ adopts the fast retransmission and combination technology to improve the

transmission efficiency fully. Node B can quickly request UE to retransmit error data

received in uplink. Not only gain of time diversity is obtained, but also the requirement of

BLER transmitted for the first time decreases due to fast retransmission, consequently

the transmitting power of UE can be reduced and the capacity of system is improved.

ZTE RAN supports parallel transmission of multiple HARQ processes so that data can be

sent continuously for a certain UE. 4 HARQ processes are supported at most in 10ms

TTI and 8 HARQ processes in 2ms TTI.

Introduced Version

U9.1&Before

Enhanced Function

No

6.1.6 ZWF25-01-021 HSUPA 1.45Mbps Peak Bit Rate

Benefits

This feature can support HSUPA user peak rate up to1.45Mbps.

Description





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 ZWF25-01-022 HSUPA 16 Users per Cell

Benefits

This feature can support 16 HSUPA users simultaneously in single cell.

Description

ZTE RAN can support 16 HSUPA users simultaneously in single cell, and it can realize

data scheduling for 16 users in single cell.

Introduced Version

U9.1&Before

Enhanced Function

No

6.1.8 ZWF25-01-023 HSUPA 2Mbps Peak Bit Rate

Benefits

This feature enables 2Mbps peak uplink rate for one user.

Description





ZTE RAN system supports 2Mbps HSUPA peak rate. When a user’s 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 ZWF25-02-001 PS Interactive/Background Service over HSUPA

Benefits

This feature can support interactive and background service over HSUPA channel.

Compared with DCH channels, more services and higher bit rate can be obtained after

using HSUPA technology.

Description

The HSUPA service is carried over the enhanced dedicated channel E-DCH. Adopting

the technology of QPSK modulation and HARQ, the E-DCH channel can provide higher

bit rate and enable multiple users to share the load of uplink cells. The E-DCH is suitable

for the interactive and background services with high burst. The higher peak rate of the

channel can effectively improve the user experience.

ZTE RAN supports the maximum uplink bit rate of 5.76Mbps. But the actual maximum bit

rate available to the user depends on UE category, the MBR (Maximum Bit Rate)

subscribed in the CN (Core Network), payload of the system, and the wireless

environment at the time of access.

The RAB wireless parameters of the interactive/background PS data services of the ZTE

UMTS RAN comply with 3GPP TS 34.108 protocol.

Introduced Version

In MAC layer, maximum uplink bit rate of 5.76Mbps is supported in U9.1&Before.





Enhanced Function

No.

6.1.10 ZWF25-02-002 PS Streaming Service over HSUPA

Benefits

This feature can support PS streaming service with GBR guaranteed. Compared with

DCH channels, more services and higher bit rate can be obtained after using HSUPA

technology.

Description

This feature supports PS streaming service over E-DCH channel such as video

monitoring.

ZTE RAN supports HSUPA fast scheduling algorithm based on GBR, so streaming

service can be carried over E-DCH.

The RAB wireless parameters of PS streaming service completely comply with 3GPP TS

34.108 in ZTE RAN.

Introduced Version

U9.1&Before

Enhanced Function

No

6.1.11 ZWF25-02-003 RAB Combination for CS over DCH and PS over HSUPA

Benefits

This feature can support RAB combination for CS over DCH and PS over HSUPA, for

example, user can make voice or video call while uploading data.

Description





All ZTE RAN can support CS service and PS I/B/S service over HSUPA concurrently:

− CS AMR voice service

− CS data service, such as video call service.

− CS data streaming service, such as FAX service.

− CS AMR-WB voice service

Note: 1 CS service and 3 PS services can be supported concurrently at most.

When CS service and PS service over HSUPA channel are provided concurrently, the

actual maximum bit rate of the uplink PS service depends on UE category, the MBR

subscribed in the CN (Core Network), payload of the system, and the wireless

environment at the time of access.

The RAB wireless parameters used for supporting CS service and the PS service over

HSUPA concurrently comply with 3GPP TS 34.108 in ZTE RAN.

Introduced Version

U9.1&Before

Enhanced Function

No.

6.1.12 ZWF25-02-004 RAB Combination for Multiple Packet Data Services over HSUPA

Benefits

This feature uses HSUPA channel to carry multiple RABs for multiple PS services, which

respectively are corresponding to multiple PDPs. For instance, a user can receive MMS

while downloading data. IMS-based streaming service, VoIP service and other services

need to use multiple PDPs at the same time as well.

Description





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 ZWF25-03-001 HSUPA Soft/Softer Handover

Benefits

This feature is used to keep service continuity and guarantee the communication quality

while HSUPA users are moving across intra-frequency adjacent cells.

Description

ZTE RAN system supports E-DCH soft/softer handover after HSUPA is introduced. The

handover procedure for E-DCH is the same as that for DCH. (Please refer to

ZWF21-03-001 Soft/Softer Handover).

ZTE RAN system supports intra-Node B E-DCH softer handover as well as inter-Node B

E-DCH soft handover and inter-RNC E-DCH soft handover. (ZWF25-03-005 HSUPA

over Iur is required).

Introduced Version

U9.1&Before

Enhanced Function

No





6.1.14 ZWF25-03-002 E-DCH Serving Cell Change inside Active Set

Benefits

This feature is used to keep the service continuity and guarantee the communication

quality while users are moving across HSUPA cells.

Description

The uplink data of a HSUPA user can be sent through multiple cells in its active set.

However, the scheduling is always controlled by one cell, which is called E-DCH serving

cell.

When HSUPA user is moving across HSUPA cells, ZTE RAN system properly changes

E-DCH serving cell to the cell with best radio quality, according to pilot power level

measured by the UE, to dominate the E-DCH scheduling. Therefore the interference to

other non-serving cells in active set is minimized and scheduling effect is optimized.

If a user is using HSUPA and HSDPA simultaneously, E-DCH serving cell and HSDPA

serving cell is always the same one. If the user moves, E-DCH serving cell and HSDPA

serving cell will change together.

Introduced Version

U9.1&Before

Enhanced Function

No

6.1.15 ZWF25-03-003 E-DCH Intra-Frequency Hard Handover

Benefits

As a supplement to soft handover, E-DCH intra-frequency hard handover is used to keep

the service continuity if the soft handover can not be executed between the

intra-frequency adjacent cells for some causes.

Description





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 ZWF25-03-004 E-DCH Inter-Frequency Hard Handover

Benefits

This feature enables an HSUPA user to hand over between inter-frequency cells, which

helps to keep service continuity while moving across inter-frequency adjacent cells. It

also can be used for load balance among inter-frequency cells in the same coverage.

Description

ZTE RAN system supports E-DCH inter-frequency hard handover when HSUPA is

introduced. The process is the same as that of DCH. (Please refer to ZWF21-03-003

Inter-Frequency Hard Handover).

If the target cell supports HSUPA, E-DCH serving cell will be changed during

inter-frequency hard handover. Otherwise, E-DCH will be switched to DCH during this

operation.

Introduced Version

U9.1&Before

Enhanced Function





No

6.1.17 ZWF25-03-005 HSUPA over Iur

Benefits

This feature enables HSUPA data frame to be transmitted on Iur interface between RNC,

which can improve user experience for high speed data service when moving across

different RNCs.

Description

When an HSUPA user is moving across cells of different RNCs, ZTE RAN system

controls parameters configuration to DRNC and attached Node B via Iur interface.

HSUPA data frame can be transmitted via Iur interface as well so that E-DCH

transmission is retained during inter-RNC handover through Iur interface and it prevents

service from falling back to DCH.

Introduced Version

U9.1&Before

Enhanced Function

No

6.1.18 ZWF25-03-012 HSUPA inter-RAT Reselection

Benefits

This feature keeps service continuity when an HSUPA user is moving between UMTS

cell and GSM cell.

Description

ZTE RAN system supports direct inter-cell handover to force an HSUPA user to access

to the GSM cell when handover is necessary. It is not necessary to fall back from E-DCH

to DCH before inter-RAT reselection.





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 ZWF25-04-001 Admission Control for HSUPA Service

Benefits

This feature implements radio access control for incoming HSUPA service request.

Admission control differentiates service priority and allocates system resources to users

and services according to service priority respectively without decreasing system

stability.

Description

If both Node B and UE are HSUPA capable, HSUPA radio resources can be allocated

during service request process. The scenarios in which the service requires new system

resources include RRC connection, RAB setup, RAB modification, SRNC relocation, Iur

relocation, intra-RNC handover, and dynamic channel allocation, etc. In order to avoid

resource exhaustion or overload when accepting new HSUPA service requests, ZTE

RAN evaluates the system resources for HSUPA according to the following factors:

− Number of HSUPA users

− CE resource of Node B

− Uplink interference

− Capacity of downlink channel





The capacity of downlink channel is restricted by the number of E-HICH/E-RGCH. Each

E-HICH/E-RGCH can be multiplexed for up to 20 HSUPA users.

When performing admission control, ZTE RAN system will consider basic strategy

(Please refer to ZWF21-05-003 Differentiated Service) to enable users and services with

higher priority to get more system resources and higher QoS level.

Introduced Version

U9.1&Before

Enhanced Function

No

6.1.20 ZWF25-04-002 Overload Control for HSUPA Service

Benefits

Overload control can stabilize the overloaded system by decreasing system load.

System resource will be reallocated to users and services according to their priority of

HSUPA services.

Description

Overload control for HSUPA service is based on RTWP measurement of the cell. When

the uplink interference arrives at overload threshold, the following actions of load control

can be triggered.

− Decrease DCH rate

− Trigger inter-frequency/inter-RAT handover

− Drop the calls by force.

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 ZWF25-04-003 Load Balance for HSUPA Service

Benefits

Load balance enables system to deploy traffic to multiple carriers of UMTS or GSM

system if available, making best use of radio resources and improving the quality of the

network.

Description

While HSUPA function is introduced, ZTE RAN system supports HSUPA service load

balance among multiple carriers of UMTS or GSM (Please refer to ZWF21-04-011 Load

Balancing for basic process). Besides the primary factor of uplink interference, the

HSUPA capability of Node B and UE are also considered for HSUPA load balance.

Introduced Version

U9.1&Before

Enhanced Function

No.

6.1.22 ZWF25-04-004 Congestion Control Strategy for HSUPA

Benefits

Congestion control intends to reallocate radio resources in the case of system

congestion according to service attributes, so as to improve the call setup success ratio

and enable proper utilization of system resources.





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:

− Decrease DCH rate

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 ZWF25-04-005 Dynamic Channel Type Transfer for HSUPA Service

Benefits

This feature is used to select and switch bearer channel according to user’s requirement

and system resource utilization status. The feature intends to make full use of radio

resources and guarantee the stability of the system and the QoS of services.

Description

ZTE RAN system is able to select bearer channel among E-DCH, DCH or RACH for the

service and configure radio parameters correspondingly, according to service

requirement and system resource utilization status.





In order to accommodate requirements of service and practical status of system

resources, ZTE RAN system supports the following functions during channel migration:

− Dynamically adjust channel type to save system resource according to the

practical traffic of I/B class service

If traffic is high, migration from RACH to E-DCH will be triggered

If traffic is low, migration from E-DCH to RACH will be triggered

If no traffic, migration from E-DCH to PCH or Idle will be triggered

If a UE at CELL_PCH state needs to transmit data, migration from PCH to

E-DCH will be triggered

− 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.

− Adjust channel type to guarantee the service quality according to downlink

channel quality

If a UE on E-DCH channel moves to the edge of the cell and triggers 1F event,

it indicates that the quality of current channel is bad and channel migration

from E-DCH to DCH will be triggered.

− Adjust channel type to guarantee mobile service continuity according to the

capability of target cell

If the capability of source cell and target cell is different during handover,

channel migration between E-DCH and DCH will be triggered to guarantee the

service continuity.

− Downlink channel migration accompanies uplink channel migration:

If uplink channel is RACH, downlink channel must be FACH. If uplink channel

is E-DCH, generally, downlink channel is HS-DSCH.





Introduced Version

U9.1&Before

Enhanced Function

No

6.1.24 ZWF25-04-006 Power Allocation for HSUPA

Benefits

This feature supports power parameter configuration and control for HSUPA service to

improve system resources utilization and increase system capacity.

Description

HSUPA Power Control includes: Uplink Open Loop Power Control, Uplink Outer Loop

Power Control, and Downlink Open Loop Power Control. ZTE RAN system supports

HSUPA Uplink Open Loop Power Control, including:

− Dynamic configuration of E-DPCCH power offset to DPCCH

In order to guarantee the BBLER of E-DPCCH control signaling, E-DPCCH

Power Offset should be set to a proper value according to different TTI (2ms or

10ms).

− Dynamic configuration of reference E-TFC and the corresponding PO

The system uses various tables of reference E-TFC and corresponding

E-DPDCH Power Offset, according to the different TTI (2ms or 10ms), to

calculate the power required for other non-reference E-TFCs.

− Dynamic configuration of E-DCH MAC-d Flow Power Offset

The power offset varies for different kinds of services to reflect different service

quality. For example, higher priority service has higher power offset to get

better service quality.

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 ZWF25-04-007 Code Allocation for HSUPA

Benefits

This feature provides the configuration of SC (Scrambling Code) and CC (Channelized

Code) for HSUPA service.

Description

After HSUPA is introduced, ZTE RAN system supports HSUPA code management for

the following types

− Downlink SC

E-AGCH, E-HICH/E-RGCH use Primary SC of the cell

− 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 B’s baseband resource.

Introduced Version

U9.1&Before

Enhanced Function

No

6.1.26 ZWF25-04-008 RSEPS based HSUPA RRM

Benefits

This feature provides measurement on Received Scheduled E-DCH Power Share

(RSEPS), which is profitable for admission control, load balance and background noise

estimation with certain accuracy so that effective RRM is achieved.

Description

In 3GPP R6, Node B reports RTWP measurement results and E-DCH Provided Bit Rate

to RNC. However, the uplink load situation of HSUPA cell is not reflected accurately with

the information of RTWP and E-DCH Provided Bit Rate only. Especially when an HSUPA





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.


U9.2

Enhanced Function

No

6.1.27 ZWF25-04-009 HSUPA Adaptive Transmission

Benefits

This feature can improve the HSUPA capacity for the cell through adaptive adjustment of

the HARQ retransmission times.

Description

Simulation result shows that the HARQ retransmission times influence the HUSPA

capacity. If the number of the HUSPA user is small, fewer HARQ retransmission times

are better for the HUSPA capacity. And if the number of the HUSPA user is large, more

HARQ retransmission times are better for the HUSPA capacity.

This feature will adaptively adjust the HUSPA HARQ retransmission times based on the

number of the HUSPA user for the cell. It is useful to improve the HUSPA capacity.

Introduced Version





U9.3

Enhanced Function

None

6.1.28 ZWF25-04-010 HSUPA E-AGCH CLPC

Benefits

This feature implements HSUPA E-AGCH closed-loop power control to effectively

reduce the network interference for the channel without power control. It can increase

system capacity, effectively use DL transmit power, reduce interference and improve

HSUPA performance.

Description

E-AGCH closed-loop power control which can make a closed-loop according to the

feedback of DPCCH and CQI will apply the service channel power control on the control

channels. When the channel quality information obtained by DPCCH or CQI forms the

power control command, this command will not only be transmitted to service channel

but also to the corresponding control channel in order to implement the consistent

association of service channel and corresponding control channel and ensure the reliable

transfer of control information. The power control can be used to resist the modification of

radio environment.

In the state of DPA/UPA coexistence, E-AGCH power control based on CQI or HS-SCCH

can effectively adjust E-AGCH power, the advantages are:

Reduce E-AGCH power consumption;

E-AGCH power control is more flexible. According to 3GPP description, UPA and DPA

have the same serving cell. AGCH belonging to UPA serving cell can use HSDPA CQI

and HS-SCCH to implement E-AGCH power control. E-AGCH power offset will be

adjusted by CQI and HS-SCCH to save DL transmitting power.

CQI reflects the channel quality of serving cell. The available CQI information can adjust

AGCH power offset.





Error probabilities of HS-SCCH demodulation can be adjusted by HS-SCCH transmit

power modification. AGCH power offset can be changed based on HS-SCCH due to the

same requirement of AGCH and HS-SCCH demodulation.

For the E-AGCH 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 3) at least.

Introduced Version

U9.3

Enhanced Function

No

6.1.29 ZWF25-04-011 HSUPA E-RGCH/HICH CLPC

Benefits

This feature implements HSUPA E-RGCH/HICH closed-loop power control. E-HICH

power control based on CQI can reduce average RBS power consumption and increase

DL capacity and bit rate.

Description

E-RGCH/HICH closed-loop power control which can make a closed-loop according to the

feedback of DPCCH and CQI will apply the service channel power control on the control

channels. When the channel quality information obtained by DPCCH or CQI forms the

power control command, this command will not only be transmitted to service channel

but also to the corresponding control channel in order to implement the consistent

association of service channel and corresponding control channel and ensure the reliable

transfer of control information. The power control can be used to resist the modification of

radio environment.

E-HICH transmit shall have enough power. The total DL interference decrease can

improve DL bit rate and capacity. The power level is decided by CQI measurement. The

algorithm is based on the current HS-SCCH power control principle.





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 ZWF25-05-001 QoS Mapping for HSUPA Service

Benefits

This feature implements QoS Mapping for HSUPA Service to support Node B scheduling

based on priorities of users and services, realizing different user experiences.

Description

ZTE RNC maps priorities of services and users assigned by RAB to HSUPA SPI

(Scheduling Priority Indicator). ZTE Node B supports SPI-based scheduling algorithm.

The higher SPI, the more chance and scheduled resource (Power Grant) the UE can get.

Therefore different user experiences are realized.

Introduced Version

U9.1&Before

Enhanced Function

No

6.1.31 ZWF25-05-002 HSUPA Nominal Bit Rate for I/B Service

Benefits





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 can’t 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 ZWF25-05-003 Directed Retry between E-DCH and DCH

Benefits

This feature establishes the service on proper carrier when R99 and HSUPA are

deployed on separated carriers.

Description

ZTE RAN system supports dedicated carrier configuration for R99 and HSDPA services.

For example, a cell can be set to be HSUPA dedicated and reject R99 service. Different

transport channels are suitable for different kinds of service. For example, CS service

needs dedicated DCH to guarantee real-time capability while high speed packet data

service should use E-DCH to make use of higher frequency efficiency.

If the network has multiple carriers and at least one of them is dedicated for HSUPA or

R99, it’s necessary to allocate radio resources to different carriers according to the

property of service. If the carrier that user accesses is not the carrier required by the

service, ZTE RAN system will trigger inter-frequency handover to directly switch the

service to the expected carrier. For example, a user initiates a CS session in an HSUPA

dedicated carrier, and RNC will directly try to switch it to the carrier supporting R99. Or a





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 ZWF25-05-004 HSUPA Flow Control

Benefits

This feature realizes the uplink data control mechanism between the RNC and the Node

B in order to avoid data loss due to Iub transmission congestion when the Node B

transmits too much data.

Description

When the peak rate of E-DCH channel is very high, if the transmission bandwidth

configured for the Iub interface is very small or the available transmission bandwidth

becomes smaller because of some transmission link trouble, the data transmission

becomes congested, and the data is disordered, discarded, or delayed. At the moment, it

is necessary to reduce the uplink transmitting traffic capacity that does not exceed the

uplink transmission bandwidth. This can avoid retransmission due to congestion and

reducing the transmission efficiency.

Additional, HSUPA user consumes more UL CE than R99 user. So there might be a

situation that baseband resource is out of use for lots of HSUPA users. When it happens,

Node B is able to perform flow control as well.

To HSUPA serving RL, Node B can completely and independently schedule UE UL data

rate when Iub bandwidth or CE is not enough. However, it’s not the same for non-serving

RL when HSUPA user is in macro-diversity status, which limits the direct control on UE

UL data transmission. Node B will send RL failure indication message to RNC including





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 Other HSUPA Related Functionality

6.2.1 ZWF25-01-024 HSUPA 2ms TTI & 5.76Mbps Peak Bit Rate

Benefits

This feature enables to use the E-DCH 2ms TTI to shorten the latency of uplink data

transmission and improve the uplink bit rate up to 5.76 Mbps for one cell. It is very

valuable for the user experience and the uplink throughput for a cell.

Description

ZTE RAN system supports 2ms TTI for HSUPA E-DCH channel. Compared to 10ms TTI,

2ms TTI has the following advantages:

− 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.


Benefits

This feature enables a cell to support 32 HSUPA users.

Description

ZTE RAN system supports channel allocation and packet scheduling for 32 HSUPA

users within a cell, so maximum 32 HSUPA users are simultaneously supported in one

cell.





Introduced Version

U9.1&Before

Enhanced Function

No


Benefits


Description



cell.

Introduced Version

U9.1&Before

Enhanced Function

No


Benefits


Description



cell.





Introduced Version

U9.1&Before

Enhanced Function

No

6.2.5 ZWF25-01-030 HSUPA 192 Users per cell

Benefits

This feature offers 192 HSUPA subscribers per cell simultaneously.

Description

Based on utilizing interference cancellation (MUD), ZTE RAN system supports channel

allocation and packet scheduling for 192 HSUPA users within a cell, thereby maximum

192 HSUPA users are simultaneously supported in one cell.

Introduced Version

UR11.1

Enhanced Function

No

6.2.6 ZWF25-02-011 SRB over HSUPA

Benefits

This feature enables RRC signaling and NAS signaling to be carried on E-DCH, which

significantly accelerates signaling process on Uu interface and reduces the latency of

subsequent service establishment.

Description

ZTE RAN system supports E-DCH can carry SRB. All SRBs are multiplexed to a

dedicated MAC-d Flow. RNC configures QoS parameters properly for SRB. ARP and





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

7 HSPA Evolution

7.1 R7 HSPA+

7.1.1 ZWF26-01-001 64QAM for HSDPA

Benefits

The HSDPA technology defined in the 3GPP R5 protocol introduces the downlink shared

channel HS-DSCH and the related physical layer processing. In an environment with

satisfactory wireless quality, the HS-DSCH channel can use the 16QAM high order

modulation, making the cell peak rate reach 14.4Mbps other than DCH channel, which

only can be modulated by QPSK. To further improve the downlink peak rate of a cell and

system frequency spectrum utilization efficiency, the HS-PDSCH channel can use

64QAM modulation mode in 3GPP R7.

Having used the 64QAM modulation, the 6 consecutive symbols in each group (including

nk, nk+1, nk+2, nk+3, nk+4, and nk+5) are converted into two branches (I and Q branches)

through serial-to-parallel conversion. In branch I, there are 3 consecutive symbols (i1= nk,

i2= nk+2, i3= nk+4); in branch Q, there are three consecutive symbols: q1= nk+1, q2= nk+3, q3=

nk+5. The symbols in branch I and Q can be mapped into 64 constellations through

modulation. The 16QAM modulation can process 4 consecutive symbols at a time.

Therefore, the modulation efficiency of the 64QAM increases by 50% in contrast to that





of 16QAM. Compared with the HS-DSCH in R5, the peak rate of a single user increases

by 50%, reaching 21.6Mbps.


U9.1&Before

Enhanced Function

No

7.1.2 ZWF26-01-003 HSDPA MIMO

Benefits

This feature provides 2x2 MIMO techniques in HSDPA, which will double spectrum

efficiency at most. For the same bandwidth, the system would improve about average bit

rate by 20% and peat bit rate by 100%. Single HSDPA user can reach 28.8Mbps peak bit

rate. It is a better choice for operators who want to improve system capacity but lack

spectrum or spectrum costs too much.

Description

In general, MIMO means the use of multiple antennae at transmitter and receiver side in

order to suppress channel fading. Through multi-antenna system, both system capacity

and spectrum efficiency can be improved without adding bandwidth or transmission

power. Moreover, it can also be beneficial to enhance channel reliability and reduce

BER.

In case of Tx diversity, the same data stream is transmitted by 2 antennae. However in

case of MIMO, pre-encoding is used for two independent data streams to decrease

correlation and reduce inter-antenna interference. After pre-encoding, two data streams

are transmitted in 2 antennae simultaneously. Each data steam is associated to an

antenna so as to double transmission bandwidth.





Figure 7-1 Basic Principle of 2×2 MIMO Technical Solution

Weight Generation

w 1 w 4

Determine weight info message from the uplink

w 2 w 3

TrCH processing

HS-DSCH TrCH processing

HS-DSCH

Spread/scramble

∑

Ant 1

Ant 2

∑

CPICH 1

CPICH 2

w 1

w 2

w 3

w 4

∑

∑

Primary transport block

Primary: Always present for scheduled UE

Secondary: Optionally present for scheduled UE

Secondary transport block

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 1w , 2w , 3w and 4w .

2/113 == ww

24 ww −=

−−+−−+

∈2

1,2

1,2

1,2

12

jjjjw

UE sends PCI (pre-coding index) to Node B according to channel state, and Node B

chooses corresponding 1w , 2w , 3w and 4w according to PCI.

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:

− Channel Quality Indicator (CQI) reported by the UE

− Pre-coding Control Indication (PCI)

− HS-PDSCH code resources and power resources of the Node B

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:





Figure 7-2 VAM Option with MIMO

Spread/scramble

HS-DSCH Trch processing

Primary transport block

HS-DSCH Trch processing

Secondary transport block

∑

∑

∑

W1

W2

W3

W4

Ant1

Ant2

∑

R99/HSU11

U21

Trch processing

VAMAnt1

Ant2

Spread/scramble

P-CPICH

f1

f2

R99/HS Trch processing

P-CPICH

Spread/scramble

+

U11

U21

VAM

U22

U12

+S-CPICH

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. This feature provides S-CPICH Power

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 UE’s 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 ZWF26-01-004 16QAM in HSUPA

Benefits

This feature supports HSUPA 16QAM high-order modulation. When UE uses the code

configuration of 2SF2+2SF4 and 16QAM technology, the cell peak rate can be up to

11.5Mbps. Relative to QPSK, 16QAM has the higher modulation gain to increase the cell

uplink capacity.

Description





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 ZWF26-01-010 Enhanced F-DPCH

Benefits

This feature provides enhanced F-DPCH function with a purpose to improve DL

channelized code utilization efficiency and increase cell capacity.

Description





F-DPCH is introduced to improve DL channelization code utilization efficiency, acting as

a substitute for A-DPCH. One F-DPCH can transmit TPC of up to 10 UEs per slot, which

is shown in Figure 33. Because of soft handover or softer handover, each UE probably

needs to receive F-DPCH signal from several cells. As a result, the average number of

UEs served by each F-DPCH is reduced. Moreover, F-DPCH is constrained with time

offset; therefore, all F-DPCHs received by one UE must have the same timing offset. If

another UE in the status of macro-diversity wants to use the same timing offset for the

same F-DPCH, confliction happens. In this case, the capacity of each F-DPCH is further

reduced. Assuming that 30% UEs are in the status of soft or softer handover, the

capacity of an F-DPCH goes down to 3 or 4 UEs per channel in reality.

Figure 7-3 F-DPCH Multiplexed

UE1UE2 UE3 UE10

UE1UE2 UE3... UE1 UE1

time1 slot

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.


U9.2

Enhanced Function

No





7.2 ZWF26-01-A CPC Package

7.2.1 ZWF26-01-005 HS-SCCH-less Operation

Benefits

This feature provides HS-SCCH-less Operation function. As it can reduce DL HS-SCCH

overhead, it can improve system capacity of DL real-time service, especially VoIP

service.

Description

In R5-based HSDPA, UE is supposed to continuously monitor HS-SCCH. As soon as the

UE detects relevant control information via a specific H-RNTI (HSDPA Radio Network

Temporary Identifier), it switches to the associated HS-PDSCH resources and receives

the data packet.

HS-SCCH-less Operation is introduced in R7, it means that the 1st HS-PDSCH

transmission is performed without accompanying HS-SCCH and UE is responsible for

blind detection when sending the predefined small transport blocks in predefined transfer

format. But the 1st or the 2nd HS-PDSCH retransmission is needed accompanying

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 ZWF26-01-006 New UL DPCCH Slot Format

Benefits

This feature provides new UL DPCCH slot format. In case of UEs without data

transmission, the new slot format is adopted, which can add TPC bits and reduce

DPCCH power. As a result, the UEs without data transmission can gain benefit of

reduced UL control channel interference. This is profitable not only to improve system UL

capacity, but also to reduce UE power consumption.

Description

The definition of DPCCH slot format in 3GPP R6 is suitable for UL data transmission. In

order to ensure decoding reliability, more pilot bits are occupied (8 bits). Upon adoption

of UL DTX, when there is no UL data transmission, continuous transmission of DPCCH is

suitable for data synchronization and power control. Later when there is data

transmission, the UL transmission can quickly restore to normal non-DTX transmission

status. In 3GPP R7, new UL slot format 4 is added. This slot format is introduced in order

to pursue balance between channel estimation and power control reliability. It contains

only 6 pilot bits and 4 TPC bits. Meanwhile, FBI and TFCI bits are absent. The advantage

of 4 TPC bits is that the reliability of power control is improved. This means DPCCH

transmission power can be reduced (DPCCH transmission power in R7 is reduced by

2~4dB than R6). Hence, the UEs without data transmission can gain benefit of reduced

UL control channel interference. This is lucrative not only to improve system UL capacity,

but also to reduce UE power consumption. This feature applies to CELL_DCH state.

Introduced Version

U9.2

Enhanced Function

No

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.





This mechanism is guaranteed by the parameters configured by RNC. This feature

applies to CELL_DCH state.

Introduced Version

U9.2

Enhanced Function

No

7.2.5 ZWF26-01-009 UL DRX in Node B

Benefits

This feature provides UL DRX function. With UL DRX enabled, the Node B shall perform

discontinuous E-DPCCH detection during the period of UL DRX, so the Node B

processing resources could be saved.

Description

In 3GPP Release 6, Node B must perform continuous E-DPCCH detection every slot.

But in 3GPP Release 7, with the introduction of UL DRX, the Node B shall perform

discontinuous E-DPCCH detection during the period of UL DRX, so the Node B

processing resources could be saved. UL DTX must be configured when the UL DRX is

enabled. This feature applies to CELL_DCH state.

Introduced Version

U9.2

Enhanced Function

No





7.3 ZWF26-01-B Enhanced Cell FACH Package

7.3.1 ZWF26-01-011 Enhanced DL CELL_FACH

Benefits

This feature can improve UTRAN and UE performance and efficiency for “always online”

services. In CELL_FACH state, using HSDPA for transferring data can increase peak

bitrate and decrease call delay, as a result, the user experience can be improved.

Description

The common H-RNTI, HS-SCCH and HS-DSCH configuration information are added to

system broadcast, then UE can use HSDPA resource of cell after reading cell broadcast.

In addition Enhanced DL CELL_FACH allows UE receive HS-DSCH data in CELL_FACH

states. Therefore HS-DSCH is regarded as universal channel, and can be used in

CELL_DCH and CELL_FACH states instead of CELL_DCH state only. For UE in

CELL_FACH state, UTRAN can send signaling and data of DCCH, CCCH, DTCH

through HS-DSCH. For UE in CELL_FACH state, UTRAN can send SYSTEM

INFORMATION CHANGE INDICATION message on BCCH through HS-DSCH.

The UE capability of supporting CELL_FACH enhancement is added, and reported to

UTRAN in the establishment of RRC connection. If UE supports the capability, HS-DSCH

reception shall take precedence instead of reception of S-CCPCH and FACH for

dedicated signalling data in CELL_FACH state..

Having using this feature, SRB bear on HSPA during the state transferring will reduce

transmission delay of control plane message. In addition he peak bitrate in CELL_FACH

increases because HS-DSCH can be used in CELL_FACH state, as a result, the channel

switching between CELL_FACH and CELL_DCH caused by burst data can be deduced

Introduced Version

UR11.1

Enhanced Function





No

7.3.2 ZWF26-02-003 Enhanced UL CELL_FACH

Benefits

This feature can reduce state transfer delay among URA_PCH, CELL_PCH,

CELL_FACH, 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 ZWF26-02-006 Enhanced UE DRX

Benefits

This feature provides a method of reducing UE power consumption and extending

battery life.

Description

Enhanced UE DRX function introduced in 3GPP R8 defines a discontinuous reception

method in CELL_FACH state, and it enables UE without data transferring enter into DRX

state firstly instead of entering PCH state directly, therefore it can reduce UE power

consumption and decrease signaling for UE to perform state transfer. When E-DCH

transmitting ends, the “inactivity timer” timer starts, UE will still be in continuous reception

before “inactivity timer” expires. If there is no data of E-DCH or HS-DSCH in the period

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.

Figure 7-4 Enhanced UE DRX

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 battery’s 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 ZWF26-02-005 CS over HSPA

Benefits

Benefiting from higher spectrum efficiency on HSPA than on Rel99 DCH, CS voice over

HSPA greatly improves the capacity of voice call per cell without network architecture

alternation in core network (such as introducing IMS), which is needed by VoIP.





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 user’s priority

is higher than the threshold, the CS AMR service will be beared on R99 channel. And if

the user’s priority is lower than the threshold, the CS AMR will be beared on HSPA

channel.

Introduced Version

U9.2

Enhanced Function

None





8 Abbreviation 16QAM 16 Quadrature Amplitude Modulation

AAL ATM Adaptation Layer

AAL2 ATM Adaptation Layer type 2

ABR Available Bit Rate

AC Access Class

ACK Acknowledgement

ACL Address Control List

A-DPCH Associated Dedicated Physical Channel

AICH Acquisition Indicator Channel Acquisition Indicator

Channel

AISG Antenna Interface Standards Group

AG Absolute Grant

AGPS Assisted Global Positioning System

ALCAP Access Link Control Application Protocol

AM Acknowledged Mode

AMC Adaptive Modulation and Coding

AMR Adaptive Multi Rate

AMR-WB Adaptive Multi-Rate Wide band

AMR-NB Adaptive Multi-Rate Narrow band

ANT Antenna





APS Active Protection System

ARP Allocation/Retention Priority

ARQ Automatic Repeat ReQuest

AS Access Stratum

ASC Access Service Class

ATM Asynchronous Transfer Mode

AWGN Additive White Gaussian Noise

BBU Base Band Unit

BER Bit Error Ratio

BFD Bidirectional Forwarding Detection

BITS Building Integrated Timing Supply System

BLER Block Error Ratio

BM-SC Broadcast Multicast Serving Center

BOOTP Bootstrap Protocol

BSC Base Station Controller

BSSMAP Base Station Subsystem Management Application Part

BTS Base Transceiver Station

CAC Call Admission Control

CBC Cell Broadcast Center

CBE Cell Broadcast Entity

CBR Constant Bit Rate





CBS Cell Broadcast Service

CC Continuity Check

CC Chase Combining

CCCH Common Control Channel

CCP Communication control ports

CDT Call Detail Trace

CE Channel Element

CN Core Network

COS Class of Service

CPC Continuous Packet Connectivity

CPEX Capital expenditure

CPICH Common Pilot Channel

CQI Channel Quality Indication

CS Circuit Switched

CSTM-1 Channelized STM-1

DCCH Dedicated Control Channel

DCH Dedicated Channel

DC-HSDPA Dual Cell HSDPA

DF Duplexer and Filter

DHCP Dynamic Host Configuration Protocol

DoS Denial of Service





DPCCH Dedicated Physical Control Channel

DPCH Dedicated Physical Channel

DPDCH Dedicated Physical Data Channel

DPT Dynamic Power Track

DRBC Dynamic Radio Bearer Control

DRNC Drifting RNC

DRT Delay Relative Time

DRX Discontinuous Reception

DSAR Domain Specific Access Restriction

DSCR Directed Signalling Connection Re-establishment

DTCH Dedicated Traffic Channel

DTM Dual Transfer Mode

DTX Discontinuous Transmission

EcN0 Received energy per chip divided by the power density in

the band

E-AGCH E-DCH Absolute Grant Channel

E-HICH E-DCH HARQ Acknowledgement Indicator Channel

E-DCH Enhanced Dedicated Channel

E-DPCCH E-DCH Dedicated Physical Control Channel

E-DPDCH E-DCH Dedicated Physical Data Channel

eNodeB E-UTRAN NodeB

EPD Early Packet Discard





E-RGCH E-DCH Relative Grant Channel

ETWS Earthquake and Tsunami Warning System

E-UTRAN Evolved Universal Terrestrial Radio Access Network

E-VAM Evolved VAM

EVC Ethernet Virtual Connection

FACH Forward Access Channel

F-DPCH Fractional Dedicated Physical Channel

FE Fast Ethernet

FEC Forward Error Correction

FIR Full Incremental Redundancy

FLC Frequency Layer Convergence

FLD Frequency Layer Dispersion

FP Frame Protocol

FSN Frame Sequence Number

GA Geographical Area

GBR Guarantee Bit Rate

GE Gigabit Ethernet

GGSN Gateway GPRS Support Node

GMGW Gated Media Gateway

GMSC Gateway MSC

GPS Global Positioning System





GERAN GSM EDGE Radio Access Network

GSM Global System for Mobile communications

GTP GPRS Tunneling Protocol

G/U GSM/UMTS

GWCN Gateway Core Network

HARQ Hybrid Automatic Repeat request

HCS Hierarchical Cell Structure

HLR Home Location Register

H-RNTI HSDPA Radio Network Temporary Identifier

HSDPA High Speed Downlink Packet Access

HS-DPCCH Dedicated Physical Control Channel (uplink) for HS-DSCH

HS-DSCH High Speed Downlink Shared Channel

HS-PDSCH High Speed Physical Downlink Shared Channel

HS-SCCH High Speed Physical Downlink Shared Control Channel

HSUPA High Speed Uplink Packet Access

IC Interference cancellation

IDNNS Intra Domain NAS Node Selector

IKE Internet Key Exchange

IMA Inverse Multiplexing over ATM

IMS IP Multimedia Subsystem

IMSI International Mobile Subscriber Identity





IPOA IP over ATM

IR Incremental Redundancy

KPI Key Performance Index

LA Location Area

LACP Link Aggregation Control Protocol

LCS Location Services

LMMSE Linear Minimum Mean Square Error

LMT Local Maintenance Terminal

LTE Long Term Evolution

M3UA MTP3 User Adaptation Layer

MAC Medium Access

MBMS Multimedia Broadcast Multicast Service

MBR Maximum Bit Rate

MCCH MBMS point-to-multipoint Control Channel

MCPPP Multi-Chasis PPP

MCS Modulation and Coding Scheme

MEP Maintenance End Point

MEG Maintenance Entity Group

MGW Media GateWay

MICH MBMS Indicator Channel

MIMO Multiple-Input Multiple-output





MLPPP Multilink-PPP

MME Mobile Management Entity

MMS Multimedia Messaging Service

MOCN Multi-Operator Core Network

MPC Multi Path Cancellation

MPO Measurement Power Offset

MR Measurement Report

MRR Measurement Report Record

MSC Mobile Switching Centre

MSCH MBMS point-to-multipoint Scheduling Channel

MSTP Multi-Service Transfer Platform

MTCH MBMS point-to-multipoint Traffic Channel

MTP3B Message Transfer Part level 3

MTU Maximum Transfer Unit

MUD Multi User Detection

NACC Network Assisted Cell Change

NACK Negative Acknowledgement

NAS Non-Access Stratum

NAT Network Address Translation

NBAP Node B Application Part

NBR Nominal Bit Rate





NCP Node B control port

N-ISDN Narrowband Integrated Services Digital Network

NITZ Network Identity and Time Zone

NNSF Network Node Selection Function

NRI Network Resource Identifier

NRT Non-Real Time

NTP Network Time Protocol

OAM Operation and Maintenance

OMC Operation and Maintenance Centre

OMCR Operation and Maintenance Centre of RNC

OPEX Operating expenses

OSPF Open Shortest Path First

OVSF Orthogonal Variable Spreading Factor

PA Power Amplifier

PCI Pre-coding Index

PDP Packet Data Protocol

PDU Protocol Data Unit

PF Proportional Fair

PHS Personal Handy phone System

PICH Paging Indicator Channel

PIR Partial Incremental Redundancy





PLMN Public Land Mobile Network

POS Packet over SONET/SDH

PPA Preferred Pool Area

PPD Partial Packet Discard

PPP Point-to-Point Protocol

PRACH Physical Random Access Channel

PS Packet Switched

PSTN Public Switched Telephone Network

PtM Point-to-Multipoint

PtP Point to Point

PVC Permanent Virtual Circuit

PWS Public Warning System

QAM Quadrature Amplitude Modulation

QoS Quality of Service

QPSK Quadrature (Quaternary) Phase Shift Keying

RA Routing Area

RAB Radio Access Bearer

RACH Random Access Channel

RAN Radio Access Network

RANAP Radio Access Network Application Part

RAT Radio Access Technology





RB Radio Bearer

RF Radio Frequency

RG Relative Grant

RL Radio Link

RLC Radio Link Control

ROHC Robust Header Compression

RR Radio Resources

RRC Radio Resource Control

RRM Radio Resource Management

RRU Radio Remote Unit

RNC Radio Network Controller

RNSAP Radio Network Subsystem Application Part

RSCP Received Signal Code Power

RSEPS Received Scheduled E-DCH Power Share

RSU Radio Sector Unit

RT Real-Time

RTCP Real-Time Transport Control Protocol

RTP Real Time Protocol

RTR RRU Transceiver

RTT Round-Trip Time

RTWP Received Total Wideband Power





SA Service Area

SAI Service Area Identifier

SABP Service Area Broadcast Protocol

SCCP Signalling Connection Control Part

SCCPCH Secondary Common Control Physical Channel

SCUDIF Service Change and UDI/RDI Fallback

SDH Synchronous Digital Hierarchy

SDP Session Description Protocol

SF Spreading Factor

SFN System Frame Number

SG Scheduling Grant

SGSN Serving GPRS Support Node

SIB System Information Block

SIP Session Initiation Protocol

SIR Signal-to-Interference Ratio

SLA Service Level Agreement

SMLC Service Mobile Location Center

SMS Short Message Service

SMS-CB SMS Cell Broadcast

SNA Shared Network Area

SNR Signal-to-noise ratio





SNTP Simple Network Time Protocol

SONET Synchronous Optical Networking

SPI Schedule Priority Indicator

SRB Signalling Radio Bearer

SRNC Serving Radio Network Controller

SRNS Serving RNS

SR-VCC Single Radio Voice Call Continuity

SSCF Service Specific Co-ordination Function

SSCOP Service Specific Connection Oriented Protocol

STM-1 Synchronous Transport Module Level 1

STTD Space Time Transmit Diversity

TB Transport Block

TC Traffic Class

TCP Transmission Control Protocol

TDM Time-division multiplexing

TFI Transport Format Indicator

TFO Tandem Free Operation

TFRC Transport Formation and Resources Combination

THP Traffic Handling Priority

TM Transparent Mode

TPC Transmit Power Control





TrCH Transport Channel

TrFO Transcoder Free Operation

TTI Transmission Time Interval

UBR Unspecified Bit Rate

UBR+ Unspecified Bit Rate Plus

UDI Unrestricted Digital Information

UE User Equipment

UEA 3G Encrypt Algorithm

UM Unacknowledged Mode

UMTS Universal Mobile Telecommunications System

URA User Registration Area

UTRAN Registration Area

USIM Universal Subscriber Identity Module

UTRAN UMTS Terrestrial Radio Access Network

VAM Virtual Antenna Mapping

VBR Variable Bit Rate

VC Virtual Circuit

VLAN Virtual Local Area Network

VoIP Voice over IP

VP Virtual Path

VSWR Voltage Standing Wave Ratio





WCDMA Wideband Code Division Multiple Access

WRR Weighted Round Robin




ZTE UTRAN UR11.1 Optional Feature Descriptiondocshare01.docshare.tips/files/30959/309597685.pdf ·...

Documents

Transcript of ZTE UTRAN UR11.1 Optional Feature Descriptiondocshare01.docshare.tips/files/30959/309597685.pdf ·...