Radio Bearers(RAN13 0_01)
Radio Bearers(RAN13 0_01)
Radio Bearers(RAN13 0_01)
RAN13.0
Feature Parameter Description
Issue 01
Date 2011-04-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.
Email: support@huawei.com
WCDMA RAN
Radio Bearers Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience ........................................................................................................................ 1-1
1.3 Change History.............................................................................................................................. 1-1
7 Parameters .................................................................................................................................7-1
8 Counters ......................................................................................................................................7-1
9 Glossary ......................................................................................................................................9-1
10 Reference Documents .........................................................................................................10-1
1 Introduction
1.1 Scope
This document describes the radio bearers feature and related functions. It covers the logical channel
management, transport channel management, physical channel management and the HSPA+ feature
selection, and furthermore provides parameters associated with this feature.
Document Issues
The document issues are as follows:
01 (2011-04-30)
Draft B (2011-03-30)
Draft A (2010-12-30)
01 (2011-04-30)
This is the document for the first commercial release of RAN13.0.
Compared with issue Draft B (2011-03-30) of RAN13.0, this issue has no change.
Draft B (2011-03-30)
This is the draft of the document for RAN13.0.
Compared with Draft A (2010-12-30) of RAN13.0, this issue optimizes the description.
Draft A (2010-12-30)
This is the draft of the document for RAN13.0.
Compared with issue 01 (2010-03-30) of RAN12.0, this issue incorporates the changes described in the
following table.
RAN13.0 supports the feature WRFD-010510 3.4/6.8/13.6/27.2 kbit/s RRC Connection and RAB
Assignment. The RNC will map the RRC connection request and the RAB assigned by the CN according
to different QoS requirements.
Mapping of channel types
For RRC connection, the operators can decide which channel type (CCH/DCH) should be configured
according to the RRC SETUP REQUEST message. For detailed information about the channel
selection, see 5 "Transport Channel Selection."
For RAB assignment, the operators can decide in which cell the RAB should be set up. For detailed
information, see section RAB DRD in the Directed Retry Decision Feature Parameter Description.
Mapping of RAB parameters
The associated transport channel and physical channel parameters are configured based on the
channel types. Huawei RAN provides different sets of configuration parameters for typical services.
These parameters are supported by each typical service. If no traffic class matches the feature, the
most approximate parameters are selected. For detailed information about the RAB parameters for
typical services, see 3.2 "TRB Specifications."
The PS streaming/interactive/background RAB can also be set up on the HS-DSCH or E-DCH. For
detailed information about mapping rules, see 5 "Transport Channel Selection."
SRB always occupies SF256 at the rate of 3.4 kbit/s or 6.8 kbit/s. It can increase the signaling
transmission speed and shorten the delay at the rate of 6.8 kbit/s. Therefore, if all the downlink services
of the UE are set up on the HS-DSCH and the downlink SRB is carried on the DCH, the SRB works at a
rate of 6.8 kbit/s.
Traffic Class
There are four traffic classes: conversational, streaming, interactive, and background. The main
difference between these classes is the degree of delay sensitivity, which is described as follows:
The conversational class is the most sensitive to delay. It is used to carry real-time traffic. The
real-time traffic requires shortest delay and strict time sequence between data streams. Therefore, this
traffic class has the highest QoS requirement.
The streaming class is used to carry unidirectional data streams. It does not have a high requirement
for delay, but the time sequence must be kept within a data stream and the end-to-end delay jitter of
data streams must be controlled.
The interactive class is used to carry traditional Internet services, such as Web browsing and database
query. Its round trip time (RTT) is a key parameter, and data packets need to be transmitted
transparently at low bit error rates.
The background class is used to receive or transmit data in background mode. Such services include
email, SMS, and FTP. This class does not have a high requirement for delay, but it requires data
packets to be transmitted transparently at low bit error rates.
TRB Specifications
The RNC automatically checks the identity of the CN domain that provides the services. The RAB
ASSIGNMENT REQUEST message received from the CN contains information of traffic class, source
statistics descriptor, and MBR.
Table 3-2 lists the TRB specifications supported by Huawei RNC.
Table 3-2 TRB specifications
RAB Index CN Domain Traffic Class Source Statistics MBR (kbit/s) Direction
Descriptor
0 CS Conversational Speech 12.2 DL/UL
1 CS Conversational Speech 23.85 DL/UL
2 CS Conversational Unknown 28.8 DL/UL
3 CS Conversational Unknown 32 DL/UL
4 CS Conversational Unknown 56 DL/UL
5 CS Conversational Unknown 64 DL/UL
6 CS Streaming Unknown 57.6 DL/UL
11 PS Conversational Unknown 8 DL/UL
12 PS Conversational Unknown 16 DL/UL
13 PS Conversational Unknown 32 DL/UL
15 PS Conversational Unknown 64 DL/UL
16 PS Conversational Unknown 38.8 DL/UL
17 PS Conversational Unknown 39.2 DL/UL
18 PS Conversational Unknown 40 DL/UL
19 PS Conversational Unknown 42.8 DL/UL
21 PS Streaming Unknown 8 DL/UL
22 PS Streaming Unknown 16 DL/UL
23 PS Streaming Unknown 32 DL/UL
24 PS Streaming Unknown 64 DL/UL
25 PS Streaming Unknown 128 DL/UL
26 PS Streaming Unknown 144 DL/UL
27 PS Streaming Unknown 256 DL/UL
28 PS Streaming Unknown 384 DL/UL
40 PS Interactive Unknown 0 DL/UL
41 PS Interactive Unknown 8 DL/UL
RAB Index CN Domain Traffic Class Source Statistics MBR (kbit/s) Direction
Descriptor
42 PS Interactive Unknown 16 DL/UL
43 PS Interactive Unknown 32 DL/UL
44 PS Interactive Unknown 64 DL/UL
45 PS Interactive Unknown 128 DL/UL
46 PS Interactive Unknown 144 DL/UL
47 PS Interactive Unknown 256 DL/UL
48 PS Interactive Unknown 384 DL/UL
49 PS Interactive Unknown 608 UL
50 PS Interactive Unknown 768 DL
51 PS Interactive Unknown 1024 DL
52 PS Interactive Unknown 1280 UL
53 PS Interactive Unknown 1536 DL
54 PS Interactive Unknown 1800 DL
55 PS Interactive Unknown 2048 DL/UL
56 PS Interactive Unknown 2720 UL
57 PS Interactive Unknown 3600 DL
58 PS Interactive Unknown 5440 UL
59 PS Interactive Unknown 7200 DL
60 PS Interactive Unknown 10100 DL
61 PS Interactive Unknown 13900 DL
62 PS Interactive Unknown 21000 DL
63 PS Interactive Unknown 27900 DL
64 PS Interactive Unknown 35200 DL
65 PS Interactive Unknown 42100 DL
66 PS Interactive Unknown 11480 UL
67 PS Interactive Unknown 512 DL
68 PS Interactive Unknown 8640 DL
69 PS Interactive Unknown 16000 DL
100 PS Interactive Unknown 48900 DL
102 PS Interactive Unknown 56000 DL
RAB Index CN Domain Traffic Class Source Statistics MBR (kbit/s) Direction
Descriptor
104 PS Interactive Unknown 63000 DL
106 PS Interactive Unknown 69900 DL
108 PS Interactive Unknown 77000 DL
110 PS Interactive Unknown 84200 DL
70 PS Background Unknown 0 DL/UL
71 PS Background Unknown 8 DL/UL
72 PS Background Unknown 16 DL/UL
73 PS Background Unknown 32 DL/UL
74 PS Background Unknown 64 DL/UL
75 PS Background Unknown 128 DL/UL
76 PS Background Unknown 144 DL/UL
77 PS Background Unknown 256 DL/UL
78 PS Background Unknown 384 DL/UL
79 PS Background Unknown 608 UL
80 PS Background Unknown 768 DL
81 PS Background Unknown 1024 DL
82 PS Background Unknown 1280 UL
83 PS Background Unknown 1536 DL
84 PS Background Unknown 1800 DL
85 PS Background Unknown 2048 DL/UL
86 PS Background Unknown 2720 UL
87 PS Background Unknown 3600 DL
88 PS Background Unknown 5440 UL
89 PS Background Unknown 7200 DL
90 PS Background Unknown 10100 DL
91 PS Background Unknown 13900 DL
92 PS Background Unknown 21000 DL
93 PS Background Unknown 27900 DL
94 PS Background Unknown 35200 DL
95 PS Background Unknown 42100 DL
RAB Index CN Domain Traffic Class Source Statistics MBR (kbit/s) Direction
Descriptor
96 PS Background Unknown 11480 UL
97 PS Background Unknown 512 DL
98 PS Background Unknown 8640 DL
99 PS Background Unknown 16000 DL
101 PS Background Unknown 48900 DL
103 PS Background Unknown 56000 DL
105 PS Background Unknown 63000 DL
107 PS Background Unknown 69900 DL
109 PS Background Unknown 77000 DL
111 PS Background Unknown 84200 DL
In Table 3-2, the CS speech service defined by RAB Index 0 is known as Adaptive
Multi-Rate-Narrowband (AMR-NB) service; the CS speech service defined by RAB Index 1 is Adaptive
Multi-Rate-Wideband (AMR-WB) service.
AMR services are 3G speech services. For AMR services, the codec rates can be adjusted according to
the change of radio environments to achieve better speech quality. AMR services are classified into
AMR-NB services and AMR-WB services. Their codec rates are as follows:
AMR-NB services have eight codec rates: 4.75 kbit/s, 5.15 kbit/s, 5.9 kbit/s, 6.7 kbit/s, 7.4 kbit/s, 7.95
kbit/s, 10.2 kbit/s, and 12.2 kbit/s.
AMR-WB services have nine codec rates: 6.6 kbit/s, 8.85 kbit/s, 12.65 kbit/s, 14.25 kbit/s, 15.85 kbit/s,
18.25 kbit/s, 19.85 kbit/s, 23.05 kbit/s, and 23.85 kbit/s.
The voice sampling frequency and bandwidth of AMR-WB services are higher than those of AMR-NB
services. Compared with AMR-NB services, AMR-WB services provide better speech quality. For
detailed information about AMR service, see AMR Feature Parameter Description.
In a cell, a maximum of 16 MBMS channels are supported at the same time. The maximum MBMS
throughput is 1,792 kbit/s. That is, a x 256 kbit/s + b x 128 kbit/s + c x 64 kbit/s + d x 32 kbit/s + e x 16
kbit/s < 1,792 kbit/s, where a + b + c + d + e <= 16.
An RNC supports a maximum throughput of 8,192 kbit/s of the MBMS channels on the Iu interface, and
a maximum number of 256 MBMS channels at the same time.
When multiple logical channels are mapped onto one transport channel, these logical channels need to
be assigned different priorities. Typically, logical channel priorities need to be set only for the DCCH and
DTCH.
The logical channel priority is set based on the type of the logical channel and the service that the logical
channel carries. Each service corresponds to a logical channel priority.
To improve the user experience, the logical channel priority is set according to the following rule:
Signaling > CS service > PS conversational and streaming services > PS interactive service > PS
background service
The value of logical channel priority ranges from 1 to 8. The value 1 corresponds to the highest priority.
Similar information is carried between SIB4 and SIB3, between SIB6 and SIB5, and betweenSIB12 and
SIB11. In idle mode, the UE reads the system information from SIB3, SIB5, and SIB11. In connected
mode, the UE reads the system information from SIB4, SIB6, and SIB12.
For more detailed information about the preceding physical channels, see 3GPP TS 25.211.
The BCCH, CCCH logical channel can be mapped onto HS-DSCH transport channel only when the UE is in the enhanced
CELL_FACH. For detailed information about the enhanced CELL_FACH state, see the HSPA Evolution Feature
Parameter Description.
As shown in Table 5-1, interactive and background services on HSDPA, streaming services on HSDPA,
interactive and background services on HSUPA, streaming services on HSUPA are implemented. For
detailed information about mapping rules, see the following sections.
− In
the uplink, if SrbChlTypeRrcEffectFlag is set to TRUE and SrbChlType is set to HSUPA or HSPA,
the SRB is carried on the E-DCH; otherwise, the SRB is carried on the DCH.
During TRB connection setup, the SRB is carried on the CCH, DCH, HS-DSCH, or E-DCH, which is
described as follows:
If the selected channel type is FACH, the SRB is carried on the CCH in both the uplink and the
downlink.
If the selected channel type is DCH/E-DCH/HS-DSCH, then
− In
the downlink, if the channels selected by all the TRBs are HS-DSCH and SrbChlType is set to
HSDPA or HSPA, the SRB is carried on the HS-DSCH; otherwise, the SRB is carried on the DCH.
− In
the uplink, if the channel types selected by all the TRBs are E-DCH and SrbChlType is set to
HSUPA or HSPA, the SRB is carried on the E-DCH; otherwise, the SRB is carried on the DCH.
If both the UE and the cell support HSPA but the SRB fails to be set up on the HSPA channel (for
example, an admission failure occurs), the SRB is set up on the DCH. At the same time, the retry timer is
started for periodic retries to set up the SRB on the HSPA channel. The length of the retry timer is
specified by ChannelRetryTimerLen.
− If
the maximum UL service rate is higher than or equal to UlBeTraffThsOnHsupa, the service is
carried on the E-DCH; otherwise, the service is carried on the DCH.
For the first PS BE service, if DraSwitch: DRA_BASE_COVER_HSUPA_DCH_SELECT_SWITCH is set
to ON and the E-DCH is selected for the uplink, the RNC will further determines the coverage of the UE. If the
UE has weak coverage, the DCH is selected to reduce the call drop rate.
The RNC determines the signal quality of the UE based on the P-CPICH Ec/No value indicated in the
RRC CONNECTION REQUEST message during the RRC setup.
If the Ec/No value is within the valid range, that is, the timer EcN0EffectTime has not expired, and the
Ec/No value is below the threshold which can be specified by the parameter ReservedU32Para0, the
signal quality is considered poor and the UE has weak coverage. In this case, the RNC selects the
DCH for the BE service. If the Ec/No value is above the threshold, the RNC selects the E-DCH for the
BE service.
If the Ec/No value exceeds the valid range, that is, the timer EcN0EffectTime has expired, the RNC
will directly set up BE services on the E-DCH without considering the Ec/No value.The IMS signaling
can be carried on the DCH, HS-DSCH, or E-DCH.
In the downlink, if ImsChlType is set to HSDPA or HSPA, the IMS signaling is carried on the
HS-DSCH. Otherwise, the IMS signaling is carried on the DCH.
In the uplink, if ImsChlType is set to HSPA, the IMS signaling is carried on the E-DCH. Otherwise, the
IMS signaling is carried on the DCH.
If both the cell and the UE support HSPA but a service fails to be set up on the HSPA channel (for
example, an admission failure occurs), the service is carried on the DCH. At the same time, the retry
timer is started for periodic retries to access the HSPA channel. The timer length is specified by
ChannelRetryTimerLen. If an HSUPA service is set up on the DCH because of weak coverage, it will
not start periodic retries but directly switch to the E-DCH when the uplink coverage improves and traffic
volume increases.
HSPA+ features are selected for UEs in the CELL_DCH state only. The following HSPA+ features can be selected for UEs
in the CELL_FACH, CELL_PCH, or URA_PCH at the first step:
Downlink Enhanced CELL_FACH
Uplink Enhanced CELL_FACH
Enhanced DRX
This section describes only the first step (step 1) of how to determine whether a service can support
HSPA+ features, also known as HSPA+ radio bearer policy. For detailed information about the second
step (step 2), see the Directed Retry Decision Feature Parameter Description.
The HSPA+ radio bearer policy considers the following factors:
HSPA+ features selected for different services. For detailed information, see 6.2 "HSPA+ Feature
Selection for Different Services."
Parameters for configuring HSPA+ features. For detailed information, see 6.3 "HSPA+ Feature
Activation."
HSPA+ feature requirements for service attributes. For detailed information, see 6.4 "HSPA+ Radio
Bearer Policies."
Generally, a single SRB is not carried over HSPA+, but the SRB for a service over HSPA+ can be
configured with an HSPA+ feature. IMS is not applied to any HSPA+ features.
The PS interactive service and PS background service use the same radio bearer policy, which are
collectively referred to as PS BE services.
For details about activating HSPA+ features, see the RAN Reconfiguration Guide.
As defined in 3GPP specifications, an SRB can be set up only in the Enhanced CELL_FACH or CELL_DCH state if both
RAN and UE support the Uplink Enhanced CELL_FACH feature, but it cannot be set up in the CELL_FACH state.
During the service setup procedure for PS streaming service or PS BE services, uplink enhanced
CELL_FACH can be selected when the following conditions are met:
During the RRC connection setup procedure, the SRB is set up in uplink enhanced CELL_FACH state.
The UE state transition function takes effect. For detailed information, see the State Transition Feature
Parameter Description.
Uplink E-DCH is selected as the transport channel, or the uplink maximum bit rate is lower than
UlStrThsOnHsupa or UlBeTraffThsOnHsupa.
Downlink HS-DSCH is selected as the transport channel, or the downlink maximum bit rate is lower
than DlStrThsOnHsdpa or DlBeTraffThsOnHsdpa.
Uplink enhanced CELL_FACH Operation is selected as long as the downlink FACH and uplink RACH
are selected as the transport channels.
If uplink enhanced CELL_FACH is selected for a UE, the RNC does not select other HSPA+ features for
the UE.
Enhanced DRX
Enhanced DRX has no requirement for traffic classes and can be implemented if both cells and UEs
support the feature. For detailed information, see the HSPA Evolution Parameter Description.
Downlink Enhanced L2
During the RRC connection setup procedure, downlink enhanced L2 is not selected for the SRB. If the
SRB selects HS-DSCH as transport channel and downlink enhanced L2 is applied to the TRB; however,
downlink enhanced L2 is reconfigured for the SRB. The feature is applied to the SRB even after the TRB
is released.
Downlink enhanced L2 can be configured when the following conditions are met:
The service type is PS streaming service or PS BE services.
Downlink HS-DSCH and uplink E-DCH/DCH are selected as the transport channel.
When downlink enhanced L2 is selected for the UE, the maximum size of the downlink PDUs can be
specified by the parameter MacPduMaxSizeForDlL2Enhance.
Uplink Enhanced L2
During the RRC connection setup procedure, uplink enhanced L2 is not selected for the SRB. If the SRB
selects E-DCH as transport channel and uplink enhanced L2 is applied to the TRB, however, uplink
enhanced L2 is reconfigured for the SRB. The feature is applied to the SRB even after the TRB is
released.
During the service setup procedure, uplink enhanced L2 can be configured when the following
conditions are met:
The service type is CS speech service, PS speech service, PS streaming service, or PS BE services.
All the links in the active set of the E-DCH support uplink enhanced L2.
Uplink E-DCH is selected as the transport channel.
When uplink enhanced L2 is selected for the UE, the RLC supports flexible PDU sizes. In this case, the
maximum size and minimum size of the uplink PDUs must be specified on the RNC through the following
parameters respectively:
RlcPduMaxSizeForUlL2Enhance
RlcPduMinSizeForUlL2Enhance
The data can be sent directly without increasing data to the minimum size when the amount of data to be
sent in the RLC buffer is smaller than the specified minimum size.
DC-HSDPA/MIMO/64QAM/MIMO+64QAM/DC-HSDPA+MIMO
DC-HSDPA/DB-HSDPA/MIMO/64QAM/MIMO+64QAM/DC-HSDPA+MIMO can be configured when the
following conditions are met:
The service type is PS streaming service or PS BE services.
Downlink HS-DSCH is selected as the transport channel.
Uplink 16QAM
Uplink 16QAM can be configured when the following conditions are met:
The service type is PS streaming service or PS BE services.
All the links in the active set of the E-DCH support uplink 16QAM.
The traffic rate exceeds 4 Mbit/s.
− When HSUPA DCCC is enabled, the current rate is considered as the traffic rate.
− When HSUPA DCCC is disabled, the MBR is considered as the traffic rate.
When the fixed PDU size is used and is configured as 336 bits, the rate cannot reach 4 Mbit/s.
If the service rate need reach 11.5 Mbit/s, the PDU size must be configured as 656 bits.
If uplink enhanced L2 is enabled, the PDU size is not restricted because uplink enhanced L2 supports
variable PDU sizes.
The RNC determines whether to select uplink 16QAM for the UE. At the same time, the NodeB performs
MAC-e/i scheduling for the UE and determines whether to allocate uplink 16QAM-related resources to
the UE.
E-DPCCH Boosting
The RNC configures E-DPCCH Boosting for the UE when the following conditions are met:
The traffic class is PS BE service.
The UE is in the CELL_DCH state and some services use E-DCH as the uplink channel.
The MBR of services on the E-DCH is higher than 1000 kbit/s.
All the cells in the active set of the E-DCH support E-DPCCH Boosting.
DTX_DRX
DTX_DRX can be configured when the following conditions are met:
The service type is CS speech service, PS speech service, PS streaming service, or PS BE services.
Downlink HS-DSCH and uplink E-DCH are selected as the transport channel.
7 Parameters
Table 7-1 Parameter description
Parameter ID NE MML Command Description
BOOST NodeB ADD LOCELL Meaning: Indicates whether the Boosting feature is
MOD LOCELL supported by the cell.
GUI Value Range: FALSE(FALSE), TRUE(TRUE)
Actual Value Range: FALSE, TRUE
Unit: None
Default Value: FALSE(FALSE)
CSVoiceChlTy BSC6900 SET Meaning: Channel type of CS voice services. DCH
pe UFRCCHLTYPEP indicates that both uplink and downlink are preferably
ARA(Optional) carried on DCH. HSPA indicates that uplink is preferably
carried on E-DCH, and downlink is preferably carried on
HS-DSCH. In particular, both uplink and downlink will be
carried on DCH if either uplink cannot be carried on E-DCH
or downlink cannot be carried on HS-DSCH.
GUI Value Range: DCH(UL_DCH,DL_DCH),
HSPA(UL_EDCH,DL_HSDSCH)
Actual Value Range: DCH, HSPA
Unit: None
Default Value: DCH
CfgSwitch BSC6900 SET Meaning: Channel configuration strategy switch group.
UCORRMALGOS 1) CFG_DL_BLIND_DETECTION_SWITCH: When the
WITCH(Optional) switch is on, the DL blind transport format detection function
is used for single SRB and AMR+SRB bearers. Note that
the UE is only required to support the blind transport format
stipulated in 3GPP 25.212 section 4.3.1.
2) CFG_HSDPA_64QAM_SWITCH: When the switch is on,
64QAM can be configured for the HSDPA service.
3) CFG_HSDPA_DC_SWITCH: When the switch is on, DC
can be configured for the HSDPA service.
4) CFG_HSDPA_MIMO_SWITCH: When the switch is on,
MIMO can be configured for the HSDPA service.
5) CFG_HSDPA_MIMO_WITH_64QAM_SWITCH: When
the switch is on and the switches for 64QAM and MIMO are
on, 64QAM+MIMO can be configured for the HSDPA
service
6) CFG_HSPA_DTX_DRX_SWITCH: When the switch is
on, DTX_DRX can be configured for the HSPA service.
7) CFG_HSPA_HSSCCH_LESS_OP_SWITCH: When the
switch is on, HS-SCCH Less Operation can be configured
for the HSPA service.
8) CFG_HSUPA_16QAM_SWITCH: When the switch is on,
16QAM can be configured for the HSUPA service.
9) CFG_IMS_SUPPORT_SWITCH: When the switch is on
8 Counters
Table 8-1 Counter description
Counter Counter Name Counter Description Feature ID Feature Name
ID
67174449 VS.RRC.AttConnEs Total Number of RRC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
tab.Msg.RNC Connection Requests Connection and Radio
Received by RNC Access Bearer
Establishment and Release
67174450 VS.RRC.AttConnEs Number of RRC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
tab.RNC Connection Requests Connection and Radio
Processed by RNC Access Bearer
Establishment and Release
67174452 VS.RRC.SuccConn Number of Successful WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
Estab.RNC RRC Connection Connection and Radio
Establishments for RNC Access Bearer
Establishment and Release
67174454 VS.RRC.AttConnR Number of RRC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
el.RNC Connection Releases Connection and Radio
for RNC Access Bearer
Establishment and Release
67174641 VS.RRC.AttConnR Number of RRC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
el.Norm.RNC Connection Releases Connection and Radio
due to Normal Event for Access Bearer
RNC Establishment and Release
67174647 VS.RRC.AttConnR Number of RRC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
el.Unspec.RNC Connection Releases Connection and Radio
due to Unspecified Access Bearer
Causes for RNC Establishment and Release
67174689 VS.RRC.AttConnEs Number of RRC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
tab.CellDCH.RNC Connection Requests Connection and Radio
for RNC (UE Target Access Bearer
State of CELL_DCH) Establishment and Release
67174691 VS.RRC.SuccConn Number of Successful WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
Estab.CellDCH.RN RRC Connection Connection and Radio
C Establishments on Access Bearer
CELL_DCH Establishment and Release
67174705 VS.RRC.AttConnEs Number of RRC WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
tab.CellFACH.RNC Connection Requests Connection and Radio
for RNC (UE Target Access Bearer
State of CELL_FACH) Establishment and Release
67174706 VS.RRC.SuccConn Number of Successful WRFD-010510 3.4/6.8/13.6/27.2Kbps RRC
Estab.CellFACH.RN RRC Connection Connection and Radio
C Establishments on Access Bearer
CELL_FACH Establishment and Release
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
10 Reference Documents
[1] 3GPP TS 25.211, "Physical channels and mapping of transport channels onto physical channels
(FDD)"
[2] 3GPP TS 25.301, "Radio Interface Protocol Architecture"
[3] 3GPP TS 25.302, "Services provided by the physical layer".
[4] 3GPP TS 25.308, "UTRA High Speed Downlink Packet Access (HSPDA); Overall description"
[5] 3GPP TS 25.309: "FDD Enhanced Uplink; Overall description"
[6] 3GPP TS 25.319: "Enhanced uplink; Overall description"
[7] 3GPP TS 25.321, "Medium Access Control (MAC) protocol specification"
[8] 3GPP TS 25.322, "Radio Link Control (RLC) protocol specification"
[9] 3GPP TS 25.331, "Radio Resource Control (RRC)"
[10] 3GPP TS 25.433, "UTRAN Iub interface NBAP signaling"
[11] HSUPA Feature Parameter Description
[12] HSPA Evolution Feature Parameter Description
[13] State Transition Feature Parameter Description