enhanced f-dpch feature guide

7/25/2019 Enhanced F-DPCH Feature Guide

1/23

Enhanced F-DPCH

Feature Guide


2/23

Enhanced F-DPCH

ZTE Confidential Proprietary 1

Enhanced F-DPCHVersion Date Author Reviewer Revision History

V1.0 2013/12/24 Cai Yaofang

Ke Yazhu, Ma

Yongchao, Yang

Hong

First edition

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


3/23

Enhanced F-DPCH


TABLE OF CONTENTS

1

Feature Attributes ............................................................................................. 4

2

Overview ............................................................................................................ 4

2.1

Feature Introduction ............................................................................................. 4

2.1.1

ZWF26-01-010 Enhanced F-DPCH ..................................................................... 4

2.2 License Control .................................................................................................... 5

2.3

Correlation with Other Features ........................................................................... 6

3

Technical Description ....................................................................................... 6

3.1

ZWF26-01-010 Enhanced F-DPCH ..................................................................... 6

3.1.1

Frame Structure and Slot Format of an E-FDPCH ............................................... 7

3.1.2

Requirements for Utilization of the E-FDPCH ....................................................... 8

3.1.3

Multiplexing Method of the E-FDPCH................................................................... 9

3.1.4

Dynamic Radio Bearer Control for the E-FDPCH ................................................. 9

3.1.5

Code Resource Allocation for the E-FDPCH ...................................................... 11

3.1.6

Mobility Management for the E-FDPCH ............................................................. 11

4

Parameters and Configurations ..................................................................... 13

4.1

ZWF26-01-010 Enhanced F-DPCH ................................................................... 13

5

Related Counters and Alarms ........................................................................ 15

5.1

Related Counters ............................................................................................... 15

5.2

Related Alarms .................................................................................................. 15

6

Engineering Guide .......................................................................................... 16

6.1

Application Scenario .......................................................................................... 16

6.2

Feature Activation Procedure ............................................................................. 16

6.3

Feature Validation Procedure ............................................................................ 19

6.4

Feature Deactivation Procedure ......................................................................... 20

6.5

Network Impact .................................................................................................. 21

7

Abbreviation .................................................................................................... 21

8 References ....................................................................................................... 22


4/23

Enhanced F-DPCH


FIGURES

Figure 2-1 F-DPCH Multiplexed .......................................................................................... 5

Figure 6-1 Parameter Configuration Interface1 ...............................................................17





TABLES

Table 2-1 License Control List .............................................................................................5

Table 3-1 F-DPCH Fields (Copied from Table 16C: F-DPCH Fields in 25.211) ....................7

Table 5-1 Counter List ....................................................................................................... 15


5/23

Enhanced F-DPCH


1 Feature Attributes

RNC Version: [ZXWR RNC V3.13.10.15/ZXUR 9000 V4.13.10.15]

Node B Version: [ZXSDR V4.13.10.20]

Attribute: [Optional]

Involved NEs:

NE Name Related or Not Special Requirement

UE Enhanced F-DPCH should be supported by the

UEs.

Node B Enhanced F-DPCH should be supported by the

Node Bs.

RNC

iTC -

MSC -

MGW -

SGSN -

GGSN -

HLR -

: Involved, -: Not involved.

2 Overview

2.1 Feature Introduction

2.1.1 ZWF26-01-010 Enhanced F-DPCH

As a substitute for a downlink associated DPCCH, an F-DPCH is introduced to improve

DL channelization code utilization efficiency. One F-DPCH can transmit TPCs of up to 10

UEs per slot, see the following figure.


6/23

Enhanced F-DPCH


Figure 2-1 F-DPCH Multiplexed

Because of soft handover or softer handover, each UE probably needs to receive

F-DPCH signals from several cells. As a result, the average number of UEs served by

each F-DPCH is reduced. Moreover, the F-DPCH is constrained by a timing 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, conflict occurs. In this case, the capacity of each F-DPCH is further reduced.

Assuming that 30% of UEs are in the status of soft or softer handover, the capacity of an

F-DPCH is decreased to 3 or 4 UEs actually.

The enhanced F-DPCH feature has removed the restriction on F-DPCH timing offset, for

example, allow activating several F-DPCHs to use different timing offsets, which are

configured at the network side. This feature requires the UE to buffer a 1-bit TPC

command per slot.

Because the enhanced F-DPCH is introduced, the F-DPCH slot format defined in 3GPP

R6 is changed. Originally, the offset is a fixed value from the TPC field to the slot

boundary. After being changed, the offset is determined by one of the multiple F-DPCH

slot formats. Assuming that 30% of UEs are in the status of soft or softer handover, the

capacity of an enhanced F-DPCH is increased to 7 UEs actually.

2.2 License Control

Table 2-1 License Control List

Feature ID Feature NameLicense

Control Item

Configured

NE

Sales

Unit

ZWF26-01-010 WCDMA Enhanced

F-DPCH

Number of

cellsRNC Cell

UE1

UE2UE3

UE10UE1

UE2UE3

...

UE1 UE1

time1 slot


7/23

Enhanced F-DPCH


2.3 Correlation with Other Features

1. Required Features

ZWF23-01-A HSDPA Introduction Package

2. Mutually Exclusive Features

None

3. Affected Features

None

3 Technical Description

3.1 ZWF26-01-010 Enhanced F-DPCH

This feature is optional in 3GPP Rel-7. Because the slot formats for an F-DPCH areextended, there are 10 options for TPC position in one time slot at an F-DPCH frame

offset. Compared with the F-DPCH in 3GPP Rel-6, an E-FDPCH increases the

multiplexing opportunity for the UE during a soft handover, which saves downlink

channelization code resources.

For the basic principles of an F-DPCH, refer to the ZTE UMTS F-DPCH & SRB over

HSDPA Feature Guide.

For convenient description, the F-DPCH in this feature guide denotes a usual F-DPCH,and the E-FDPCH denotes an enhanced F-DPCH introduced in 3GPP Rel-7, that is, the

extended slot formats based on the F-DPCH in 3GPP Rel-6.

The differences between E-FDPCH and F-DPCH only reside in the multiplexing method,

dynamic radio bearer control and mobility management, while the same parts are not

described in this feature guide. For more details, refer to the ZTE UMTS F-DPCH & SRB

over HSDPA Feature Guide.


8/23

Enhanced F-DPCH


3.1.1 Frame Structure and Slot Format of an E-FDPCH

The frame structure of an E-FDPCH is the same as that of an F-DPCH, and is illustrated

in the following figure. The difference is the slot format.

Figure 3-1 Frame structure of an F-DPCH

In 3GPP Rel-6, a fixed slot format (Slot Format #0 in the following table) is used. In 3GPP

Rel-7, there are 10 slot formats. Each slot format corresponds to a different position of

the TPC field within an F-DPCH slot. Ten positions of 256 chips are denoted by Slot

Format #0#9. The exact number of bits of the OFF periods and the number of the TPC

field (NTPC) are described in the following table.

Table 3-1 F-DPCH Fields (Copied from Table 16C: F-DPCH Fields in 25.211)

Slot

Format

#i

Chann

el Bit

Rate

(kbps)

Channe

l

Symbol

Rate

(ksps)

SF Bits/

Slot

NOFF1

Bits/Slot

NTPC

Bits/Slot

NOFF2

Bits/Slot

0 3 1.5 256 20 2 2 16

1 3 1.5 256 20 4 2 14

2 3 1.5 256 20 6 2 12

3 3 1.5 256 20 8 2 10

4 3 1.5 256 20 10 2 8

5 3 1.5 256 20 12 2 6

6 3 1.5 256 20 14 2 4

7 3 1.5 256 20 16 2 2


9/23

Enhanced F-DPCH


Slot

Format

#i

Chann

el Bit

Rate

(kbps)

Channe

l

Symbol

Rate

(ksps)

SF Bits/

Slot

NOFF1

Bits/Slot

NTPC

Bits/Slot

NOFF2

Bits/Slot

8 3 1.5 256 20 18 2 0

9 3 1.5 256 20 0 2 18

Because the multiplexing is independent of each cell, the F-DPCH slot format is

configured by the CRNC. For Iur, the slot format is allocated by the DRNC and then

transfered to the SRNC. The UE during a soft hanover receives different slot formats

from different cells and combines multiple TPC commands about the same downlink slot

from the same radio link set.

3.1.2 Requirements for Utilization of the E-FDPCH

When the following conditions are met, the E-FDPCH can be enabled for the UE.

The parameter for the E-FDPCH on the RNC level (Uhspa.rncEfdpchSupInd) is set

to Supported.

The parameter for the E-FDPCH on the cell level (UUtranCellFDD.efdpchSupInd) is

set to Supported.

The Node B indicates that the cell supports the E-FDPCH through the F-DPCH Slot

Format Capability IE in the AUDIT RESPONSE message or other related

messages.

The UE indicates that it supports the E-FDPCH through the Enhanced F-DPCH

supported IE.

There is no DCH in the downlink.

Note:

If the conditions for utilizing the E-FDPCH are met and SRBs can be carried on HSDPA,

and if there is a service carried on HSUPA, the conditions for SRBs carried on HSUPA


10/23

Enhanced F-DPCH


should be also met, otherwise, SRBs cannot be carried on HSDPA and the E-FDPCH

cannot be used. For details, referto the ZTE UMTS SRB over HSUPA Feature Guide.

For an inter-RNC neighboring cell, the E-FDPCH capacity is configured by

UExternalUtranCellFDD.eFdpchSupInd.

3.1.3 Multiplexing Method of the E-FDPCH

For the cells and the UEs supporting the E-FDPCH, the multiplexing method of the

channelization code for the E-FDPCH is independent of the configured F-DPCH frame

offset, which means that the UEs with the same F-DPCH frame offset can use the same

channelization code in different slot formats. The RNC allocates an F-DPCH slot format

to each radio link through the Iub and the Uu interfaces.

Both Rel-6 UEs and Rel-7 UEs may exist in a cell supporting the E-FDPCH. In order to

allocate the same channelization code for the F-DPCH to UEs in these two versions, the

RNC allocates an idle TPC bit position first for Rel-6 UEs, and then detemines the

F-DPCH frame offset based on Slot Format #0 and the TPC bit position for the UE to

establish the first radio link.

3.1.4 Dynamic Radio Bearer Control for the E-FDPCH

The principle of dynamic radio bearer control for the E-FDPCH is almost the same as that

for the F-DPCH except for the parameters. Because the use of the F-DPCH is related to

SRBs, the signaling channel allocation in the RRC phase, and signaling channel

allocation in the RAB phase and Dynamic Channel Type Transfer are described as

follows.

3.1.4.1 Signaling Channel Allocation in the RRC Phase

If the following conditions are met in the RRC phase, the SRBs of the UE can be carried

on the HS-DSCH and there is an associated F-DPCH.

The conditions of using E-FDPCH are satisfied, refer to 3.1.2 Requirements for

Utilization of the E-FDPCH;


11/23

Enhanced F-DPCH


The URncFunction.InitRrcOnDchparameter is set to 7: Forced to HSPA or 8: Not

Forced,Using HSPA Signalling on CELL_DCH state.

If either of the above conditions is not met or the SRB fails to be established on HSPA,

the RNC attempts to establish SRBs on the DCH at the rate of 3.4 kbps.

3.1.4.2 Signaling Channel Allocation in the RAB Phase

If the SRB is established on the DCH in the RRC phase, and if the following conditions

are met in the RAB phase, the SRBs of the UE in the RAB phase can be carried on the

HS-DSCH and there is an associated F-DPCH.

The conditions of using E-FDPCH are satisfied, refer to 3.1.2 Requirements for

Utilization of the E-FDPCH;

If the UHspa.Event1fHsInd parameter is set to 1: True and event 1F is configured

to the UE (that is, the measurement control message of event 1F is sent to the UE),

event 1F is not triggered; otherwise, event 1F does not need to be considered.

For the other scenarios of HS-DSCH serving cell change (including intra-frequency

and inter-frequency), transition from non HS-DSCH to HS-DSCH triggered by thetraffic volume in a cell, or relocation into the RNC, the conditions for E-FDPCH usage

are the same as those for signaling channel allocation in the RAB phase.

Note:

Event 1f indicates that the quality of a primary CPICH becomes worse than an absolute

threshold during a specified period. For details, refer to the ZTE UMTS Handover Control

Feature Guide.

3.1.4.3 Dynamic Channel Type Transfer for the E-FDPCH

The principles of dynamic channel type transfer for the E-FDPCH are the same as those

for the F-DPCH. For details, refer to the ZTE UMTS F-DPCH & SRB over HSDPA

Feature Guide.


12/23

Enhanced F-DPCH


3.1.5 Code Resource Allocation for the E-FDPCH

Code resource allocation for the E-FDPCH is only related to channelization code

allocation and scrambling code allocation for a new established F-DPCH. The allocation

method is the same as that for the F-DPCH. For details, refer to the ZTE UMTS F-DPCH

& SRB over HSDPA Feature Guide.

3.1.6 Mobility Management for the E-FDPCH

A cell supporting the E-FDPCH and a cell only supporting the F-DPCH may be adjacent

cells, but the F-DPCH multiplexing method in each cell is independent, so the two kinds

of cells can be in the same active set.

If a UE supports the E-FDPCH, then the following situation may occur: Cell 1 in the active

set allocates the F-DPCH based on the method in Rel-6 and cell 2 in the active set

allocates the F-DPCH based on the method in Rel-7.

When the serving HS-DSCH cell changes, if the F-DPCH/E-FDPCH is used in the source

cell, but the conditions to use the F-DPCH/E-FDPCH are not met in the target cell, the

transition from F-DPCH to DPCH will be triggered.

When the serving HS-DSCH cell changes, if DPCH is used in the source cell, and the

conditions to use F-DPCH/E-FDPCH is met in all the cells in the active set, the transition

from a DPCH to an F-DPCH will be triggered.

During a hard handover or relocation into the RNC, if the target cell meets the conditions

to use the E-FDPCH, an F-DPCH is allocated.

Note:

For the conditions to use the E-FDPCH, refer to3.1.4.2 Signaling Channel Allocation in

the RAB.For mobility management for the F-DPCH, refer to the ZTE UMTS F-DPCH &

SRB over HSDPA Feature Guide.

Because the F-DPCH Slot Format Support Request IE cannot be carried in the Radio link

addition message across the Iur interface, the F-DPCH cell and the E-FDPCH cell

crossing the Iur interface cannot stay in an active set if the UE is using the E-FDPCH.

The following rules are used:


13/23

Enhanced F-DPCH


If all the neighboring cells of the DRNC configured on the SRNC support the

E-FDPCH, the SRNC sends the F-DPCH Slot Format Support Request IE to the

DRNC through the Radio Link Setup Request message or the Radio Link

Reconfiguration Preparation message. And then the SRNC sends the F-DPCH slot

format fed back by the DRNC to the UE.

If not all the neighboring cells of the DRNC configured on the SRNC support the

E-FDPCH, the SRNC does not send the F-DPCH Slot Format Support Request IE,

and all the neighboring cells of the DRNC are regarded as cells with the F-DPCH.

If there is a radio link on the DRNC which is using the E-FDPCH, and if a new radio

link to be added on the DRNC does not support the E-FDPCH, the cell cannot be

added to the active set.

If there is a radio link on the DRNC which is using the F-DPCH, and if a new radio

link to be added does not support the E-FDPCH, the radio link can only use the

F-DPCH.

If the E-FDPCH is used by the UE, and if a new radio link to be added supports

neither the E-FDPCH nor the F-DPCH, the cell cannot be added to the active set.

For a neighboring cell of the DRNC which is not configured on the SRNC, if the

value of the cells F-DPCH Support Indicator in Cell Capability Container FDD

fed back through the Iur interface is Support, the cell is regarded as a cell which

supports the F-DPCH; otherwise, the cell is regarded as a cell which does not

support the F-DPCH. If the value of the cells F-DPCH Slot Format Support

Indicator in Cell Capability Container FDD fed back through the Iur interface is

Support, the cell is regarded as a cell which supports the E-FDPCH; otherwise,

the cell is regarded as a cell which does not support the E-FDPCH.


14/23

Enhanced F-DPCH


4 Parameters and Configurations

4.1 ZWF26-01-010 Enhanced F-DPCH

Table 4-1 Parameter List

Parameter

NameGUI Name

Parameter

DescriptionRange

Un

itDefault

Recommend

ation

UHspa.rncEfdpchSupInd

RNC Enhanced

F-DPCHSupport

Indicator

This parameter

indicates whether

the RNC supports

the Enhanced

F-DPCH or not.

0: Not

Supported1:

Supported

N/A

0: Not

Support

ed

1: Supported

UUtranCellFD

D.efdpchSupI

nd

Cell Enhanced

F-DPCH

Support

Indicator

This parameter

indicates whether

the cell supports

Enhanced F-DPCH

or not.

0: Not

Supported

1:

Supported

N/

A

0: Not

Support

ed

1: Supported

UExternalUtra

nCellFDD.eFd

pchSupInd

Neighboring

Cell Enhanced

F-DPCH

Support

Indicator

This parameter

indicates whether

the neighboring cell

supports Enhanced

F-DPCH.

0:Supported

1: Not

Supported

N/

A

1: Not

Support

ed

0: Supported

UHspa.event1

fHsInd

Indicator for

Whether to

Judge Event 1F

Condition When

the Service is

Setup on HSPA

This parameter

indicates whether to

udge event 1F

condition when the

service is setup on

HSPA.

0: False

1: True

N/

A0: False0: False


15/23

Enhanced F-DPCH


URncFunction

.initRrcOnDch

Type of

Transport

Channel for

Initial RRC

Connection

Setup

This parameter

indicates the type of

transport channel

and signaling rate

for initial RRC

connection setup.

0: Forced

to

CELL_DC

H and

Using

DCH/DCH

Low Rate

Signalling

1: Forced

to

CELL_DC

H and

Using

DCH/DCH

with 13.6k

Signalling

2: Forced

to FACH

3: Not

Forced,

Using

DCH/DCH

with

DCH/DCH

Low Rate

Signalling

on

Cell_DCH

State

4: Not

Forced,

Using

DCH/DCH

with 13.6k

Signalling

on

Cell_DCH

State

5: Forced

to

CELL_DC

H and

Using

DCH/DCH

with 27.2k

Signalling

6: Not

Forced

N/

A

Forced

to

CELL_D

CH and

Using

DCH/D

CH with

13.6k

Signallin

g

Forced to

CELL_DCH

and Using

DCH/DCH

with 13.6k

Signalling


16/23

Enhanced F-DPCH


5 Related Counters and Alarms

5.1 Related Counters

Table 5-1 Counter List

Counter No. Description

C310424276 Summation Number of Code Node Used, SF=256

C310424283~C31042

4314

Distribution Of Code Node Occupied, SF=256

C310032024 Number of E-FDPCH users in the best cell

C310032025 Average Number of E-FDPCH users in the best cell

C310032028 Number of E-FDPCH users in the non best cell

C310032029

Average Number of E-FDPCH users in the non best cell

C310032022 Number of F-DPCH users in the best cell

C310032023 Average Number of F-DPCH users in the best cell

C310032026 Number of F-DPCH users in the non best cell

C310032027 Average Number of F-DPCH users in the non best cell

C310030436 Number of including only HSDPA users in the best cell

C310030448 Max Number of including only HSDPA users in the best cell

C310030460 Average Number of including only HSDPA users in the best

cell

5.2 Related Alarms

This feature has no related alarm.


17/23

Enhanced F-DPCH


6 Engineering Guide

6.1 Application Scenario

1. Scenarios for Enabling the E-FDPCH

One F-DPCH can be used by up to 10 users in time-multiplex mode and downlink

channelization code resources are saved, especially after the E-FDPCH is introduced in

3GPP Rel-7, the code utilization during a soft handover is improved. As a result of the

code saving on the F-DPCH, the number of HS-DPSCHs is increased, and the average

throughput and the user experience are improved. So it is recommended to activate this

feature after HSDPA is deployed. The E-FDPCH feature developed by ZTE is compatible

with the UEs supporting the F-DPCH in Rel-6.

2. Precautions for Enabling the E-FDPCH

Because there may be compatibility issues from some UEs, it is recommended to

activate this feature in several cells first. If it is confirmed that there is no UE with

compatibility issues, this feature can be activated in the entire network, otherwise it

cannot be deployed in the network.

6.2 Feature Activation Procedure

The procedure describes how to find the GUI location of the parameters that are related

to the deployment of this feature. The values indicated by the captures may be not the

real value to be configured. For the real configuration value, refer to the last column of

the table in chapter 4.

In the configuration resource tree, select Modify Area > Managed Element > UMTS

Logical Function Configuration> External Resource Configuration> External RNC

Functionand double-click External UTRAN Cell, and set Neighboring Cell Enhanced

F-DPCH Support Indicator, seeFigure 6-1.


18/23

Enhanced F-DPCH


Figure 6-1 Parameter Configuration Interface1


Logical Function Configuration > Service configuration and double-click Hspa

Configuration, and set RNC Enhanced F-DPCH Support Indicatorand Indicator for

Whether to Judge Event 1F Condition When the Service is Setup on HSPA, see

Figure 6-2 andFigure 6-3.


19/23

Enhanced F-DPCH





Logical Function Configurationand double-click UTRAN Cell, and set Cell Enhanced

F-DPCH Support Indicator, seeFigure 6-4.


20/23

Enhanced F-DPCH



In the configuration resource tree, select Modify Area > Managed Element and

double-click UMTS Logical Function Configuration, and set Type of Transport

Channel for Initial RRC Connection Setup, seeFigure 6-5.


6.3 Feature Validation Procedure

Table 6-1 Feature Validation Procedure

Test Item Enhanced F-DPCH


21/23

Enhanced F-DPCH


Test Item Enhanced F-DPCH

Prerequisit

e

1. The WCDMA system is ready.

2. Cell1 supports HSUPA, HSDPA and DCH.

3. UE1 supports enhanced F-DPCH and resides in Cell1 in Idle mode.

4. The Enhanced F-DPCH feature is enabled.

Steps

1. Use UE1 to activate a PS call in Cell1.

2. Start FTP downloading.

3. Stop FTP downloading and release the call.

Expected

Result

1. The PS call is setup successfully after step 1.

2. The RNC configures SRBs on HS and indicates the slot format in the Radio

Bearer Setup message. The following IE should be present:

fdpch_SlotFormatPresent = 1

fdpch_SlotFormat = 0..9

3. Data transfer is normal after step 2.

4. The call is released normally after step 3.

6.4 Feature Deactivation Procedure

Table 6-2 RNC Parameter List2

Managed Object. Logic

Name

GUI NameDefault

Value

Deactivation

Value

UHspa.rncEfdpchSupInd

RNC Enhanced

F-DPCH Support

Indicator

0: Off 0: Off

UUtranCellFDD.efdpchSupInd

Cell Enhanced

F-DPCH Support

Indicator

0: Off 0: Off

For a description and configuration of the above parameters, refer to 6.2 Feature

Activation Procedure.


22/23

Enhanced F-DPCH


6.5 Network Impact

1. Equipment Performance

None

2. Network KPI

Activating this feature, the advantage is:

Because of the restriction that the TPC from different cells for a given UE must have the

same offset timing during a soft handover is removed for the E-FDPCH, the multiplexing

of code resources increases, more downlink channelization codes are saved, and the

average throughput and the user experience are improved.

The possible disadvantages are as follows:

Because the downlink Pilot of DPCCH is removed and the mechanism for the

reliability of TPC commands between the F-DPCH and the DPCH is different, and

the UE combines the different slot formats for TPC, the RTWP may be raised.

Because there are compatibility issues from some UEs, the following KPIs may be

deteriorated: CS RAB setup success rate (caused by concurrent PS services and

CS services with the PS services set up first), PS RAB setup success rate, and PS

call drop rate.

7 AbbreviationAbbreviation Full Name

DPCCH Dedicated Physical Control Channel

E-FDPCH Enhanced Fractional Dedicated Physical Channel

F-DPCH Fractional Dedicated Physical Channel

P-CPICH Primary CPICH

SRB Signaling Radio Bearer


23/23

Enhanced F-DPCH

8 References

[1] R1-062672

[2] ZTE UMTS F-DPCH & SRB over HSDPA Feature Guide

[3] ZTE UMTS Code Resource Allocation Feature Guide

[4] ZTE UMTS Handover Control Feature Guide

[5] ZXUR 9000 UMTS(V4.13.10.15)Radio Network Controller Radio Parameter

Reference

[6] ZXUR 9000 UMTS(V4.13.10.15)Radio Network Controller Ground Parameter

Reference

[7] ZXUR 9000 UMTS(V4.13.10.15)Radio Network Controller Performance Counter

Reference

[8] ZXWR RNC(V3.13.10.15)Radio Network Controller Radio Parameter Reference

[9] ZXWR RNC(V3.13.10.15)Radio Network Controller Ground Parameter Reference

[10] ZXWR RNC(V3.13.10.15)Radio Network Controller Performance Counter Reference

enhanced f-dpch feature guide

Documents