Академический Документы
Профессиональный Документы
Культура Документы
RAN13.0
Feature Parameter Description
Issue 02
Date 2012-05-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.
Website: http://www.huawei.com
Email: support@huawei.com
WCDMA RAN
CE Resource Management Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience......................................................................................................................... 1-1
1.3 Change History.............................................................................................................................. 1-1
2 Overview......................................................................................................................................2-1
3 Technical Description ..............................................................................................................3-1
3.1 Basic Concepts ............................................................................................................................. 3-1
3.1.1 CE ......................................................................................................................................... 3-1
3.1.2 CE Sharing in a Resource Group ......................................................................................... 3-1
3.1.3 NodeB CE Capacity Specifications ...................................................................................... 3-2
3.2 Rules for Calculating CE Consumption ......................................................................................... 3-2
3.3 Admission and Congestion Control Based on CE Resources ...................................................... 3-7
3.3.1 Admission Control ................................................................................................................. 3-7
3.3.2 Basic Congestion Control ..................................................................................................... 3-7
3.4 Admission-CE-based Dynamic TTI Adjustment ............................................................................ 3-8
3.5 Dynamic CE Resource Management for HSUPA ......................................................................... 3-8
3.6 License CE Capacity Alarm ........................................................................................................... 3-8
4 Parameters..................................................................................................................................4-1
5 Counters ......................................................................................................................................5-1
6 Glossary ......................................................................................................................................6-1
7 Reference Documents .............................................................................................................7-1
1 Introduction
1.1 Scope
This document describes the basic concepts related to channel element (CE) resources and basic
methods of managing and controlling CE resources.
Document Issues
The document issues are as follows:
02 (2012-5-30)
01 (2011-12-30)
02 (2012-05-30)
This is the document for the second commercial release of RAN13.0.
Compared with issue 02 (2011-06-30) of RAN13.0, this issue has the following changes.
01 (2011-12-30)
This is the document for the first commercial release of RAN13.0.
This is a new document.
2 Overview
CE resources are a type of NodeB hard resource. The number of CEs supported by a NodeB indicates
the channel demodulation capabilities of the NodeB. The more CEs a NodeB supports, the more
powerful the channel demodulation and service processing capabilities.
Services at different rates require different numbers of CEs to ensure proper channel demodulation.
In a RAN, CE resources are managed by both the RNC and NodeB, as shown in Figure 2-1. The NodeB
reports its CE capacity to the RNC. The RNC determines whether to admit a new service based on the
number of CEs that need to be consumed and controls CE resources during CE congestion. This
ensures the proper use of CE resources. The NodeB dynamically manages CE resources and rapidly
adjusts the number of CEs that can be consumed based on the actual service rate. This increases CE
resource usage.
Figure 2-1 CE resource management
A proper use of CE resources increases the number of UEs that can be admitted and improves the
service quality of the admitted UEs.
3 Technical Description
3.1 Basic Concepts
3.1.1 CE
CE is a basic unit that measures the channel demodulation capabilities of a NodeB. CEs are classified
into uplink (UL) CEs and downlink (DL) CEs.
One UL CE needs to be consumed by a UL 12.2 kbit/s voice service (SF = 64) plus 3.4 kbit/s signaling.
One DL CE needs to be consumed by a DL 12.2 kbit/s voice service (SF = 128) plus 3.4 kbit/s
signaling.
If only 3.4 kbit/s signaling traffic is carried on a DCH or HSPA channel, one CE still needs to be
consumed. The number of CEs that need to be consumed by services of other types can be calculated
by analogy.
The number of UL and DL CEs supported by a NodeB is determined by the NodeB hardware capabilities
and the licensed CE capacity. The number of UL and DL CEs supported by the NodeB hardware is
called the physical CE capacity. The licensed CE capacity may differ from the physical CE capacity. The
smaller determines the number of CEs that can be used by an operator.
CE is a concept of the NodeB side. On the RNC side, it is called NodeB credit. The RNC performs
admission and congestion control based on the NodeB credit. In the UL, the number of Node credit
resources is twice that of CEs. In the DL, the number of NodeB credit resources equals that of CEs.
UL Resource Group
A UL resource group is a UL resource pool shared on a per-channel basis. As shown in Figure 3-1, more
than one cell can be setup in one UL resource group, One UL resource group can have multiple
baseband boards, but one board can belong to only one UL resource group. CE resources in one UL
resource group can be shared by baseband boards. This means that UEs in a cell in a UL resource
group can set up services on any board in the group. The physical CE capacity of a UL resource group is
the total CE capacity of baseband boards in the group.
DL Resource Group
Different from a UL resource group, a DL resource group is shared on a per-cell basis. As shown in
Figure 3-1, resources in a DL resource group are allocated to each baseband board based on cells; one
board can be configured to multiple DL resource groups. DL CE resources for UEs in the same cell can
be provided by any baseband board in the DL resource group. CE resources in one DL resource group
can be shared only within a baseband board.
CE resources reserved by the NodeB for common and HSDPA channels are shown in gray. CE
resources that need to be consumed by R99 and HSUPA services are shown in orange.
As listed in Table 3-1, the CE consumption at the rate of 3.4 kbit/s or 13.6kbit/s corresponds to the situation in which only
SRBs (without TRBs) are carried during an RRC connection. In other cases, if TRBs are also carried, CEs consumed are
also used for the SRBs that are transmitted at 3.4 kbit/s only.
If the UL enhanced L2 function is disabled, the RLC PDU size is fixed. The bit rate of one RLC PDU is determined by the
RLC PDU size and transmission time interval (TTI).
If the UL enhanced L2 function is enabled and the NodeB indicates in a private IE that dynamic CE
resource management has been enabled in the cell, the RNC calculates the SF based on the larger of
the bit rate of the smallest RLC PDU and the GBR.
If the UL enhanced L2 function is enabled, the RLC PDU size is flexible. The bit rate of the smallest RLC PDU is
determined by the minimum RLC PDU size and the TTI. The minimum RLC PDU size can be specified by the
RlcPduMaxSizeForUlL2Enhance parameter.
If the NodeB reports that dynamic CE resource management has been disabled, the RNC calculates
the SF based on the MBR.
If the NodeB does not report whether dynamic CE resource management has been enabled, the RNC
calculates the SF based on the value of the HsupaCeConsumeSelection parameter and whether the
UL enhanced L2 function is enabled.
− If HsupaCeConsumeSelection is set to MBR, the RNC calculates the SF based on the MBR.
For an HSUPA service, if the SRB over DCH function is enabled, the signaling of the HSUPA service consumes an
additional CE.
As listed in Table 3-3, the rate in the SF = minSF column indicates the maximum typical rate supported by the
corresponding SF when an HSUPA service is admitted at the MBR, and the rate in the SF > minSF column indicates the
maximum typical rate supported by the corresponding SF when the HSUPA service is admitted at the max(one RLC
PDU bit rate, GBR). For example, if an HSUPA service is admitted at the MBR, the maximum typical rate supported by
SF4 is 608 kbit/s.
If a rate is not listed in the preceding table, the number of CEs consumed corresponds to the larger rate specified in the
table. For example, in 2RX scenarios, if an HSUPA service is admitted at the MBR of 384 kbit/s, the HSUPA service
matches SF4 and consumes 8 CEs and 16 credit resources, which corresponds to the MBR of 608 kbit/s.
Table 3-4 CE consumption for an HSUPA service (2 ms TTI, SRB over DCH)
Direction Rate Rate SF 2RX 4RX
(kbit/s) (kbit/s)
SF > SF = Number of Corresponding Number of Corresponding
minSF minSF CEs Credits CEs Credits
Consumed Consumed Consumed Consumed
UL 608 608 4 8 16 8 16
1280 1280 2SF4 16 32 16 32
2720 2720 2SF2 32 64 32 64
Table 3-5 CE consumption for an HSUPA service (10 ms TTI, SRB over HSUPA)
Direction Rate Rate SF 2RX 4RX
(kbit/s) (kbit/s)
SF > SF = Number of Corresponding Number of Corresponding
minSF minSF CEs Credits CEs Credits
Consumed Consumed Consumed Consumed
UL NA 64 32 1 2 2 4
32 128 16 2 4 2 4
128 256 8 4 8 4 8
608 608 4 8 16 8 16
1280 1280 2SF4 16 32 16 32
Table 3-6 CE consumption for an HSUPA service (2 ms TTI, SRB over HSUPA)
Direction Rate (kbit/s) Rate SF 2RX 4RX
SF > minSF (kbit/s)
SF = Number of Corresponding Number of Corresponding
minSF CEs Credits CEs Credits
Consumed Consumed Consumed Consumed
UL 608 608 4 8 16 8 16
1280 1280 2SF4 16 32 16 32
2720 2720 2SF2 32 64 32 64
The CE consumption rules in Table 3-3, Table 3-4, Table 3-5 and Table 3-6 are only applicable to WBBPb and WBBPd in
3900 serial base station.
Examples of CE Consumption
UE A, which performs a UL 64 kbit/s and DL 384 kbit/s service on the DCH, consumes three UL CEs and
eight DL CEs.
UE B, which performs a UL 64 kbit/s and DL 1024 kbit/s service on the DCH and HS-DSCH respectively,
consumes three UL CEs and one DL CE if the DL signaling radio bearer (SRB) is carried on the DCH.
UE C, which performs a UL 608 kbit/s and DL 1024 kbit/s service on the E-DCH and HS-DSCH
respectively and at the same time performs an AMR speech service, consumes nine UL CEs and one DL
CE.
Call Admission
CE resources to be consumed by common channels and HSDPA services are reserved in advance.
Therefore, UEs requesting common or HSDPA channels do not need to be admitted based on CE
resources.
Admission control based on NodeB credit is performed on the RNC side. It mainly applies to RRC
connection requests, handover requests and non-HSDPA services.
Admission based on NodeB credit is optional in resource admission control. This function is controlled by
the switch parameters CacSwitch:NODEB_CREDIT_CAC_SWITCH and
NBMCacAlgoSwitch:CRD_ADCTRL. It is recommended that these two switch parameters are turned
on. If these two switch parameters are turned off, the correctness of the channel demodulation may not
be guaranteed because of excessive user admission.
For the detailed description of admission control based on NodeB credit, see the Call Admission Control
Feature Parameter Description.
For detailed information about LDR triggered by NodeB credit, see the Load Control Feature Parameter
Description.
4 Parameters
Table 4-1 Parameter description
Parameter ID NE MML Command Description
RlcPduMaxSiz BSC6900 SET UFRC(Optional) Meaning:This parameter specifies the maximum RLC
eForUlL2Enha PDU size when the UE is in CELL_DCH state and UL
nce Layer 2 Enhanced is enabled.
GUI Value Range:4~402
Actual Value Range:4~402
Unit:byte
Default Value:302
5 Counters
There are no specific counters associated with this feature.
6 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
7 Reference Documents
[1] 3GPP TS 25.433 "UTRAN Iub interface Node B Application Part (NBAP) signaling"
[2] Load Control Feature Parameter Description
[3] HSUPA Feature Parameter Description