You are on page 1of 90

RAN

Transmission Resource Management Parameter Description
Issue Date 01 2009-03-30

Error! Unknown document property name.

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. For any assistance, please contact our local office or company headquarters.

Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China Website: Email: http://www.huawei.com support@huawei.com

Copyright © Huawei Technologies Co., Ltd. 2009. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions
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 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.

Error! Unknown document property name.

Error! Unknown document property name. Error! Unknown document property name.

About This Document

About This Document
Author
Prepared by Edited by Reviewed by Translated by Tested by Approved by Zhang Lijun Lu Feng Duan Zhongyi Xing Ruizhi Sun Jingshu Date Date Date Date Date Date 2008-12-10 2009-01-10 2009-03-30 2008-10-16 2008-11-20

Issue Error! Unknown document property name. (Error! Unknown document property name.)

Error! Unknown document property name.

iii

.

.............................. 4-1 4.........................3................................................................... 4-9 4................3................................................... 4-2 4..........................................................................2.3 Capacity Requirement ............................................3..4 Path Resources ...................................................................................... 3-3 4 Transmission Resources .........................) Error! Unknown document property name.... 3-2 3.................................................. 3-1 3............................................5 ATM LP at the NodeB .................................................................................................................................................................................. 5-5 Issue Error! Unknown document property name........1-1 2 Introduction.............................................................................................................................................................................................2 Transport Bearer ................ 4-9 4..........................................................4-1 4...........................................1 Type of Path .3......... 4-4 4...................................................1 Transmission Resource Introduction .....................................................1 LP Introduction ................................. 5-3 5........ 4-6 4.................................................2 Physical and Data Link Layer Resources of the RNC for IP Transport .............................. Error! Unknown document property name............................................................................. 4-8 4...............................................................................................4.......................................................................................................................................1 RNC-Oriented Default Mapping ............................................................................................................................ 4-2 4...3........................... 3-1 3.................................................... 5-4 5........................4 Resource Group at the RNC . 4-10 5 TRM Mapping ....3 IP LP at the RNC .....................3 LP Resources .................. Contents Contents 1 Change History .......................3...........................................3-1 3.......Error! Unknown document property name.................................................... 4-3 4......2 ATM LP at the RNC ...........2 IP Path ....4..............................................................................1 Physical Layer Resources of the RNC for ATM Transport ..........3.............................................................5 Priorities ..........................2 DiffServ and DSCP ........................ 4-8 4.......................................................................2...............................................................2 Requirements of TRM Algorithms ..............................................................................2-1 3 TRM Algorithm Overview ...........................2......... v ............................... 4-4 4.................................... 4-9 4.........................................................................................2 Adjacent-Node-Oriented Mapping ....................................................................3 Mapping from Traffic Bearers to Transport Bearers ............................................................................................................ 5-4 5.......................... 3-3 3.................................... 5-2 5........................ 3-1 3............2....6 IP LP at the NodeB........................................................................................................1 Networking Requirement ...............2....1 AAL2 Path ........................................... 4-8 4.................................................................................................................................................... 5-3 5.............................2................................... 5-3 5............................................................................ 4-9 4..........................2..................................................1 Traffic Bearer ...............................1 Contents of TRM Algorithms .........................................4 Differentiated Service Requirement ......................................................................................................................................................................3.............................................5-1 5.........................2 Physical Transmission Resources ..........................................................................................................2 QoS Requirement ................... (Error! Unknown document property name..................................................................2.........................................................................................................

......................................................................................................10-1 Issue Error! Unknown document property name.......................................................................1 Admission Control Algorithm .............. 8-6 9 TRM Reference Documents ..3.................. 7-18 7............................................................ Error! Unknown document property name...............................................................................................1 Overview of the Downlink Iub Congestion Control Algorithm ..............................................................3 Admission Procedure ............................................................. 7-12 7............................................................................................................................................................................. 7-10 7................................................................................................... 7-9 7................3 Congestion Control of Iub User Plane... 7-18 7....................... 6-4 6....................................................7-1 7............. 6-11 6......................5 NodeB HSDPA Adaptive Flow Control Algorithm ...............................2 Values and Ranges ................................3 NodeB Uplink Bandwidth Adaptive Adjustment Algorithm ........................5 Uplink Iub Congestion Control Algorithm ............................................................................................................................ 6-1 6................4.................................5 NodeB Cross-Iur Single HSUPA Service Uplink Congestion Control Algorithm ................4 Intelligent Access Control ... 6-4 6................1 Overview of User Plane Processing .............2 Bandwidth Reserved for Services .........................................................9-1 10 Appendix .......................................2 NodeB Backpressure-Based Uplink Congestion Control Algorithm (R99 and HSUPA) ...... (Error! Unknown document property name. 8-1 8.. 7-3 7...........5..............................5.....Error! Unknown document property name.................................4 RNC R99 Single Service Uplink Congestion Control Algorithm .......................................2 IP RAN Header Compression .....................................4........................................................5...............4 RNC R99 Single Service Downlink Congestion Control Algorithm .........................................................2 Load Balancing ..................... 7-19 7............................................................. 6-11 6.6-1 6....................................................................................................................................................................................6.... 6-12 7 User Plane Processing .........................................5............................................................................ 7-17 7................. 6-1 6..... 6-5 6..........................................2 Hub Scheduling and Shaping ...................................5 Load Reshuffling and Overload Control ...................................................... 7-2 7......................................8-1 8.5...................................................4...........................5.................. Contents 6 Load Control.................................................................................................. 7-15 7.............3.........................2 RNC RLC Retransmission Rate-Based Downlink Congestion Control Algorithm ................7 IP PM ...........................................................................................................1 Definition of Load ..................................................................... 7-3 7.........3 Congestion and Overload Handling .. 7-1 7............................................................. 7-5 7......1 Iub Congestion Detection ...........................1 IP RAN FP-MUX .... 7-8 7................ 6-8 6..................................................................................3....................... 7-1 7.........................................................................................................5.................................... 7-16 7....................................................... 7-1 7................................... 7-13 7.......................................................................................................1 Overview of the Uplink Iub Congestion Control Algorithm ................................................................................................................. vi ..................................................2.................................................6 Iub Efficiency Improvement .....................4......................................... 7-17 7........ 6-11 6.........................................................................................4 Downlink Iub Congestion Control Algorithm ......................................3 Admission Control ...............................................................................................................................4..............................................................2....................... 7-19 8 TRM Parameters ..........3 RNC Backpressure-Based Downlink Congestion Control Algorithm ............1 RNC Scheduling and Shaping ......................... 6-12 6.................2 Iub Overload Detection ..............................................6..............2 NodeB Scheduling and Shaping .6...................................................1 Description ............................................3 FP Silent Mode..........................5...... 7-2 7........................................ 7-12 7...............................................) Error! Unknown document property name..............

..) Error! Unknown document property name....................................................5 Default TRMMAP Table for the ATM-Based Iu-CS Interface ......6 Default TRMMAP Table for the IP-Based Iu-CS Interface .......................................................................................Error! Unknown document property name...........2 Default TRMMAP Table for the IP-Based Iub and Iur Interfaces ................................1 Default TRMMAP Table for the ATM-Based Iub and Iur Interfaces .................. (Error! Unknown document property name............ Error! Unknown document property name............4 Default TRMMAP Table for the Hybrid-IP-Based Iub Interface ... 10-7 10.............. vii ...................... 10-8 Issue Error! Unknown document property name................................................ 10-4 10........ 10-2 10......3 Default TRMMAP Table for the ATM&IP-Based Iub Interface ...... 10-7 10.............................................7 Default TRMMAP Table for the Iu-PS Interface .... 10-1 10................ 10-5 10.............. Contents 10...........................................................

Error! Unknown document property name. (Error! Unknown document property name. The description of UBR PLUS is changed to UBR +. Issue Error! Unknown document property name. None.0 Change History The change history provides information on the changes in different document versions. this issue incorporates the following changes: Change Type Feature change Editorial change Change Description None.0. Compared with draft (2009-03-10) of RAN11.0 11. 1 Document and Product Versions Table 1-1 Document and product versions Document Version 01 (2009-03-30) Draft (2009-03-10) Draft (2009-01-15) 11. which are defined as follows:   Feature change: refers to the change in the transmission resource management. RAN Version This document is based on the BSC6810 and 3900 series NodeBs.0 11.Error! Unknown document property name. 01 (2009-03-30) This is the document for the first commercial release of RAN11. 1-1 . There are two types of changes. Error! Use the Home tab to apply 标题 1 to the text that you want to appear here. Editorial change: refers to the change in the information that was inappropriately described or the addition of the information that was not described in the earlier version.Error! Use the Home tab to apply 标题 1 to the text that you want to appear here. Parameter Change None.) Error! Unknown document property name.0. The available time of each feature is subject to the RAN product roadmap.

None. None. Draft (2009-03-10) This is the second draft of the document for RAN11.Error! Unknown document property name. and the description in this document is revised. (Error! Unknown document property name.0. Error! Unknown document property name.) Error! Unknown document property name. The title of the document is changed from Transmission Resource Management Description to Transmission Resource Management Parameter Description. Draft (2009-01-15) This is the initial draft of the document for RAN11.0. 1-2 .0. The added parameters are as follows:         MoniterPrd TimeToTriggerA EventAThred PendingTimeA TimeToTriggerB TimeToMoniter EventBThred PendingTimeB Issue Error! Unknown document property name. Compared with 02 (2008-07-30) of RAN10. None. draft (2009-03-10) optimizes the description.Error! Use the Home tab to apply 标题 1 to the text that you want to appear here. Compared with draft (2009-01-15). Parameter Change None. Parameter names are replaced with parameter IDs. None. Error! Use the Home tab to apply 标题 1 to the text that you want to appear here. draft (2009-01-15) incorporates the following changes: Change Type Feature change Editorial change Change Description None. General documentation change: The contents of the Iub Overbooking Description are added to this document.

2-1 . Intended Audience This document is intended for:   System operators who need a general understanding of transmission resource management. 2 Introduction Transmission Resource Management (TRM) is aimed at increasing the system capacity in various networking scenarios without affecting the Quality of Service (QoS). In addition. (Error! Unknown document property name.  Network Elements Involved Table 2-1 lists the Network Elements (NEs) involved in TRM. Personnel working on Huawei products or systems. Error! Use the Home tab to apply 标题 1 to the text that you want to appear here. Iur.) Error! Unknown document property name. this document describes only the TRM algorithms for the Iub interface. Impact  Impact on system performance None. the transmission on the Iub interface is of higher costs and more complex networking modes and has a greater impact on the system performance. Issue Error! Unknown document property name. TRM involves management of the transmission resources on the Iub. Therefore. Closely related to TRM algorithms are Radio Resource Management (RRM) algorithms. such as the scheduling algorithm and load control algorithm for the Uu interface. Impact on other features None.Error! Unknown document property name. Error! Unknown document property name. Transmission resources are one type of resource that the UTRAN provides. and Iu interfaces. The TRM algorithm policies should be consistent with the RRM algorithm policies. Compared with the transmission on the other interfaces.Error! Use the Home tab to apply 标题 1 to the text that you want to appear here. TRM provides differentiated services for Best Effort (BE) services to improve the data transmission efficiency.

2-2 .Error! Use the Home tab to apply 标题 1 to the text that you want to appear here. Error! Use the Home tab to apply 标题 1 to the text that you want to appear here. SGSN = Serving GPRS Support Node. Table 2-1 NEs involved in TRM UE – NodeB √ RNC √ MSC Server – MGW √ SGSN √ GGSN – HLR – NOTE:  –: not involved  √: involved UE = User Equipment. MSC Server = Mobile Service Switching Center Server. HLR = Home Location Register Issue Error! Unknown document property name. MGW = Media Gateway. Error! Unknown document property name.) Error! Unknown document property name. GGSN = Gateway GPRS Support Node. RNC = Radio Network Controller.Error! Unknown document property name. (Error! Unknown document property name.

The TRM algorithms applicable in transmission convergence scenarios are relatively complicated. Congestion control on the user plane of the transport network layer: For non-real-time (NRT) services.1 Contents of TRM Algorithms TRM algorithms cover the following aspects: Transmission resources: basic transmission resources. in which the TRM algorithms are also simple. the control helps prevent congestion and packet loss. Load control for transmission resources: The TRM algorithms control access of users to the network. the transmission convergence information. This is the simplest scenario.3    TRM Algorithm Overview 3. for example. Improvement in efficiency on the user plane of the transport network layer: The bandwidth occupied by services is reduced to improve the transmission efficiency on the user plane.   3.) Error! Unknown document property name.2. and radio bearer types of services. According to the QoS requirements. which can serve as the input to TRM algorithms. 3-1 . the bandwidth of which is exclusively occupied by this Iub interface. and attributes such as priorities and bandwidth. Allocation/Retention Priority (ARP).2 Requirements of TRM Algorithms 3.  Issue Error! Unknown document property name. on the transport network or by the hub NodeB. the transport networks map traffic to the transport bearers with the appropriate characteristics of transport types and transmission priorities. Transmission convergence: As shown in Figure 3-1. must be configurable.1 Networking Requirement The typical networking scenarios for the Iub interface are as follows:  Direct connection: The RNC is directly connected to a NodeB through a physical port. In this scenario. the network allows access of users to the maximum extent. Traffic Handling Priority (THP). the Iub traffic of more than one NodeB is converged. traffic class. With the QoS guaranteed. Mapping from traffic bearers to transmission bearers: Transport networks can provide priority-based services. including key objects such as ports and paths. (Error! Unknown document property name.

2 QoS Requirement The WCDMA system supports the following types of service:  Signaling. SIP. such as SRB. Table 3-1 Types of transport applicable to each interface Interface Iub Iur Iu-CS Iu-PS ATM √ √ √ – IP √ √ √ √ ATM&IP Dual Stack √ – – – Hybrid IP √ – – – 3.    Table 3-1 lists the types of transport applicable to each interface.) .2. the bandwidth of Asymmetric Digital Subscriber Line (ADSL) transmission is variable. ATM&IP dual stack: ATM and IP transmission resources are available for one Iub interface at the same time so that the transmission cost is reduced. and CCP Error! Unknown document property name. (Error! Unknown document property name. Hybrid IP: High-QoS transmission (such as IP over E1) and low-QoS transmission (IP over FE) are applicable to one Iub interface at the same time so as to enable differentiated management of services. In this case. For example. some bandwidth should be reserved for each operator.Figure 3-1 Iub transmission convergence networking NB = NodeB BW = bandwidth BW0 = bandwidth of the physical port  Bandwidth being variable: The bandwidth on the transport network might be variable. RAN sharing: Operators share the physical bandwidth. 3-2 Issue Error! Unknown document property name. the TRM algorithms need to be able to detect the available bandwidth. NCP. In this case.

In order to guarantee the basic QoS of NRT services. the transmission of signaling takes precedence. The appropriate type of transport bearer and transmission priority should be selected according to the traffic class. the traffic is low and its performance is closely related to Key Performance Indicators (KPIs) of the network.4 Differentiated Service Requirement Different types of service have different requirements.2. in descending order of priority. and SIP. For R99 services. in descending order of traffic priority. the Guaranteed Bit Rate (GBR) is not provided. 3-3 Issue Error! Unknown document property name. and background.  Real-time (RT) service. and the Iub delay and jitter are required to stay within a certain range. For the signaling such as NCP. and packet loss and long delay should be prevented.3 Capacity Requirement The capacity requirements are as follows:   With the QoS guaranteed. and High Speed Uplink Packet Access (HSUPA). For NRT services. interactive. the RAN allows the configuration of the GBR for NRT services. The details are as follows:  Differentiated service requirement for the transport layer: The transport layer provides multiple types of transport bearers and transmission priorities. When data needs to be transferred for NRT services with innate bursty characteristic. and type of radio bearer. (Error! Unknown document property name. and thus the frame loss rate of the traffic is low and the transmission delay is short. Service differentiation needs to take the following factors into consideration:   Traffic class: The WCDMA system provides four traffic classes: conversational. High Speed Downlink Packet Access (HSDPA). and Copper. CCP. user priority. the bandwidth should be fully utilized to ensure a high throughput and prevent congestion. The mapping between user priorities and ARPs is configurable. Therefore. see the Load Control Parameter Description. 3. and radio bearer type of the service. user priority. RT services do not allow packet loss or buffering of a huge data volume. Type of radio bearer: R99.2. The buffering of a huge data volume will result in an increase in the delay. Therefore. The transmission of high-priority traffic takes precedence upon transmission congestion. In the case of resource shortage. For details. In terms of QoS. the bandwidth must be guaranteed. SRB. This is mainly implemented by the user plane congestion control algorithm. so the bandwidth is not required to be guaranteed. such as conversational and streaming NRT or BE service.  To provide differentiated services is to provide different QoSs according to the traffic class. the data can be buffered so as to reduce the traffic throughput. streaming. the level of quality guaranteed varies according to the type of service. This is mainly implemented by the load control algorithm.    3. the time window mechanism is employed in the downlink." Error! Unknown document property name. User priority: There are three user priorities: Gold. such as interactive and background The requirements are as follows:  For RT services.) . Silver. see chapter 5 "TRM Mapping. For details. the network should allow access of users to the maximum extent.

see section 7. in the case of Iub transmission resource shortage."   Issue Error! Unknown document property name." Differentiated service requirement for the GBR of NRT services: For NRT services. The load control algorithm for transmission resources should keep consistent with that for the Uu interface. Differentiated service requirement for the load control algorithm: The load control algorithm for the Uu interface already supports differentiated services. when Uu resources face a hurdle. the bandwidth needs to be allocated to the services in a certain way. the GBR is configurable by running the SET USERGBR command according to the traffic class. Differentiated service requirement for the allocation of bandwidth for NRT services: The activity of NRT services does not follow any obvious rule. see chapter 6 "Load Control. For details. 3-4 . (Error! Unknown document property name. DCH or HSPA) of the services. For details. and bearer type (that is. For High Speed Packet Access (HSPA) services. Accordingly.) Error! Unknown document property name. When the demand from NRT services for the transmission bandwidth exceeds the total available Iub bandwidth. the Iub transmission resources also need to be allocated to the NRT services according to the SPI. the Uu resources are allocated to NRT services according to the Scheduling Priority Indicator (SPI) weight. user priority.3 "Congestion Control of Iub User Plane.

Figure 4-1 Relation between the ATM transmission resources IP transmission resources are as follows: Issue Error! Unknown document property name. and fractional ATM) Logical Port (LP) resources: ATM hub LP and ATM leaf LP Path resources: AAL2 path. (Error! Unknown document property name. channelized STM-1. UNI. ATM transmission resources are as follows: Physical transmission resources: E1/T1.) Error! Unknown document property name.4    Transmission Resources 4. ATM physical port (IMA. SAAL link. 4-1 . unchannelized STM-1. and IPoA PVC Figure 4-1 shows the relation between the ATM transmission resources.1 Transmission Resource Introduction Transmission resources consist of ATM transmission resources and IP transmission resources.

4-2 .2 Physical Transmission Resources 4. unchannelized STM-1. IP physical port (PPP/MLPPP port and trunk port) LP resources: IP LP Path resources: IP path and SCTP link Figure 4-2 shows the relation between the IP transmission resources.   Physical transmission resources: Ethernet port. channelized STM-1.2.) Error! Unknown document property name. (Error! Unknown document property name. Figure 4-2 Relation between the IP transmission resources 4. E1/T1.1 Physical Layer Resources of the RNC for ATM Transport The following types of physical transmission port are available for ATM transport:    E1/T1: electrical ports on the AEUa board Channelized STM-1/OC-3: optical ports on the AOUa board Unchannelized STM-1/OC-3c: optical ports on the UOIa board Issue Error! Unknown document property name.

Transmission Mode    VPI /VCI Range   Type of Service at the ATM Layer      UNI IMA Fractional ATM Fractional IMA LP UNI IMA LP VPI: 0 to 255 VCI: 32 to 65535 CBR RTVBR NRTVBR UBR UBR+   AOUa AOUa refers to the RNC 2-port ATM over channelized optical STM-1/OC-3 interface unit (REV: a).) Error! Unknown document property name. The following types of physical transmission port are available for IP transport:     E1/T1: electrical ports on the PEUa board FE/GE: electrical ports on the FG2a board Optical GE: optical GE ports on the GOUa board Unchannelized STM-1/OC-3c: optical ports on the UOIa board Table 4-2 describes the IP interface boards. the user plane data of the Iub.2. NCOPT   VPI: 0 to 255 VCI: 32 to 65535      4. and Iub interfaces. Table 4-1 ATM interface boards Board AEUa Description AEUa refers to the RNC 32-port ATM over E1/T1 interface unit (REV: a). Iu-CS. and Iu-PS interfaces is carried on UDP/IP.      VPI: 0 to 255 VCI: 32 to 65535      CBR RTVBR NRTVBR UBR UBR+ CBR RTVBR NRTVBR UBR UBR+ UOIa UOIa refers to the RNC 4-port ATM/packet over unchannelized optical STM-1/OC-3c interface unit (REV: a). 4-3 . Iu-BC.2 Physical and Data Link Layer Resources of the RNC for IP Transport The IP transmission resources include the physical layer and data link layer resources. Issue Error! Unknown document property name. (Error! Unknown document property name. Iur. The UOIa is applicable to the Iu-CS. Iur. Iur.Table 4-1 describes the ATM interface boards. In IP transport mode. and Iub interfaces. Iur. The AEUa is applicable to the Iu-CS. and Iub interfaces. The AOUa is applicable to the Iu-CS. Iu-PS.

As shown in Figure 4-3.3. UOIa POUa The board provides four unchannelized STM-1/OC-3c optical ports and supports IP over SDH/SONET. The POUa provides two IP over channelized STM-1/OC-3 optical ports and supports IP over E1/T1 over SDH/SONET. The PEUa is applicable to the IP-based Iub.3 LP Resources 4. as shown in Figure 4-3). and Iu-PS interfaces. The FG2a is applicable to the IP-based Iub. convergence of NB3 and NB4 at NB1. the total available bandwidth BW0 is known. Iur. however.) Error! Unknown document property name. Issue Error! Unknown document property name. Iu-CS. The POUa supports 42 MLPPP groups in E1 mode and 64 MLPPP groups in T1 mode. the system can start to operate and services can be established. If only physical transmission resources and path resources are configured. the total volume of data sent to NB2 may exceed BW2. Thus. the admission algorithm does not work properly. Iur.Table 4-2 IP interface boards Board PEUa Description PEUa refers to the RNC 32-port packet over E1/T1 interface unit (REV: a). in the following scenarios:  Transmission convergence Transmission convergence can be performed either on the transport network (for example. 4-4 . and Iu-CS interfaces. (Error! Unknown document property name. GOUa GOUa refers to the RNC 2-port packet over optical GE Ethernet interface unit (REV: a). convergence of NB1 and NB2. but the values of BW1 through BW4 are unknown. There are problems. The GOUa is applicable to the IP-based Iub. Iu-CS. FG2a FG2a refers to the RNC packet over electrical 8-port FE or 2-port GE Ethernet interface unit (REV: a). as shown in Figure 4-3) or at the hub NodeB (for example. POUa refers to the RNC 2-port packet over channelized optical STM-1/OC-3 interface unit (REV: a). if the total reserved bandwidth at NB2 exceeds BW2. the bandwidth constraints at the convergence points are unavailable. Iur.1 LP Introduction After the physical transmission resources and path resources are configured. PPP   Transmission Mode    PPP MLPPP MCPPP IP over Ethernet IP over Ethernet PPP MLPPP 4. For example. and Iu-PS interfaces. congestion and packet loss may occur and in the downlink.

LPs are used for bandwidth configuration at transport nodes and for bandwidth admission and traffic shaping. Such an LP is called a leaf LP. such a requirement fails to be fulfilled. A physical port can be a leaf LP. An LP describes the bandwidth constraints between paths or between other LPs. and transmission resource groups cannot contain LPs either. Only one level of IP LP is supported. Such an LP is called a hub LP.) Error! Unknown document property name.Figure 4-3 Iub transmission convergence  RAN sharing Operators share the bandwidth at one NodeB. To solve the preceding problems. One key characteristic of LPs is the bandwidth. LPs are configured on the RNC side for the following purposes: Issue Error! Unknown document property name. LPs at the RNC can be classified into the following types:    ATM LP: used for bandwidth admission and traffic shaping. On the RNC side. the bandwidth needs to be configured for each operator so that the bandwidth used by each operator does not exceed their respective reserved bandwidth. If only physical transmission resources and path resources are configured. the Logical Port (LP) concept is introduced to the TRM feature. IP LP: used for bandwidth admission and traffic shaping. For an LP. so as to prevent congestion. LPs need to be configured on both the RNC and NodeB sides. An LP can also be comprised of only other LPs. In this case. LPs cannot contain transmission resource groups. (Error! Unknown document property name. Multiple levels of ATM LPs are supported. the uplink bandwidth can be different from the downlink bandwidth.   An LP can be comprised of only paths. Multiple levels of transmission resource groups are supported. A physical port can be a hub LP. Transmission resource group: used for admission only and applicable to ATM and IP transport. 4-5 .

Resource management mode. that is. so as to implement bandwidth admission and traffic shaping. also called Virtual Ports (VPs). link. 4-6 . and the uplink bandwidth is used for bandwidth admission only. These LPs have the following attributes:    Type of LP. or ADD IPOAPVC command is executed to add an AAL2 path. hub or leaf Bandwidth: The downlink bandwidth is used for traffic shaping and bandwidth admission. ADD SAALLNK.) Error! Unknown document property name. In the case of ATM traffic convergence. have the functions of ATM traffic shaping and bandwidth admission. which involves both leaf LPs and hub LPs. The RNC supports multi-level shaping (a maximum of five levels).3. or PVC can be set to join an LP. They are configured on ATM interface boards by running the ADD ATMLOGICPORT command.  Admission control in convergence or RAN sharing scenario Traffic shaping in the downlink LPs are configured on the NodeB side for the following purposes:   Fairness between local data and forwarded data in convergence scenario Traffic shaping in RAN sharing scenario 4. SHARE or EXCLUSIVE: indicates whether operators in RAN sharing scenario share the Iub transmission resources. (Error! Unknown document property name.2 ATM LP at the RNC ATM LPs. Issue Error! Unknown document property name. the path. that is. When the ADD AAL2PATH. LPs need to be configured for each NodeB and at each convergence point. Take the convergence shown in Figure 4-4 as an example. or an IPoA PVC respectively. an SAAL link.

Table 4-3 ATM LP capabilities of interface boards at the RNC Board AEUa Number of LPs   Level of LPs Five Leaf LP: 0 to 127 Hub LP: 128 to 191 Issue Error! Unknown document property name. corresponds to the hub NodeB. have a one-to-one relation with the NodeBs.    In RAN sharing scenario. In the Call Admission Control (CAC) algorithm.Figure 4-4 Traffic convergence at LPs NB = NodeB BW = bandwidth BW0 = bandwidth of the physical port on the RNC  The leaf LPs. (Error! Unknown document property name. The bandwidth of the hub LP is equal to the Iub bandwidth of the hub NodeB. That is. and LP4. LP2. and the LPs connected to the hub LP correspond to the NodeBs on the network. The actual rate at a leaf LP is limited by the bandwidth of the leaf LP and the scheduling rate at the hub LP and physical port. LP3. LP125. The bandwidth of each leaf LP is equal to the Iub bandwidth of each corresponding NodeB. an LP needs to be configured for each operator that uses the NodeB. LP1. the total reserved bandwidth of all the LPs under a hub LP cannot exceed the bandwidth of the hub LP. that is. The hub LP. Table 4-3 describes the ATM LP capabilities of interface boards at the RNC.) Error! Unknown document property name. that is. 4-7 . the reserved bandwidth of a leaf LP is limited by not only the bandwidth of the leaf LP but also the bandwidth of the hub LP and the bandwidth of the physical port.

RX bandwidth.4 Resource Group at the RNC Resource groups have the bandwidth admission function but do not have the traffic shaping function. They are configured on IP interface boards by running the ADD IPLOGICPORT command. To configure an ATM LP. the path or link can be set to join an LP. run the ADD RSCGRP command to add an ATM resource group to the interface board at the NodeB. and bearing port number. The LP has attributes such as the TX bandwidth.3 IP LP at the RNC IP LPs have the functions of IP traffic shaping and bandwidth admission. 4. (Error! Unknown document property name. IP LPs are similar to ATM LPs in terms of principles and application. The current version of RAN supports only one level of IP LP.3. and the RX Issue Error! Unknown document property name. run the ADD RSCGRP command.3. These LPs have the following attributes:   Bandwidth: The downlink bandwidth is used for traffic shaping and bandwidth admission. When the ADD IPPATH or ADD SCTPLNK command is executed to add an IP path or an SCTP link respectively.Board AOUa Number of LPs   Level of LPs Five Leaf LP: 0 to 255 Hub LP: 256 to 383 Leaf LP: 0 to 383 Hub LP: 384 to 447 UOIa_ATM   Five 4. bearing port type. 4-8 .3. Table 4-4 IP LP capabilities of interface boards at the RNC Board PEUa FG2a GOUa UOIa POUa Number of LPs None 0 to 119 0 to 119 0 to 119 None Level of Shaping One-level shaping at PPP or MLPPP ports Two-level shaping at LPs and Ethernet ports Two-level shaping at LPs and Ethernet ports One-level shaping at PPP ports One-level shaping at PPP or MLPPP ports 4. Resource management mode.) Error! Unknown document property name.5 ATM LP at the NodeB ATM LPs at the NodeB have the function of ATM traffic shaping. SHARE or EXCLUSIVE: indicates whether operators in RAN sharing scenario share the Iub transmission resources. Table 4-4 describes the IP LP capabilities of interface boards at the RNC. and the uplink bandwidth is used for bandwidth admission only. To add a resource group. that is. The TX bandwidth is used for traffic shaping.

They determine the type of path. the TXTRFX and RXTRFX parameters need to be set.) Error! Unknown document property name. that is.4. 4. user plane. when the ADD IPPATH command is executed to add an IP path.1 AAL2 Path In ATM transport mode. when the ADD AAL2PATH.bandwidth is used to calculate the remaining bandwidth for backpressure. are key resources. The paths on the user plane.6 IP LP at the NodeB IP LPs at the NodeB have the function of IP traffic shaping. or ADD OMCH command is executed to add an AAL2 path. Each interface board of the NodeB supports a maximum of four IP LPs. The traffic record indexes are configured by running the ADD ATMTRF command. Issue Error! Unknown document property name. ATM LPs at the NodeB are mainly used to differentiate operators in RAN sharing scenario. The TX bandwidth is used for traffic shaping. is applicable to only hybrid IP transport. Then. that is. IP LPs at the NodeB are mainly used to differentiate operators in RAN sharing scenario. denoted LQ_xx. 4. AAL2 paths for ATM transport and IP paths for IP transport. The LP has attributes such as the TX bandwidth. or channel can be set to join an LP. an SAAL link. and management plane. the following types of AAL2 path can be configured:      CBR RT-VBR NRT-VBR UBR UBR+ When an AAL2 path is configured. 4. 4. To configure an IP LP. Each interface board of the NodeB supports a maximum of four ATM LPs. ADD SAALLNK. the path can be set to join an LP. RX bandwidth.3. The allocation and management of transmission resources are based on paths.4. bearing port type. a path carrying the data traffic of the local NodeB. link. and bearing port number. when the ADD IP2RSCGRP command is executed. Then. run the ADD RSCGRP command to add an IP resource group to the interface board at the NodeB.4 Path Resources Path resources involve those on the control plane. (Error! Unknown document property name. or an OM channel respectively. the path. 4-9 . the signaling traffic and the forwarded data traffic can be set to join an LP. and the RX bandwidth is used to calculate the remaining bandwidth for backpressure.2 IP Path IP paths can be categorized into the following classes:   High-quality class Low-quality class The low-quality class.

Table 4-5 Types of IP path Type QoS path Non-QoS path High-Quality Class QoS BE AF11 AF12 AF13 AF21 AF22 AF23 AF31 AF32 AF33 AF41 AF42 AF43 EF Low-Quality Class LQ_QoS LQ_BE LQ_AF11 LQ_AF12 LQ_AF13 LQ_AF21 LQ_AF22 LQ_AF23 LQ_AF31 LQ_AF32 LQ_AF33 LQ_AF41 LQ_AF42 LQ_AF43 LQ_EF NOTE   On the Iu-PS interface. HSDPA and HSUPA services can be carried on the same IP path. as shown in Figure 4-5. The PHB of non-QoS paths is determined by the type of path. UNI.IP paths can be further classified into QoS path and non-QoS path. there are five types.5 Priorities At each ATM port (such as IMA. 4. Table 4-5 lists the types of IP path. even if IPoA transport is used. 4-10 . (Error! Unknown document property name. Issue Error! Unknown document property name. with HSDPA services in the downlink and HSUPA services in the uplink. The scheduling order is as follows: CBR > RT-VBR > MCR of UBR+ > NRT-VBR > UBR > UBR+. or fractional ATM port) or leaf LP of the RNC.   The Per Hop Behavior (PHB) of QoS paths is determined by the TRM mapping configuration.) Error! Unknown document property name. IP paths still need to be configured.

UNI.) Error! Unknown document property name. or fractional ATM port) or LP of the NodeB. Queue5. Queue4.Figure 4-5 Priorities at each ATM port of the RNC At each IP port (such as PPP/MLPPP port) or LP of the RNC. Queue6). (Error! Unknown document property name. there are four types. The default scheduling order is as follows: Queue1 > WFQ (Queue2. The scheduling order is as follows: CBR or MCR of UBR+ > RT-VBR > NRT-VBR > UBR or UBR+. 4-11 . where WFQ refers to Weighted Fair Queuing. as shown in Figure 4-8. where WRR refers to Weighted Round Robin. The default scheduling order is as follows: Queue1 > Queue2 > WRR (Queue3. as shown in Figure 4-6. Queue5. Issue Error! Unknown document property name. there are six types. Queue4. Figure 4-6 Priorities at each IP port of the RNC At each ATM port (such as IMA. there are six types. Figure 4-7 Priorities at each ATM port of the NodeB At each IP port (such as Ethernet port or PPP/MLPPP port) or LP of the NodeB. Queue6). as shown in Figure 4-7. Queue3.

Figure 4-8 Priorities at each IP port of the NodeB Issue Error! Unknown document property name. 4-12 .) Error! Unknown document property name. (Error! Unknown document property name.

5-1 . The RNC supports configuration of mapping to transport bearers according to the characteristics of traffic. and the QoS requirements of traffic vary according to the traffic types.5 Figure 5-1 shows the TRM mapping.) Error! Unknown document property name. (Error! Unknown document property name. Figure 5-1 TRM mapping TRM Mapping The transport network can provide differentiated QoS services. TRMMAP refers to the mapping from traffic bearers to transport bearers. Issue Error! Unknown document property name.

but they still have delay specifications for ping commands. For R99 services. When the load is heavy. When the load is light. the delay requirement must be fulfilled. (Error! Unknown document property name. Different types of service have different QoS requirements. there are requirements for the delay and frame loss rate. traffic types are determined jointly by the traffic class. ARP: Even for traffic of the same type. The factors such as the frame loss rate and delay will affect KPIs such as the connection delay. BE services are relatively insensitive to the delay. Traffic bearers are used to describe the traffic types in the broad sense only. streaming. For CS services. R99 bearers have certain requirements for the delay because of the time window mechanism. These traffic types are further classified according to user priorities. and HSUPA. reliable transmission is required. the delay requirement can be lowered to a certain extent so as to guarantee the throughput. Thus. excessive delay and jitter must be avoided. traffic types are determined by the traffic class at the radio network layer and the type of radio bearer. The mapping from traffic types to transmission resources takes the following factors into consideration:  Traffic class at the radio network layer: conversational. and background. however. 5-2  Issue Error! Unknown document property name. the time window will be adjusted frequently. The RNC provides the following traffic classes that can be used in TRMMAP configuration: − − − − − − − − − − Common channel SRB SIP AMR speech CS conversational CS streaming PS conversational PS streaming PS interactive PS background  Type of radio bearer: R99. and THP. high-priority services may require high-QoS transport bearers at the transport layer. Error! Unknown document property name. Video Phone (VP) services are closely sensitive to packet loss.5. in descending order of QoS requirement. the end-to-end latency of voice services affects the Mean Opinion Score (MOS).  For the Iub control plane and the Uu signaling. Otherwise. interactive. have relatively low requirements for the delay because of the absence of the time window mechanism on the Iub interface.) .    Traffic types are defined as follows:   From the narrow perspective. the QoS requirements of different users vary. From the broad perspective. handover success rate. ARP.1 Traffic Bearer The prerequisite for TRM algorithms is the guarantee of QoS. HSDPA. For example. for the purpose of better differentiated services. HSPA bearers. and call drop rate. access success rate. type of radio bearer.

which are collectively called PHB. type of radio bearer. medium. There are three classes of THP: high. In summary. and THP. such as PS interactive services. and packet discard policies. Issue Error! Unknown document property name.2. THP: For interactive services. and low.4 "Path Resources. user priority and ARP. the inputs to TRMMAP are the traffic class. traffic is differentiated and applied with flow control according to the QoS requirement. The QoS information. When entering the network. 5-3 .2. The transport bearer service refers to the service of transmitting traffic over paths of specific types. All nodes within the DiffServ domain implement PHB according to the DSCP field in each packet. the DSCP fields of the packets are set.2 Transport Bearer 5. 5. That is. Through the DSCP. see section 4.) Error! Unknown document property name. In addition. The services include resource allocation. that is. THP parameters are available." 5. the QoS mechanism differentiates traffic and QoS requirements according to the DSCP values and also provides services for the traffic.1 Type of Path Paths are defined for the purpose of preventing the impact of different types of interface boards and different traffic queues at the physical layer. each combination of these inputs corresponds to one priority of transport bearer. is carried in the header of each IP packet to inform the nodes on the network of the QoS requirement.2 DiffServ and DSCP Differentiated Services (DiffServ) is a key technology adopted in IP transport to improve the network QoS. (Error! Unknown document property name. For path types. each router on the propagation path knows which type of service is desired. On the network. the Differentiated Services Code Point (DSCP). queue scheduling.

Value range of PHB: BE. Table 5-1 lists the default TRMMAP tables. AF41. Iur IP. 5-4 .3 Mapping from Traffic Bearers to Transport Bearers For the mapping from traffic bearers to transport bearers. because of simple configuration and better implementation of multiplexing. Iu-CS IP. Issue Error! Unknown document property name. PHB. both the default configuration and the adjacent-node-oriented configuration are available.3. Primary and secondary paths can be configured. The keyword used for configuring TRMMAP is the traffic type. AF23. Iur ATM. Iub hybrid IP. and Iu-PS respectively.) Error! Unknown document property name. 5. Iub ATM&IP. AF33. AF21. QoS guarantee.   Value range of DSCP: 0 to 63. AF11. The mapping from PHB to DSCP can be set by running the SET PHBMAP command. AF42.Figure 5-2 DSCP field in an IP packet The DSCP mechanism employed at the RNC is as follows: The traffic carried on QoS paths uses the DSCPs mapped from services. AF22.1 RNC-Oriented Default Mapping The RNC provides default mapping tables with IDs from 0 to 8 for Iub ATM. and EF. AF43. For details about primary and secondary paths. AF31." 5. Each DSCP corresponds to a PHB attribute. (Error! Unknown document property name. that is. AF32. and service differentiation. that is.3 "Admission Control. and THP. AF12. Iub IP. type of radio bearer. These tables can only be queried by running the LST TRMMAP command. QoS paths are recommended. in ascending order of priority. Iu-CS ATM. the combination of traffic class. see section 6. whereas the traffic carried on non-QoS paths uses the DSCPs corresponding to the type of IP path. AF13.

Configuration of TRM Mapping For details. (Error! Unknown document property name.Table 5-1 Default TRMMAP tables Interface Iub Iur Iu-CS Iu-PS ATM 0 4 6 IP 1 5 7 8 ATM&IP 2 Hybrid IP 3 NOTE The RNC-oriented default TRM mapping is not specific for operators or user priorities. see chapter 10 "Appendix. the RNC-oriented default TRM mapping applies.) Error! Unknown document property name. If no adjacentnode-oriented mapping is configured. 5-5 ." Configuration of DSCP Mapping Table 5-2 lists the default mapping from PHB to DSCP. Issue Error! Unknown document property name. Table 5-2 Default mapping from PHB to DSCP PHB EF AF43 AF42 AF41 AF33 AF32 AF31 AF23 AF22 AF21 AF13 AF12 AF11 DSCP (Binary) 101110 100110 100100 100010 11110 11100 11010 10110 10100 10010 1110 1100 1010 DSCP (Decimal) 46 38 36 34 30 28 26 22 20 18 14 12 10 If the mapping from PHB to DSCP is not configured by running the SET PHBMAP command. the default mapping applies.

 

If the traffic is carried on a non-QoS IP path, the DSCP corresponding to the path type is used. If the traffic is carried on a QoS IP path, the DSCP is determined by the mapping (that is, the PHBMAP) from the PHB, which is further determined by the mapping (that is, the TRMMAP) from traffic classes to QoS paths. Thus, the user needs to configure only one QoS path before obtaining diversified mapping from different traffic classes and user priorities to different DSCPs.

5.3.2 Adjacent-Node-Oriented Mapping
To provide better differentiated services, the RNC supports configuration of TRMMAP for adjacent nodes and even for a specific operator and a specific user priority at a specific adjacent node. This helps achieve flexible configuration of mapping from traffic bearers to transport bearers. To configure the mapping for an adjacent node, perform the following steps: Step 1 Run the ADD TRMMAP command to specify the mapping from the traffic classes of a specific interface type and transport type to the transport bearers. Step 2 Run the ADD ADJMAP command to reference the configured TRMMAP tables for the adjacent node. In this step, the TRMMAP tables need to be individually specified for Gold, Silver, and Copper users.
NOTE

In RAN sharing scenario, if the resource management mode is set to EXCLUSIVE, the operator index needs to be set so as to specify the TRMMAP for the users of that operator at the adjacent node. The related commands are ADD TRMMAP, MOD TRMMAP, ADD ADJMAP, and MOD ADJMAP.

----End

Issue Error! Unknown document property name. (Error! Unknown document property name.)

Error! Unknown document property name.

5-6

6
6.1 Definition of Load

Load Control

The load control algorithm allocates transmission resources to services, manages the transmission bandwidth, and controls the transmission load for the purpose of allowing access of users to the maximum extent without affecting the QoS.

The load control algorithm is implemented at the RNC, and therefore, the load is defined and measured at the RNC. The definition of load is based on the reserved bandwidth. The load control algorithm reserves bandwidth for each service. The load refers to the sum of bandwidth reserved for all services. The uplink load and downlink load are calculated separately. The load of each path and that of each LP (including leaf LP and hub LP) need to be calculated. The load definitions are as follows:
  

Load of a path: sum of bandwidth reserved for all services on the path Load of a leaf LP: total load of all paths carried on the LP Load of hub LP: total load of all LPs under the hub LP

6.2 Bandwidth Reserved for Services
The load is defined on the basis of the bandwidth reserved for each service. Therefore, the method of calculating the bandwidth reserved for each type of service must be provided. Bandwidth reserved for a service = Transport-layer rate of the service x Activity factor, where the transport-layer rate of the service derives from the rate that the user applies for. The RNC calculates the reserved bandwidth based on the activity factor and performs admission control based on the reserved bandwidth, thus enabling Iub overbooking, that is, allowing admission of more services to the bandwidth. The more the services admitted, the higher the statistical multiplexing gain. After activity factors are taken into consideration, a larger number of users can access the network over the Iub interface. In this case, however, the Iub congestion probability increases accordingly. If all services are transmitted at the rate higher than their respective admission bandwidth at the same time, congestion and packet loss occur on the Iub interface. Then, the
Issue Error! Unknown document property name. (Error! Unknown document property name.) Error! Unknown document property name. 6-1

user experience deteriorates and the Iub bandwidth usage decreases. To solve the possible congestion problem, the Iub interface requires the related congestion control algorithm. For details, see section 7.3 "Congestion Control of Iub User Plane." The following bandwidth reservation policies apply:

RT services, including conversational and streaming services, are admitted at the Maximum Bit Rate (MBR).
− −

The bandwidth for RT services must be guaranteed. RT services do not allow packet loss or large-volume data buffering. The activity of RT services follows an obvious rule. When multiple services access the network, the total actual traffic volume is relatively stable. The appropriate setting of activity factors can help achieve correct admission of the services. RT services should be admitted on the basis of the average actual traffic volume, so that the number of users allowed to access the network can be increased to the maximum extent under the condition that the QoS is guaranteed. Reserved bandwidth for admission of an RT service = MBR x Activity factor, where the activity factor needs to be set for each type of service. NRT services do not have strict requirements for bandwidth guarantee. When resources are insufficient, the traffic throughput can be lowered at the application layer through data buffering, to which the application layer can be adaptive. The activity of NRT services does not follow any obvious rule. When multiple services access the network, the total actual traffic volume fluctuates greatly. Therefore, it is difficult to estimate the exact bandwidth used by NRT services. If a large number of users access the network, the bandwidth efficiency is improved to a certain extent, but congestion and packet loss occur. If a small number of users access the network, the bandwidth efficiency is low. If no appropriate user plane congestion control algorithm is available for preventing congestion and packet loss, the services should be admitted at the MBR multiplied by the activity factor. The MBR, however, needs to be adjusted frequently in the interests of high bandwidth efficiency and a large number of users accessing the network. Thus, a complicated user plane load algorithm is required. Huawei has developed a complete user plane congestion control algorithm, in which the only condition of transmission admission is to provide GBR guarantee for users. The principle is to allow access of users to the maximum extent under the condition that the GBR is guaranteed. That is, the admission algorithm can reserve the bandwidth for users based on the GBR. Admission at 3.4 Kbit/s: The bandwidth is fixed at 3.4 Kbit/s. This admission mode is applicable to R99, HSDPA, and HSUPA services. Admission at the GBR: For R99 services, if the bandwidth of a transport channel varies between 3.4 Kbit/s and 13.6 Kbit/s, resource allocation and resource admission do not need to be performed again.

− 

NRT services, including interactive and background services, are admitted at the GBR.

In terms of 3G signaling, SRB services can be admitted at either the GBR or 3.4 Kbit/s.
− −

In terms of common channels, EFACH services are admitted at the GBR, and other common channel services are admitted at the MBR.

Because of the discontinuity of traffic, there are active periods, during which data is transmitted, and inactive periods, during which data is not transmitted. Activity factors are used by the admission control to achieve better utilization of transmission resources.
Issue Error! Unknown document property name. (Error! Unknown document property name.) Error! Unknown document property name. 6-2

Activity factors are applicable to the Iub, Iur, Iu-CS, and Iu-PS interfaces. The number of users that can access the network is related to the activity factors. For common channels or SRBs, the activity factors are identical for all users, instead of varying according to user priorities. Activity factors can be configured for different types of service by running the ADD TRMFACTOR command. Table 6-1 lists the default settings of activity factors for different types of service. Table 6-1 Default settings of activity factors for different types of service Type of Service General common channel General common channel IMS SRB IMS SRB MBMS common channel SRB SRB AMR voice AMR voice R99 CS conversational R99 CS conversational R99 CS streaming R99 CS streaming R99 PS conversational R99 PS conversational R99 PS streaming R99 PS streaming R99 PS interactive R99 PS interactive R99 PS background R99 PS background HSDPA SRB HSDPA IMS SRB HSDPA voice
Issue Error! Unknown document property name. (Error! Unknown document property name.)

UL/DL DL UL DL UL DL DL UL DL UL DL UL DL UL DL UL DL UL DL UL DL UL DL DL DL

Default Activity Factor (%) 70 70 15 15 100 15 15 70 70 100 100 100 100 70 70 100 100 100 100 100 100 50 15 70
6-3

Error! Unknown document property name.

Type of Service HSDPA conversational HSDPA streaming HSDPA interactive HSDPA background HSUPA SRB HSUPA IMS SRB HSUPA voice HSUPA conversational HSUPA streaming HSUPA interactive HSUPA background EFACH channel

UL/DL DL DL DL DL UL UL UL UL UL UL UL DL

Default Activity Factor (%) 70 100 100 100 50 15 70 70 100 100 100 20

When the adjacent-node-oriented mapping is added or modified by running the ADD ADJMAP or MOD ADJMAP command respectively, the activity factor table to be referenced can be specified by the FTI parameter. For BE services, the GBR can be set by running the SET USERGBR command. The associated parameters are as follows:
     

TrafficClass THPClass BearType UserPriority UlGBR DlGBR

6.3 Admission Control
Admission control is used to determine whether the system resources are sufficient for the network to accept the access request of a new user. If the system resources are sufficient, the access request is accepted; otherwise, the request is rejected.

6.3.1 Admission Control Algorithm
The admission policy varies according to the type of user.

For a new user, the following requirements apply:

Admission to a path:
Error! Unknown document property name. 6-4

Issue Error! Unknown document property name. (Error! Unknown document property name.)

2 Load Balancing In the admission control mechanism.) Load of the LP + Bandwidth required by the user < Total bandwidth of the LP – Bandwidth reserved for handover  For handover of a user.) Load of the LP + Bandwidth required by the user < Total bandwidth of the LP – Congestion threshold NOTE  For a path that belongs to a path group. For an IMA group or MLPPP group. the RNC automatically adjusts the maximum bandwidth available to the whole group and uses the new admission threshold if the bandwidth of an IMA link or MLPPP link changes. the following requirements apply: − Admission to a path: Load of the path + Bandwidth required by the user < Total configured bandwidth of the path − Admission to an LP: (The admission to LPs should be performed level by level.3. admission control must be performed at both the path level and the path group level. 6-5 . A service is not always preferably admitted to the primary path.Load of the path + Bandwidth required by the user < Total configured bandwidth of the path – Bandwidth reserved for handover − Admission to an LP: (The admission to LPs should be performed level by level. The parameters that are used to reserve bandwidth for handover are as follows:   FWDHORSVBW BWDHORSVBW 6. If the load of the primary path exceeds its load threshold and the ratio of primary path load to secondary path load is higher than the load ratio threshold. the following requirements apply: − Admission to a path: Load of the path + Bandwidth required by the user < Total configured bandwidth of the path – Congestion threshold − Admission to an LP: (The admission to LPs should be performed level by level. (Error! Unknown document property name. Based on the preceding requirement. the user priorities are as follows: User requesting handover > New user > User requesting rate upsizing The congestion thresholds are FWDCONGBW and BWDCONGBW. The following requirement is applicable to each level of LP. load balancing is an algorithm used to achieve the load balance between primary and secondary paths.  Bandwidth reserved for handover ≤ Congestion threshold ≤ Congestion resolving threshold The congestion threshold and the congestion resolving threshold are used to prevent the pingpong effect. The following requirement is applicable to each level of LP.) Error! Unknown document property name. The following requirement is applicable to each level of LP. and the congestion resolving thresholds are FWDCONGCLRBW and BWDCONGCLRBW. then the Issue Error! Unknown document property name.) Load of the LP + Bandwidth required by the user < Total bandwidth of the LP  For rate upsizing of a user.

the ARP needs to be taken into consideration. they can be referenced when load balancing parameters need to be set for ATM&IP. including the used bandwidth. It can only be queried by running the LST LOADEQ command. The table with the index 0 is the default one. If the reference for load balancing tables is not set for the adjacent node. The load of a path is calculated as follows: PathLoad = PortUsed ÷ PortAvailable x 100% where:    PathLoad refers to the load of the path. 6-6 . PortUsed and PortAvailable refer to the sum of used bandwidth and the sum of available bandwidth at these ports respectively. the default load balancing table applies. so as to improve the resource usage and user experience. PortAvailable refers to the total available bandwidth at the physical port. When the primary path for a type of service exists at more than one physical port. Each table contains primary path load thresholds and primary-to-secondary path load ratio thresholds. (Error! Unknown document property name.) Error! Unknown document property name. In addition. PortUsed refers to the total bandwidth of the admitted services at the physical port. Load balancing tables can be configured by running the ADD LOADEQ command.service is preferably admitted to the secondary path. The combination of a primary path load threshold and a path load ratio threshold can vary depending on the traffic type. The load balancing application policy is similar to the TRMMAP policy.or hybrid-IP-based Iub adjacent nodes by running the ADD ADJMAP or MOD ADJMAP command. Table 6-2 Default settings of load and load ratio thresholds for different types of service Threshold Primary path load threshold for common channel Primary-to-secondary path load ratio threshold for common channel Primary path load threshold for IMS SRB Primary-to-secondary path load ratio threshold for IMS SRB Primary path load threshold for SRB Primary-to-secondary path load ratio threshold for SRB Primary path load threshold for AMR voice Primary-to-secondary path load ratio threshold for AMR voice Primary path load threshold for R99 CS conversational Primary-to-secondary path load ratio threshold for R99 CS conversational Default Value 100 0 100 0 100 0 100 0 100 0 Issue Error! Unknown document property name. Table 6-2 lists the default settings of load and load ratio thresholds for different types of service. After the load balancing tables are configured.

) Error! Unknown document property name. (Error! Unknown document property name.Threshold Primary path load threshold for R99 CS streaming Primary-to-secondary path load ratio threshold for R99 CS streaming Primary path load threshold for R99 PS conversational Primary-to-secondary path load ratio threshold for R99 PS conversational Primary path load threshold for R99 PS streaming Primary-to-secondary path load ratio threshold for R99 PS streaming Primary path load threshold for R99 PS high-priority interactive Primary-to-secondary path load ratio threshold for R99 PS highpriority interactive Primary path load threshold for R99 PS medium-priority interactive Primary-to-secondary path load ratio threshold for R99 PS mediumpriority interactive Primary path load threshold for R99 PS low-priority interactive Primary-to-secondary path load ratio threshold for R99 PS lowpriority interactive Primary path load threshold for R99 PS background Primary-to-secondary path load ratio threshold for R99 PS background Primary path load threshold for HSDPA SRB Primary-to-secondary path load ratio threshold for HSDPA SRB Primary path load threshold for HSDPA IMS SRB Primary-to-secondary path load ratio threshold for HSDPA IMS SRB Primary path load threshold for HSDPA conversational Primary-to-secondary path load ratio threshold for HSDPA conversational Primary path load threshold for HSDPA streaming Primary-to-secondary path load ratio threshold for HSDPA streaming Primary path load threshold for HSDPA high-priority interactive Primary-to-secondary path load ratio threshold for HSDPA highpriority interactive Primary path load threshold for HSDPA medium-priority interactive Primary-to-secondary path load ratio threshold for HSDPA mediumpriority interactive Issue Error! Unknown document property name. Default Value 100 0 100 0 100 0 30 100 30 100 30 100 30 100 100 0 100 0 100 0 100 0 30 100 30 100 6-7 .

3.Threshold Primary path load threshold for HSDPA low-priority interactive Primary-to-secondary path load ratio threshold for HSDPA lowpriority interactive Primary path load threshold for HSDPA background Primary-to-secondary path load ratio threshold for HSDPA background Primary path load threshold for HSUPA SRB Primary-to-secondary path load ratio threshold for HSUPA SRB Primary path load threshold for HSUPA IMS SRB Primary-to-secondary path load ratio threshold for HSUPA IMS SRB Primary path load threshold for HSUPA conversational Primary-to-secondary path load ratio threshold for HSUPA conversational Primary path load threshold for HSUPA streaming Primary-to-secondary path load ratio threshold for HSUPA streaming Primary path load threshold for HSUPA high-priority interactive Primary-to-secondary path load ratio threshold for HSUPA highpriority interactive Primary path load threshold for HSUPA medium-priority interactive Primary-to-secondary path load ratio threshold for HSUPA mediumpriority interactive Primary path load threshold for HSUPA low-priority interactive Primary-to-secondary path load ratio threshold for HSUPA lowpriority interactive Primary path load threshold for HSUPA background Primary-to-secondary path load ratio threshold for HSUPA background Default Value 30 100 30 100 100 0 100 0 100 0 100 0 30 100 30 100 30 100 30 100 6. then the admission to the non-preferred path is performed. (Error! Unknown document property name. the RNC calculates the load of the primary and secondary paths and then determines whether to select the primary or secondary path as the preferred path for admission based on the settings of the primary path load threshold and primary-to-secondary path load ratio threshold.3 Admission Procedure Primary and secondary paths are used in admission control. see chapter 5 "TRM Mapping. If the admission to the preferred path fails." Issue Error! Unknown document property name. According to the mapping from traffic types to transmission resources.) Error! Unknown document property name. 6-8 . For details about the mapping from traffic types to transmission resources.

the user then attempts to be admitted to available bandwidth 2 on the secondary path. ----End Issue Error! Unknown document property name. Step 2 If the user succeeds in applying for the resources on the primary path. the bandwidth admission request of the user is rejected. the user then attempts to be admitted to available bandwidth 2 on the secondary path. The admission procedure for a new user is as follows: Step 1 The new user attempts to be admitted to available bandwidth 1 on the primary path. Step 4 If the user succeeds in applying for the resources on the secondary path. the user is admitted to the secondary path. handover of users. as shown in Figure 6-1. ----End Figure 6-1 Admission procedure for a new user Available bandwidth 1 = Total bandwidth of the primary path – Used bandwidth – Bandwidth reserved for handover Available bandwidth 2 = Total bandwidth of the secondary path – Used bandwidth – Bandwidth reserved for handover The admission procedure for handover of a user is as follows: Step 1 The user attempts to be admitted to available bandwidth 1 on the primary path. as shown in Figure 6-2. Step 4 If the user succeeds in applying for the resources on the secondary path. (Error! Unknown document property name. Step 2 If the user succeeds in applying for the resources on the primary path. the user is admitted to the primary path. Step 3 If the user fails to apply for the resources on the primary path. the user is admitted to the secondary path. as shown in Figure 6-2. The following procedures describe the admission of these users on the Iub interface respectively. 6-9 .For example. If the user fails. assume that secondary paths are available for new users. the user is admitted to the primary path. and rate upsizing of users and that the RNC selects primary paths as preferred paths for admission of the new users and handover of users (the procedures of admission with secondary paths preferred are the same). Step 3 If the user fails to apply for the resources on the primary path. If the user fails. as shown in Figure 6-1. the bandwidth admission request of the user is rejected.) Error! Unknown document property name.

the rate upsizing of the user fails. it attempts to be admitted to the non-preferred path (that is. Otherwise. Step 2 If the rate upsizing on the bearing path is successful. the user attempts to be admitted to available bandwidth 2 on the preferred path (that is.Used bandwidth The admission procedure for rate upsizing of a user is as follows: Step 1 The user attempts to be admitted to available bandwidth 1 on the bearing path of the user (that is. as shown in Figure 6-3. the primary path in this example). (Error! Unknown document property name. the secondary path in this example. Step 5 If the rate upsizing on the non-preferred path is successful.Used bandwidth Available bandwidth 2 = Total bandwidth of the secondary path . If the user fails. another primary path in this example). as shown in Figure 6-3. the traffic of the user is still carried on the path. as determined by the load balancing algorithm). Step 4 If the user succeeds in applying for the resources on the preferred path. 6-10 .) Error! Unknown document property name. the user is admitted to the preferred path. Step 3 If the rate upsizing on the bearing path fails.Figure 6-2 Admission procedure for handover of a user Available bandwidth 1 = Total bandwidth of the primary path . ----End Figure 6-3 Admission procedure for rate upsizing of a user Available bandwidth 1 = Total bandwidth of the primary path – Used bandwidth – Bandwidth reserved against congestion Available bandwidth 2 = Total bandwidth of the secondary path – Used bandwidth – Bandwidth reserved against congestion Issue Error! Unknown document property name. the user is admitted to the nonpreferred path.

the admission is performed only on the primary paths.  Congestion resolving parameters: − − FWDCONGCLRBW BWDCONGCLRBW These two parameters are used to determine whether the congestion is resolved.NOTE If no secondary paths are available for the users. 6. modification. Iub resources.5 Load Reshuffling and Overload Control When the usage of cell resources exceeds the basic-congestion threshold.4 Intelligent Access Control Intelligent Access Control (IAC) is aimed at improving the access success rate. For details about other resources. CAC.1 Iub Congestion Detection For a path. the following congestion-related parameters are applicable:  Congestion detection parameters: − − FWDCONGBW BWDCONGBW The default values of the two parameters are 0. see the Load Control Parameter Description. see the Load Control Parameter Description. TRM performs congestion detection according to the settings. and Directed Retry Decision (DRD). pre-emption. port. or resource group. If the parameters are set to values other than 0. which indicates that no congestion detection will be performed. This section describes only the Iub resources. 6. and NodeB credit resource. LDR involves the following algorithms:    Iub Congestion Detection Iub Overload Detection Congestion and Overload Handling 6.5. Load Reshuffling (LDR) is required to reduce the cell load and increase the access success rate. Congestion detection can be triggered in any of the following conditions:    Bandwidth adjustment because of resource allocation. In this case. 6-11 . IAC involves the following procedures: rate negotiation. For details about IAC. (Error! Unknown document property name. or release Change in the configured bandwidth or the congestion threshold Fault in the physical link Assume that the forward parameters of a port for congestion detection are defined as follows: Issue Error! Unknown document property name. the cell enters the basic congestion state. The following four resources can trigger the basic congestion of a cell: power resource. code resource. queuing.) Error! Unknown document property name.

Then. The congestion detection for a path or a resource group is similar to that for a port. OLC triggers release of resources used by users in order of comprehensive priority. If ATM LPs or IP LPs are configured. If different types of AAL2 paths or IP paths require different congestion thresholds. (Error! Unknown document property name. overload occurs when USED > AVE. congestion control is also applicable to the LPs. 6-12 . For example: Assume the available bandwidth at a port as AVE and the used bandwidth at the port as USED.) Error! Unknown document property name. resource groups. Generally. After the RNC receives an overload message. see the Load Control Parameter Description.3 Congestion and Overload Handling Handling on the Iub Interface If IUB_LDR under the NodeBLdcAlgoSwitch parameter is set to 1 by running the ADD NODEBALGOPARA or MOD NODEBALGOPARA command. the RNC triggers LDR actions. the associated parameters need to be set for the paths as required. Some links in an IP MLPPP group are faulty. the available ADSL bandwidth deteriorates abruptly. In ADSL networking scenario. the mechanism of congestion detection for the port is as follows:   Congestion occurs on the port when CON + USED ≥ AVE. 6. for example.) Used bandwidth: USED Then. and ports. 6. and thus the available bandwidth of the group decreases. an IMA group contains multiple E1s.    Configured bandwidth: AVE Forward congestion threshold: CON Forward congestion resolving threshold: CLEAR (Note that CLEAR is greater than CON.5.5. the RNC triggers Overload Control (OLC) actions.   After the RNC receives a congestion message. overload detection is applicable to paths. among which some E1s are broken whereas others work properly. from 8 Mbit/s to 1 Mbit/s. and thus the available bandwidth of the group decreases. Some links in a link aggregation group are faulty. Issue Error! Unknown document property name. Similar to congestion detection. Congestion disappears from the port when CLEAR + USED < AVE. For details about the LDR actions. congestion thresholds need to be set for only ports or resource groups.2 Iub Overload Detection Overload can be triggered in any of the following conditions:     In ATM IMA networking scenario. The congestion detection mechanism for the LPs is the same as that for resource groups.

the congested state is reported to the RANAP subsystem of the RNC. During Iu signaling flow control. if congestion is detected on the signaling link towards the signaling point. For details about SRNS relocation. 6-13 .) Error! Unknown document property name.  Issue Error! Unknown document property name. the RANAP subsystem discards user messages in the following sequence: short message service > CS and PS call > registration. (Error! Unknown document property name. see the SRNS Relocation Parameter Description. Then.Handling on Other Interfaces  The congestion on the Iur interface can trigger Serving Radio Network Subsystem (SRNS) relocation.

Congestion control: controls the transmission rate of the NRT service. which guarantees fairness between the ports. Each port performs the shaping function. prevents congestion due to packet loss on the Iub interface.7     User Plane Processing 7. That is. It does not involve the actual processing procedure.1 Overview of User Plane Processing The load control algorithm described in the previous chapter is based on the bandwidth reserved for services. Scheduling is performed to guarantee fairness between NodeBs in the convergence scenario. the hub LP performs scheduling of the ports contained in the hub LP so that the total transmission rate of all the ports does not exceed the bandwidth configured for the hub LP. In addition. the scheduling rate of a port is in direct proportion to the load of the port. This prevents congestion and packet loss at the hub node. The hub LP performs the scheduling function. Shaping is performed to control the total transmission rate of the RNC and NodeB to prevent congestion on the transport network. 7.2 Hub Scheduling and Shaping Hub scheduling and shaping consists of RNC scheduling and shaping and NodeB scheduling and shaping. 7-1 . Shaping refers to Logical Port (LP) shaping. It consists of the following contents: Hub scheduling and shaping: consists of RNC scheduling and shaping and NodeB scheduling and shaping. Efficiency improvement: improves the transmission efficiency on the Iub interface by reducing the transmission bandwidth for services. IP Performance Management (PM): detects that the available bandwidth is provided for shaping and admission algorithms in IP transport mode. and provides differentiated services.2.1 RNC Scheduling and Shaping The RNC performs scheduling and shaping of user plane data in the downlink direction.) Error! Unknown document property name. 7. Issue Error! Unknown document property name. (Error! Unknown document property name. This chapter describes the algorithm for user plane processing. The total data transmission rate does not exceed the bandwidth configured for the port.

3 Congestion Control of Iub User Plane Iub congestion control is only applied to the NRT service. The details are as follows:  Service-to-SPI mapping: Based on the TC. Each LP performs the shaping function. The RNC notifies the NodeB of the SPI corresponding to each service through the NBAP signaling. Therefore. The PVCs with high priority are dispatched preferentially. you also need to adopt the congestion control algorithm of the user plane to control the resource consumption for the NRT service. ARP. in addition to the admission control algorithm. (Error! Unknown document property name. The PVCs with the same priority are dispatched on the basis of the services carried on the PVCs.  Requirement of differentiated NRT services: The bandwidth resources are allocated among NRT services by proportion based on the service priorities (including service type. 7-2  Issue Error! Unknown document property name. Therefore. the congestion control algorithm must be adopted to control the total transmission rate on the Iub interface to prevent congestion and packet loss and to improve the bandwidth efficiency. and THP. THP.7. Differentiated resource allocation: When the resources on the air interface are limited. Error! Unknown document property name. The mapping is configured on the RNC. Scheduling in IP transport mode: When there are multiple LPs.  Except to guarantee the total bandwidth efficiency. thus seriously affecting the bandwidth efficiency on the Iub interface. Iub congestion control is performed to control the transmission rate of the NRT service. The NRT service flow fluctuates significantly.  The RT service flow is stable. see the HSPA Parameter Description. The HSPA scheduling algorithm (including HSDPA and HSUPA scheduling algorithms) implements differentiated services on the air interface. As a result. and radio bearer type) in the case that the GBR of NRT services is guaranteed. the HSPA scheduling algorithm allocates the total resources among users based on the SPI weighting factors. For details on SPI mapping. The fluctuation of the NRT service flow may cause the data flow to be sent on the Iub interface to exceed the actual available bandwidth. congestion and packet loss occur. and the corresponding SPI weighting factors are configured. the IP physical port performs Round Robin (RR) scheduling of all the LPs to guarantee fairness between the LPs. and the demand for resources is relatively regular. Thus. the congestion control algorithm is applied to meet the requirement of differentiated NRT services.  7. The scheduling function is described as follows:  Scheduling in ATM transport mode: When there are multiple LPs or the hub NodeB needs to transmit the uplink data of the lower-level NodeB. The total data transmission rate does not exceed the bandwidth configured for the LP.2 NodeB Scheduling and Shaping The NodeB performs scheduling and shaping of user plane data in the uplink direction.2.) . the load control algorithm is usually adopted to control the resource consumption for the RT service. the physical port performs scheduling of all the PVCs. ARP. one service is mapped to SPI.

the bandwidth is allocated by proportion based on the SPI weighting factors in the case that the GBR of the service is guaranteed. which are described in Table 7-1. 7-3 . the shaping algorithm is also required. that is. including HSPA and R99 services. The downlink Iub congestion control algorithm is implemented in the RNC. The Iub congestion control algorithm is applied only to the NRT services.1 Overview of the Downlink Iub Congestion Control Algorithm The downlink congestion control algorithms are of four types. and SPI weighting factors are set for R99 services.. The HSPA scheduling algorithm is implemented in the NodeB. RLC AM mode HSDPA service R99 service.To implement differentiated services in the same way. R99 services adopt the same service-to-SPI mapping mechanism as that of HSPA services. For packet loss at the transport layer. (Error! Unknown document property name.4 Downlink Iub Congestion Control Algorithm 7. The differences are as follows:   The HSPA scheduling algorithm is applied to all the HSPA services except R99 services. Table 7-1 Downlink congestion control algorithms Congestion Control Algorithm RNC RLC retransmission ratebased congestion control algorithm NodeB HSDPA adaptive flow control algorithm RNC backpressure-based downlink congestion control algorithm Scenario All networking scenarios Service Type R99 service. Issue Error! Unknown document property name.  The Iub congestion control algorithm must be implemented in the uplink and downlink directions. HSDPA service. The uplink Iub congestion control algorithm is implemented on the NodeB side.4. HSDPA NRT service All networking scenarios Congestion and packet loss in the RNC. the Iub congestion control algorithm also uses SPI weighting factors for implementing differentiated services on the Iub interface.) Error! Unknown document property name. It consists of the following algorithms:        RLC (Radio Link Control) retransmission rate-based downlink congestion control algorithm Backpressure-based downlink congestion control algorithm NodeB HSDPA-based adaptive downlink flow control R99 single service downlink congestion control algorithm NodeB backpressure-based uplink congestion control algorithm Transport layer uplink congestion control algorithm R99 single service uplink congestion control algorithm 7.

The R99 single service congestion control algorithm monitors packet loss and reduces the rate only when congestion occurs on the transport network. it has no impact on the backpressure-based congestion control algorithm. In the IP transport scenario. the IP PM is enabled if it is supported. and the backpressurebased congestion control algorithm is implemented in the RNC. Therefore.  Relation between the RNC backpressure-based congestion control algorithm and the RNC R99 single service congestion control algorithm − − Both the algorithms are implemented in the RNC. The relations between the four downlink congestion control algorithms are as follows:  Relation between the RNC backpressure-based congestion control algorithm and the RNC RLC retransmission rate-based congestion control algorithm − − Both the algorithms are implemented in the RNC. Therefore. when the R99 single service congestion control algorithm takes effect. Therefore. then the two algorithms do not conflict in the case that backpressure takes effect. Therefore. they may take effect simultaneously. (Error! Unknown document property name.  Relation between the NodeB HSDPA flow control algorithm and the RNC backpressurebased congestion control algorithm The HSDPA flow control algorithm is implemented in the NodeB. 7-4 Issue Error! Unknown document property name. The R99 single service congestion control algorithm can take the place of the RLC retransmission rate-based congestion control algorithm.Congestion Control Algorithm RNC R99 single service downlink congestion control algorithm Scenario All networking scenarios Service Type R99 service The recommended configurations for the downlink congestion control algorithms are as follows:    The RLC retransmission rate-based congestion control algorithm switch is disabled. It serves as the supplement in the case that backpressure does not take effect. Therefore. the RLC retransmission rate-based congestion control algorithm switch is disabled automatically. the RLC retransmission ratebased congestion control algorithm can be disabled. they may take effect simultaneously. When the backpressure-based congestion control algorithm switch of a service is enabled. they may take effect simultaneously. the backpressure-based congestion control algorithm ensures that no packet loss occurs in the RNC.) . − If the NodeB HSDPA flow control algorithm switch is set to NO_BW_SHAPING. In the convergence scenario. The Error! Unknown document property name.  Relation between the RNC R99 single service congestion control algorithm and the RNC RLC retransmission rate-based congestion control algorithm − − Both the algorithms are implemented in the RNC. In the case that backpressure takes effect. Therefore. the multiple-level LPs are configured if the configuration of multiple-level LPs is supported. Other algorithm switches are enabled. they may take effect simultaneously.

and set the DRA_R99_DL_FLOW_CONTROL_SWITCH subparameter of DraSwitch to On. The algorithm is implemented as follows: Issue Error! Unknown document property name. the RLC retransmission rate-based congestion control algorithm of the HSDPA service is not used. use the SET CORRMALGOSWITCH command. and the other is applied to HSDPA services. and the R99 single service congestion control algorithm is implemented in the RNC.2 RNC RLC Retransmission Rate-Based Downlink Congestion Control Algorithm The RNC RLC retransmission rate-based downlink congestion control algorithm is implemented in the RNC. −  Relation between the NodeB HSDPA flow control algorithm and the RNC R99 single service congestion control algorithm − The HSDPA flow control algorithm is implemented in the NodeB. The prerequisites for implementing the algorithm are as follows:   For the R99 BE service. Therefore.) Error! Unknown document property name. Based on the RLC retransmission rate. They do not conflict. Therefore. Therefore.congestion problem on the Iub interface cannot be solved in the case that backpressure does not take effect. The R99 single service congestion control algorithm aids the NodeB HSDPA flow control algorithm in solving flow control problems of R99 services. −  Relation between the NodeB HSDPA flow control algorithm and the RNC RLC retransmission rate-based congestion control algorithm − The NodeB HSDPA flow control algorithm is excellent. and set the DRA_HSDPA_DL_FLOW_CONTROL_SWITCH subparameter of DraSwitch to On. then the NodeB flow control policy is automatically set to DYNAMIC_BW_SHAPING and can independently solve the congestion problem of HSDPA users in the case that backpressure does not take effect. − 7. it solves the downlink congestion problems of R99 and HSDPA NRT services. It is applied to all the Iub interface boards. When both the algorithms take effect simultaneously. they may take effect simultaneously. one is applied to R99 services. The NodeB HSDPA flow control algorithm can independently solve the congestion problem of HSDPA users on the Iub interface in the case that backpressure does not take effect.4. Generally. the rate of HSDPA services is reduced till the rate reaches the minimum value. use the SET CORRMALGOSWITCH command. then the two algorithms conflict in the case that backpressure takes effect. 7-5 . They do not conflict with each other. (Error! Unknown document property name. − If the NodeB HSDPA flow control algorithm switch is set to DYNAMIC_BW_SHAPING. The NodeB flow control policy is automatically set to NO_BW_SHAPING in the case that backpressure takes effect. the priority of R99 services is higher than that of HSDPA services. the RLC retransmission rate-based congestion control algorithm takes effect to limit the rate of R99 services. and the other is applied to HSDPA services. one is applied to R99 services. If the NodeB HSDPA flow control algorithm switch is set to BW_SHAPING_ONOFF_TOGGLE. For the HSDPA BE service. In this case. When both the algorithms take effect simultaneously.

Step 3 When the retransmission rate is lower than EventBThred in a specified continuous period (TimeToTriggerB x MoniterPrd ). there is a waiting period (PendingTimeA x MoniterPrd ). The procedure for flow control algorithm 1 of the BE service is shown in Figure 7-1. The monitoring period is specified by the MoniterPrd parameter.   For the R99 BE service. In this period. 7-6 . the RNC increases the current transmission rate by 130%. After event A is triggered. Issue Error! Unknown document property name.5 Step 2 When the retransmission rate is higher than EventAThred in a specified continuous period (TimeToTriggerA x MoniterPrd ). The RNC calculates the retransmission rate according to the following formula: Fn = (1 – a) x Fm + a x Mn      Fn: retransmission rate to be calculated Fm: previously calculated retransmission rate n=m+1 Mn: currently measured retransmission rate a = 0. there is a waiting period (PendingTimeB x MoniterPrd ). the RNC stops monitoring the retransmission rate. the RNC increases the current transmission rate by 130%. In this period.   For the R99 BE service. the RNC reduces the current transmission rate by 50%. event B is triggered. the RNC stops monitoring the retransmission rate. For the HSDPA BE service.Step 1 The RNC initiates periodic monitoring of the RLC PDU retransmission rate. (Error! Unknown document property name. For the HSDPA BE service. After event B is triggered. the RNC reduces the current transmission rate by 50%. event A is triggered.) Error! Unknown document property name.

as shown in Figure 7-2. Figure 7-2 BE service flow control in the case of Iub congestion ----End Issue Error! Unknown document property name. the transmission rate of the RNC matches the bandwidth on the Iub interface. 7-7 .) Error! Unknown document property name. (Error! Unknown document property name.Figure 7-1 Procedure for flow control algorithm 1 of the BE service Through flow control algorithm 1.

and DROPPKTTHD5. and the IP interface board has six queues.) Error! Unknown document property name. Therefore. the setting of FLOWCTRLSWITCH is based on the ports. (Error! Unknown document property name. the number of queues with absolute priorities can be set through the PQNUM parameter. MLPPP group.7. and Ethernet port. the RNC starts discarding data packets from the buffer. Step 2 When the buffer length of a queue is greater than the congestion threshold. DROPPKTTHD4. The interface boards send congestion signals to the DPUb boards concerned. the queue enters the congestion state. CONGTHD3. 7-8 . The port is recovered if all the queues on the port leave the Issue Error! Unknown document property name. For the IP network. DROPPKTTHD3. fractional link. CONGTHD2. For the IP interface board. DROPPKTTHD1. It is applied to downlink congestion of R99 and HSDPA NRT services. the ports are the UNI link. The congestion thresholds are CONGTHD0. The following functions require corresponding licenses: − − − ATM Iub overbooking: used for the ATM non-hub network Hub Iub overbooking: used for the ATM hub network IP Iub overbooking: used for the IP network  The algorithm switch must be enabled. The RR scheduling is performed according to the sequence of the queues and then the sequence of the tasks. and optical port. The length of packets discarded from the queue is equal to the packet discarding threshold minus the congestion threshold. PPP link.4. When a queue on the port is congested. the ports are the LP. IMA group. LP.  Step 4 When the buffer length of the queue is smaller than the congestion recovery threshold. optical port. CONGTHD1. The prerequisites for implementing the algorithm are as follows:  This algorithm is based on backpressure flow control of the interface board. The scheduling of queues with absolute priorities depends on the priorities of special users. and the FCINDEX parameter together with the thresholds is used for port flow control. the port becomes congested accordingly. DROPPKTTHD2. the queue leaves the congestion state. Step 3 When the buffer length of the queue is greater than the packet discarding threshold. The algorithm is implemented as follows: Step 1 The interface boards monitor the transmission buffers of the queues on the Iub interface.3 RNC Backpressure-Based Downlink Congestion Control Algorithm The RNC backpressure-based downlink congestion control algorithm is implemented in the RNC. and CONGTHD5. and the Iub overbooking feature must be activated. The FLOWCTRLSWITCH parameter is set to ON. The ATM interface board has five queues. The rest queues use the RR scheduling algorithm. CONGTHD4. The DPUb boards reduce the transmission rate of the BE service to GBR x 10%. The license must be obtained according to different network modes.  The packet discarding thresholds are DROPPKTTHD0. − − For the ATM network. The number of rest queues is equal to 6 minus the value of PQNUM.

(Error! Unknown document property name. CONGCLRTHD3. The interface boards send congestion resolving signals to the associated DPUb boards. and the step is doubled at intervals of 200 ms.  The recovery thresholds are CONGCLRTHD0.  Step 5 After the BE users leave the congestion state. and CONGCLRTHD5. CONGCLRTHD4. The initial increasing step of the transmission rate is 2. the RNC increases the transmission rate every 10 ms according to the increasing step until the BE users reach the Maximum Bit Rate (MBR). where r is the final transmission rate of the user before the user enters the congestion state.4 RNC R99 Single Service Downlink Congestion Control Algorithm The RNC R99 single service downlink congestion control algorithm is implemented in the RNC. CONGCLRTHD1. The value of MBR is carried on the Radio Access Bearer (RAB) from the Core Network (CN).) Error! Unknown document property name. CONGCLRTHD2. and the DPUb boards restore the transmission rate of BE users on the port. The RNC extends the node synchronization frame to detect congestion in R99 service Issue Error! Unknown document property name. 7-9 .4. Figure 7-3 Result of flow control algorithm 2 for the BE service The other parameters used in flow control algorithm 2 are as follows:      TrafficClass UserPriority THP SPI BearType 7.000 bit/s x SPI. The restored rate is r x 95%. ----End The result of flow control algorithm 2 for the BE service is shown in Figure 7-3.congestion state.

5 NodeB HSDPA Adaptive Flow Control Algorithm The NodeB HSDPA adaptive flow control algorithm is implemented in the NodeB. The algorithm is implemented as follows: Step 1 The RNC measures the number of FP packets in real time and sends the downlink node synchronization frame once a second to implement congestion detection based on the downlink node synchronization frame. Therefore. IMS. Step 4 The RNC increases the L2 transmission rate by a certain step every 1. The flow control algorithm solves the Iub congestion problems of HSDPA users in various scenarios. the RNC sends data by using the leaky bucket algorithm. The prerequisite for implementing the algorithm is that the DLR99CONGCTRLSWITCH parameter is set to ON. Step 2 The NodeB measures the number of received FP packets in real time. Step 5 After obtaining the L2 transmission rate. VoIP. which may lead to congestion on the Iub interface. The rate fluctuates considerably. and then generates an uplink node synchronization frame and sends it to the RNC. When the data burst occurs. Error! Unknown document property name. The downlink node synchronization frame contains the PM packet sequence number and the number of FP packets sent by the RNC (excluding the number of control frames). fills the number of FP packets in the received downlink node synchronization frame. The flow control policy is not used for the SRB. and the step is doubled at intervals of 20s. It is applied to the MAC-hs queues of the BE service and streaming service of HSDPA users. the RNC reduces the L2 transmission rate by a certain percentage to a rate not smaller than the GBR. ----End 7.    The BE service is less sensitive to delay. 7-10 Issue Error! Unknown document property name. The initial increasing step of the transmission rate is 2. or CS AMR service of HSDPA users because the amount of data is small and the services are sensitive to delay. When the NodeB MAC-hs flow control entity distributes flow to the users. the RNC sends the user MBR to the NodeB.000 bit/s x SPI. The rate of the steaming service is relatively high.transport and thus controls the transmission rate of the downlink R99 service. the flow control problems of the R99 service can be solved.4. Step 3 If the RNC detects frame loss and congestion of the downlink R99 service after receiving the uplink node synchronization frame and does not reduce the L2 transmission rate in a period of time. (Error! Unknown document property name.5s to a rate not greater than the MBR. the rate does not exceed the MBR.) . The RNC adopts the policy of reducing rate by proportion and increasing rate by absolute rate to ensure fairness and to implement differentiated services. The prerequisites for implementing the algorithm are as follows:  The HSDPA MBR reporting switch is set as follows: − When the switch is set to ON. the rate may become very high.

the NodeB does not adjust the bandwidth based on the delay and packet loss condition on the Iub interface. 7-11 . and then the RNC performs bandwidth allocation. When the switch is set to BW_SHAPING_ONOFF_TOGGLE. The algorithm architecture is shown in Figure 7-4. NOTE This switch is not configurable. Issue Error! Unknown document property name. Then. (Error! Unknown document property name. the Iub MBR reporting function is disabled.  The NodeB Iub flow control algorithm switch Switch is set as follows: − When the switch is set to DYNAMIC_BW_SHAPING. If the NodeB detects no congestion. − − This section describes the flow control policy used when Switch is set to BW_SHAPING_ONOFF_TOGGLE. the flow control policy for the ports of the NodeB is either DYNAMIC_BW_SHAPING or NO_BW_SHAPING in accordance with the congestion detection mechanism of the NodeB. When the switch is set to NO_BW_SHAPING.) Error! Unknown document property name.− When the switch is set to OFF. The NodeB reports the conditions on the air interface to the RNC. Figure 7-4 Dynamic flow control algorithm architecture The algorithm is implemented as follows: Step 1 The congestion status of the transport network is reported to the NodeB through the DRT and FSN. the NodeB adjusts the available bandwidth for HSDPA users based on the delay and packet loss condition on the Iub interface. the NodeB performs Iub shaping and distributes flow to HSDPA users. It is set to ON by default. it increases the HSDPA Iub bandwidth. The NodeB monitors transmission delay and packet loss periodically. considering the rate on the air interface.

the Iub bandwidth adaptive algorithm and flow shaping are enabled. it continues with the delay detection and the algorithm switch is set to DYNAMIC_BW_SHAPING. no congestion due to delay occurs. The Iub delay congestion threshold is specified by TD. In this way. Step 4 Based on the capacity allocated on the Uu interface. and slow changes in the bandwidth of transport networks. hub convergence. flow shaping is disabled. and overload is prevented.1 Overview of the Uplink Iub Congestion Control Algorithm The uplink congestion control algorithms are of four types. The adjusted bandwidth is the input for the Iub shaping function of the NodeB. no congestion due to packet loss occurs. Step 2 The NodeB adjusts the HSDPA Iub bandwidth based on the congestion due to delay and packet loss. Step 3 The NodeB allocates capacity to MAC-hs based on the rate on the Uu interface. the NodeB allocates the Iub bandwidth to HSDPA users and performs Iub shaping to ensure that the total flow of all the queues does not exceed the available Iub bandwidth.    The Iub frame loss rate threshold is specified by DR. Iub interface utilization is improved. That is. 7-12 . which are described in Table 7-2. it stops the delay detection and the algorithm switch is set to NO_BW_SHAPING. (Error! Unknown document property name. If the NodeB detects no congestion in a period of time. ----End 7.) Error! Unknown document property name. skip this step. Step 5 The RNC limits the bandwidth for each MAC-hs queue based on the HS-DSCH capacity allocation result. If the Iub shaping function of the NodeB is disabled. If the NodeB detects congestion due to packet loss. That is.5. The allocated capacity does not exceed the MBR. All networking scenarios Service Type R99 service and HSUPA service R99 service and HSUPA service RNC R99 single service uplink congestion control algorithm R99 service Issue Error! Unknown document property name. and the NodeB boards support the algorithm. If the detected frame loss rate is lower than the threshold. Iub interface congestion is controlled. If the detected delay is lower than the threshold. Table 7-2 Uplink congestion control algorithms Congestion Control Algorithm NodeB backpressure-based uplink congestion control algorithm NodeB uplink bandwidth adaptive adjustment algorithm Scenario The available bandwidth for LPs is known.5 Uplink Iub Congestion Control Algorithm 7. The bandwidth of various transport networks is unknown or the scenarios include ATM convergence.

The RNC R99 single service uplink congestion control algorithm is implemented in the RNC. Issue Error! Unknown document property name. The relations between the four uplink congestion control algorithms are as follows:  The NodeB backpressure-based uplink congestion control algorithm and the NodeB uplink bandwidth adaptive adjustment algorithm are implemented in the NodeB. the RNC R99 single service uplink congestion control algorithm independently controls the transmission rate of UEs based on the FP congestion detection results. The policy of reducing rate by proportion and increasing rate by absolute rate is adopted to ensure fairness between BE services. The result (available bandwidth for LPs) of the NodeB uplink bandwidth adaptive adjustment algorithm is the input for the NodeB backpressure-based uplink congestion control algorithm. They do not conflict with each other.5. NOTE The switch of this algorithm is not configurable. These three algorithms may take effect simultaneously. Otherwise. If the NodeB supports the NodeB backpressure-based uplink congestion control algorithm and the NodeB uplink bandwidth adaptive adjustment algorithm.2 NodeB Backpressure-Based Uplink Congestion Control Algorithm (R99 and HSUPA) The NodeB backpressure-based uplink congestion control algorithm is implemented in the NodeB to ensure that there is no congestion due to packet loss in the NodeB. This is the main scheme of the uplink flow control algorithm. (Error! Unknown document property name. both the algorithms can be used together to solve the uplink Iub congestion problems (in direct connection and convergence scenarios). the NodeB cross-Iur single HSUPA service uplink congestion control algorithm can solve the packet loss problem due to Iur interface congestion for HSUPA users.) Error! Unknown document property name. It is set to ON by default. 7-13 . In the IP transport scenario. the RNC R99 single service uplink congestion control algorithm can control the transmission rate of UEs based on the backpressure flow control and rate limiting results. If the NodeB boards support the NodeB uplink bandwidth adaptive adjustment algorithm and the NodeB backpressure-based uplink congestion control algorithm.    7. the IP PM is enabled if it is supported. Figure 7-5 shows the principle of the NodeB backpressure-based congestion control algorithm. If the NodeB supports the NodeB backpressure-based uplink congestion control algorithm and the NodeB uplink bandwidth adaptive adjustment algorithm.Congestion Control Algorithm NodeB cross-Iur single HSUPA service uplink congestion control algorithm Scenario Iur congestion scenario Service Type HSUPA service The recommended configurations for the uplink congestion control algorithms are as follows:   All the algorithm switches are enabled.

Step 3 When the buffer data volume of the LPs and queues is smaller than the congestion recovery threshold.Figure 7-5 Principle of the NodeB backpressure-based uplink congestion control algorithm The algorithm is implemented as follows: Step 1 The interface boards monitor the transmission buffers of the LPs and queues on the Iub interface. (Error! Unknown document property name. Step 2 When the buffer data volume on the decoding DSP is larger than a certain threshold. all queues are congested. the interface boards send congestion signals to the DSP concerned. For R99 users. If no congestion is detected on the port. some data packets in the buffer are discarded. − − If congestion is detected on the port.  For ATM transport or IP transport based on the V1 platform: The algorithm must calculate a virtual buffer data volume and check whether congestion occurs because LP shaping is not supported. Issue Error! Unknown document property name. the data can be buffered in the decoding DSP for 500 ms and will be discarded after 500 ms. The transmission rate is limited but is not lower than the GBR. the data can be buffered in the decoding DSP for 60 ms and will be discarded after 60 ms. All the BE users on the DSP enter the congestion state. the status of the queues must be checked on the basis of the buffer data of the queues. the rates of all the BE users on the port are reduced.   For HSUPA users.) Error! Unknown document property name. The interface boards send the congestion resolving signals to the DSP concerned. If congestion is detected on the port. the decoding DSP increases the transmission rate by a certain step every 10 ms until the transmission rate of the BE users reaches the MBR. congestion is resolved. When congestion is detected.  For IP transport based on the V2 platform: The algorithm directly checks whether congestion occurs on the port based on the actually measured buffer usage on the port because LP shaping is supported. and the transmission rates are restored. Step 4 After the BE users leave the congestion state. The BE users on the port leave the congestion state. 7-14 .

Figure 7-6 Frame structure of the congestion indication on the transport network Congestion Status indicates the congestion status of the transport network. it reduces the exit bandwidth of the LP by a certain step.5. the NodeB adjusts the exit bandwidth on the NodeB side according to the following principles:  If the NodeB receives the congestion indication in which the value of Congestion Status is 2 or 3 in a measurement period. The NodeB uplink bandwidth adaptive adjustment algorithm automatically monitors congestion on the transport network and adjusts the maximum available bandwidth on the Iub interface. It is set to ON by default. which is used for the NodeB to perform cross-Iur flow control for HSUPA users. the bandwidth configured by the NodeB may be much greater than the available bandwidth on the transport network. ----End 7. The frame structure of the congestion indication is shown in Figure 7-6. (Error! Unknown document property name. 7-15 Issue Error! Unknown document property name. Algorithm for ATM Transport The RNC monitors congestion due to delay and frame loss based on the packet transmission time specified in the Spare Extension field in the FP frame and the number of FP packets sent by the NodeB. and the step is doubled at intervals of 200 ms. The adjustment result is the input for the NodeB backpressure-based congestion control algorithm. the RNC returns the congestion indication according to the congestion detection result. Error! Unknown document property name.000 bit/s x SPI.The initial increasing step of the transmission rate is 2. At the same time. Then.3 NodeB Uplink Bandwidth Adaptive Adjustment Algorithm The NodeB uplink bandwidth adaptive adjustment algorithm is implemented in the NodeB. Therefore. Considering the difference between ATM transport and IP transport.) . this algorithm is also called transport network congestion control algorithm. Its values are as follows:     0: no TNL congestion 1: reserved for future use 2: TNL congestion detected by delay build-up 3: TNL congestion detected by frame loss After receiving the non-cross-Iur congestion indication periodically measured on each LP. two types of algorithms are available. The hybrid service may consider the buffer conditions of several services on the decoding DSP. Step 5 The buffer data volume on the decoding DSP is the input for scheduling. the cross-Iur indication is added to the congestion indication. In the scenario of network convergence or hub NodeB. NOTE The switch of this algorithm is not configurable.

4 RNC R99 Single Service Uplink Congestion Control Algorithm The RNC R99 single service uplink congestion control algorithm monitors congestion by monitoring end-to-end packet loss (from the NodeB to the RNC) for each DCH FP at the FP layer. the rate cannot be reduced. Then. ----End Issue Error! Unknown document property name.  If the FP of a service of a user detects the uplink R99 congestion due to frame loss. the rate reducing period timer and the congestion recovery timer are started. The algorithm is implemented as follows: Step 1 The uplink DCH data frame is extended to implement FP-based uplink congestion detection. the NodeB directly obtains the congestion status of the transport network according to the IP PM result without using the congestion indication from the RNC. total number of FP packets sent by the decoding DSP (including data packets discarded from the buffer of the decoding DSP). − If the rate reducing period timer expires. and the changed exit bandwidth does not exceed the configured bandwidth. the congestion recovery timer is restarted. The rate is not lower than the GBR. − Step 3 If the congestion recovery timer expires and the current rate of the user does not reach the MBR. Algorithm for IP Transport For IP transport. Then. PM packet transmission time. If the rate reducing period timer does not expire. NOTE The switch of this algorithm is not configurable. the NodeB increases the exit bandwidth of the LP by a certain step. the RNC increases the rate by a level and notifies the UE through the TFC CONTROL signaling.5.) Error! Unknown document property name. the NodeB increases the exit bandwidth of the LP by a certain step. the NodeB adjusts the exit bandwidth according to the following principles:   If the NodeB detects congestion due to frame loss or delay in a measurement period. and the changed exit bandwidth does not exceed the configured bandwidth. the RNC reduces the rate of the uplink service by a level and notifies the UE through the TFC Control signaling. the RNC controls the transmission rate of UEs through the RRC signaling TFC Control. and total number of FP packets sent by the decoding DSP to the transport network (excluding data packets discarded from the buffer of the decoding DSP). Then. it reduces the exit bandwidth of the LP by a certain step. and the congestion recovery timer is restarted. 7. the RNC performs R99 single service uplink congestion detection. This algorithm is applied to the R99 uplink congestion control scenario in which backpressure does not take effect. Otherwise. Otherwise. (Error! Unknown document property name. It is set to ON by default. Step 2 If the DCH FP frame carries the total number of FP packets sent by the NodeB. 7-16 . The extension information consists of the PM packet indication. After obtaining the Iub congestion status of the transport network.

FP silent mode: The FP silent mode is a mechanism of eliminating unused and null data on the Iub/Iur interface. It is set to ON by default. The boards of the RAN10. the NodeB performs the operation as follows: The NodeB limits the transmission rate (not lower than the GBR) of the user and restarts the rate reducing and suspension period timer of the uplink cross-Iur HSUPA service if the TNL Congestion Indication indicates congestion due to frame loss or delay and the timer expires. The FP-MUX is only applied to Iub user plane data based on the UDP/IP protocol.) Error! Unknown document property name. thus improving the transmission efficiency.6 Iub Efficiency Improvement The Iub efficiency is improved in the following aspects:  IP RAN FP-MUX: The frame protocol multiplexing (FP-MUX) is used to encapsulate several small FP PDU frames (also called subframe) into a UDP packet. the RNC sends the cross-Iur TNL Congestion Indication to the NodeB and indicates that the user is across the Iur interface. the NodeB adjusts the exit rate of a single service according to the TNL Congestion Indication returned by the SRNC to prevent congestion due to packet loss on the Iur interface. 7-17 . the decoding DSP sends data by using the leaky bucket algorithm.   Issue Error! Unknown document property name. NOTE The switch of this algorithm is not configurable.000 bit/s x SPI.5. ----End 7. The algorithm is implemented as follows: Step 1 For the cross-Iur HSUPA service. (Error! Unknown document property name. The new boards of the RAN10.0 or earlier versions do not support this algorithm. IP RAN header compression: IP RAN header compression is performed to compress the protocol header of the PPP frame to improve the bandwidth utilization. and the step is doubled at intervals of 20s. Step 2 After receiving the cross-Iur TNL Congestion Indication from the RNC.0 support this algorithm. For users across the Iur interface. The initial increasing step of the transmission rate is 2. Step 4 After obtaining the transmission rate. the NodeB increases the transmission rate for the uplink cross-Iur HSUPA user by a level by a certain step until the rate of the BE user reaches the MBR.7. the transmission rate is the minimum value between the rate limited by the backpressure algorithm and the rate specified by this algorithm. If the NodeB supports uplink backpressure.5 NodeB Cross-Iur Single HSUPA Service Uplink Congestion Control Algorithm The NodeB cross-Iur single HSUPA service uplink congestion control algorithm is implemented in the NodeB. Step 3 In a period of 1s.

ACFC Address and Control Field Compression (ACFC) complies with RFC 1661. At the time set by FPTIME. The RNC and NodeB support the following header compression methods. frames with the same DSCP value. the address and control field values are fixed values and need not be transferred each time. the FPMUXSWITCH parameter should be set to YES. After the Link Control Protocol (LCP) negotiation of the PPP link is complete.   The FP-MUX is applied only to Iub user plane data based on the UDP/IP protocol. MAXFRAMELEN indicates the maximum frame length of the FP-MUX UPD/IP packet. Each board supports 1. It is used to compress the address and control fields of the PPP protocol.IP RAN Header Compression IP RAN header compression is performed to compress the protocol header of the PPP frame to improve the bandwidth utilization.800 FP-MUX streams. the UDP packet is sent. The FP-MUX can be applied to frames with the same priority. SUBFRAMELEN indicates the maximum length of the subframe. the address and control field of successive packets can be compressed. Figure 7-7 shows the format of the FP-MUX UDP/IP packet.1 IP RAN FP-MUX The FP-MUX is used to encapsulate several small FP PDU frames (also called subframe) into a UDP packet.) Error! Unknown document property name. Figure 7-7 Format of the FP-MUX UDP/IP packet To activate the FP-MUX. namely.6. thus improving the transmission efficiency.7. (Error! Unknown document property name. Generally. Only the FG2a and GOUa support the FP-MUX. The QoS path occupies 14 FP-MUX streams for mapping. 7-18 . and the non-QoS path occupies only one FP-MUX stream. Issue Error! Unknown document property name.

IPHC improves the bandwidth utilization by using the following methods:   The unchanged header fields in the IP/UDP header are not carried in each packet.) Error! Unknown document property name. It is used to compress the IP/UDP header on the PPP link.6. Based on the packet loss and delay on the IP transport network detected by IP PM. normal mode and silent mode. 7-19 .3 FP Silent Mode The FP silent mode saves the transmission bandwidth of the uplink R99 service and improves the uplink transmission efficiency. In silent mode.PFC Protocol Field Compression (PFC) complies with RFC 1661.   The associated parameter on the RNC side is IPHC. The remaining bits follow this bit. can be used in uplink transmission. the protocol field contains one byte. the bandwidth on the Iub interface may be variable. The original header can be restored according to the context and the received compressed header. the transmission mode is permanently set to the normal mode. The associated parameter on the NodeB side is IPHC. for all associated DCHs.   In normal mode. (Error! Unknown document property name. the NodeB does not send the UL DATA FRAME to the RNC after receiving a TFI indicating TB numbered 0. for the DCH. The structure of this field is consistent with the ISO 3309 extension mechanism for the protocol field. the protocol field contains two bytes. In silent mode. the transmission Issue Error! Unknown document property name. This byte is the last one. IPHC IP Header Compression (IPHC) complies with RFC 2507 and RFC 3544. the NodeB continuously sends the UL DATA FRAME to the RNC.7 IP PM On the actual network. It is used to compress the 2-byte protocol field to a 1-byte one. the header context can be established at both ends of the link. the NodeB does not send the UL DATA FRAME to the RNC after receiving a TFI indicating TB numbered 0 in a TTI period. The header fields changed in a specified mode are replaced by the less significant bits. 7. Two modes. When a packet with a full header is occasionally sent. when only one transport channel is transmitted on the transport bearer. the SRNC selects the transmission mode.   When the least significant bit of the protocol field is 0. When the least significant bit of the protocol field is 1. When the transport bearer is established and the NodeB is informed through the related control plane procedure. Most packets can be compressed because the assigned protocol field value is generally less than 256.  In the current release. 7.

The non-QoS Path occupies only one PM stream. The RNC and NodeB implement IP PM in the following way to detect congestion and packet loss on the transport network: − − − The transmitter sends a Forward Monitoring (FM) packet containing the count and timestamp of the transmit packet to the receiver. The ACT IPPM command is used to activate IP PM.3 "Admission Control. The QoS Path needs to occupy a maximum of 14 PM streams. congestion and packet loss do not occur on the LP but may occur on the transport network. (Error! Unknown document property name. The receiver adds the count and timestamp of the receive packet to the FM packet to generate a Backward Reporting (BR) packet and then sends it to the transmitter. see section 6. only one fixed bandwidth may be configured for the LP. The IP PM solution is described as follows:   If backpressure is implemented on the LP. The adjusted bandwidth can be used as the input for port backpressure. 7-20 . Therefore.  Issue Error! Unknown document property name. MAXBW and MINBW must be configured. Only the FG2a and GOUa support IP PM. The dynamic adjustment of the bandwidth on the LP is dependent on the IP PM detection result. and the DEA IPPM command is used to deactivate IP PM. For details."    If the BWADJ parameter is set to ON. Each board supports 500 PM streams.) Error! Unknown document property name. The transmitter adjusts the available bandwidth on the LP according to the FM and BR packets and adjusts the rate on the LP according to the bandwidth adjustment result.  The predicted available bandwidth is also applied to the access algorithm.bandwidth on the Iub IP LP can be adjusted adaptively. if the BWADJ parameter is set to ON. IP PM for all IP paths on the LP must be activated. If the BWADJ parameter is set to OFF. During the LP configuration. the system dynamically adjusts the bandwidth on the LP according to the Iub transmission quality information obtained by IP PM.

we cancel port flow control.) . When the time of the queue 3 buffer no more than the value of this parameter. and when the port flow control type is ATM. When the time of the queue 2 buffer no more than the value of this parameter. When the time of the queue 0 buffer no less than the value of this parameter. If the available backward bandwidth is greater than this value. When the time of the queue 1 buffer no more than the value of this parameter. we cancel port flow control. When the time of the queue 5 buffer no more than the value of this parameter. 8-1 CONGCLRTHD1 CONGCLRTHD2 CONGCLRTHD3 CONGCLRTHD4 CONGCLRTHD5 CONGTHD0 Issue Error! Unknown document property name. and when the port flow control type is ATM. . we cancel port flow control.R99: The service is carried on a non-HSPA channel. If the available backward bandwidth is less than or equal to this value. we Error! Unknown document property name. .1 Description Table 8-1 TRM parameter description Parameter ID Beartype Description BWADJ BWDCONGBW BWDCONGCLRBW BWDHORSVBW CONGCLRTHD0 TRM Parameters This parameter specifies the bearer type of the service. and when the port flow control type is ATM.HSPA: The service is carried on an HSPA channel. this parameter means the recover threshold of the CBR queue.8 8. the backward congestion alarm is emitted. this parameter means the recover threshold of the NRTVBR queue. When the time of the queue 0 buffer no more than the value of this parameter. this parameter means the recover threshold of the RTVBR queue. (Error! Unknown document property name. we cancel port flow control. and when the port flow control type is ATM. we cancel port flow control. this parameter means the recover threshold of the UBR queue. the backward congestion alarm is cleared. Automatic bandwidth adjustment switch for logical ports. When the time of the queue 4 buffer no more than the value of this parameter. and when the port flow control type is ATM. we cancel port flow control. Reserved backward bandwidth for handover user. this parameter means the recover threshold of the UBR+ queue.

3) DRA_BE_RATE_DOWN_BF_HO_SWITCH: When the switch is on. we begin port flow control. and when the port flow control type is ATM. we begin port flow control. (Error! Unknown document property name. the DCCC algorithm is used for HSUPA.Parameter ID Description begin port flow control. the status of the UE RRC that carrying HSUPA services can be changed to CELL_FACH at the RNC. The DCCC switch must be also on before this switch takes effect. 1) DRA_AQM_SWITCH: When the switch is on. the status of the UE RRC that carrying HSDPA services can be changed to CELL_FACH at the RNC. If a PS real-time service is carried over the HS-DSCH. the switch PS_BE_STATE_TRANS_SWITCH should be on simultaneously. When the time of the queue 2 buffer no less than the value of this parameter. 6) DRA_HSDPA_STATE_TRANS_SWITCH: When the switch is on. the switch PS_NON_BE_STATE_TRANS_SWITCH should be on simultaneously. this parameter means the congestion threshold of the UBR queue. 8) DRA_HSUPA_STATE_TRANS_SWITCH: When the switch is on. The link is not congested when the frame loss ratio is lower than or equal to this threshold. this parameter means the congestion threshold of the NRTVBR queue. When the time of the queue 3 buffer no less than the value of this parameter. we begin port flow control. the switch PS_NON_BE_STATE_TRANS_SWITCH should be on simultaneously. 7) DRA_HSUPA_DCCC_SWITCH: When the switch is on. When the time of the queue 4 buffer no less than the value of this parameter. the bandwidth for BE services is reduced before soft handover. It is recommended that the DCCC switch be on when this switch is on. and when the port flow control type is ATM. and when the port flow control type is ATM. Discard Rate. this parameter means the congestion threshold of the RTVBR queue. the TTI could be reconfigured to HSUPA traffic dynamically between 2ms and 10ms. and when the port flow control type is ATM. 5) DRA_HSDPA_DL_FLOW_CONTROL_SWITCH: When the switch is on. the switch PS_BE_STATE_TRANS_SWITCH should be on simultaneously. we begin port flow control. power control is enabled for HSDPA services in AM mode. When the switch is selected. and when the port flow control type is ATM. If a PS real-time service is carried over the E-DCH. If a PS BE service is carried over the HS-DSCH. 4) DRA_DCCC_SWITCH: When the switch is on. the dynamic channel reconfiguration control algorithm is used for the RNC. this parameter means the congestion threshold of the CBR queue. If a PS BE service is carried over the E-DCH. we begin port flow control. 9) DRA_IU_QOS_RENEG_SWITCH: When the switch is on and the Iu QoS Error! Unknown document property name. the congestion detection and control for DL R99 service is supported. CONGTHD1 When the time of the queue 1 buffer no less than the value of this parameter. the active queue management algorithm is used for the RNC.) . 2) DRA_BE_EDCH_TTI_RECFG_SWITCH: When the switch is on. this parameter means the congestion threshold of the UBR+ queue. When the time of the queue 5 buffer no less than the value of this parameter. 8-2 CONGTHD2 CONGTHD3 CONGTHD4 CONGTHD5 DLR99CONGCTRLS WITCH DR DraSwitch Issue Error! Unknown document property name. Dynamic resource allocation switch.

and when the port flow control type is ATM. When the time of the queue 4 buffer no less than the value of this parameter. 10) DRA_PS_BE_STATE_TRANS_SWITCH: When the switch is on. we begin to loss the packets. Flow control switch. When the time of the queue 5 buffer no less than the value of this parameter.) Error! Unknown document property name. the DCCC based on traffic statistics is supported over the DCH. we begin to loss the packets. the upper limit of RLC retransmission ratio. This parameter specifies the DiffServ Code Point for the ping command. we begin to loss the packets. we begin to loss the packets. the RNC supports renegotiation of the maximum rate if the QoS of real-time services is not ensured according to the cell status. this parameter means the packet discard threshold of the UBR queue. and when the port flow control type is ATM. Only FG2a and GOUa board support FPMUX. This parameter specifies the threshold of event B. 11) DRA_PS_NON_BE_STATE_TRANS_SWITCH: When the switch is on. this parameter means the packet discard threshold of the RTVBR queue. 12) DRA_R99_DL_FLOW_CONTROL_SWITCH: Under a poor radio environment. Indicating whether to check the link of the IP path with FPMUX. DROPPKTTHD0 When the time of the queue 0 buffer no less than the value of this parameter. This parameter specifies the threshold of event A. this parameter means the packet discard threshold of the CBR queue. the QoS of high speed services drops considerably and the TX power is overly high. 8-3 . the Iub overbooking function is enabled. In this case. that is. this parameter means the packet discard threshold of the UBR+ queue . When the time of the queue 1 buffer no less than the value of this parameter. Index of the factor table used by the current adjacent node. 13) DRA_THROUGHPUT_DCCC_SWITCH: When the switch is on. and when the port flow control type is ATM. When the time of the queue 3 buffer no less than the value of this parameter. UE RRC status transition (CELL_FACH/CELL_PCH/URA_PCH) is allowed at the RNC. (Error! Unknown document property name. Flow control parameter index. and when the port flow control type is ATM. DROPPKTTHD1 DROPPKTTHD2 DROPPKTTHD3 DROPPKTTHD4 DROPPKTTHD5 DSCP EventAThred EventBThred FCINDEX FLOWCTRLSWITC H FPMUXSWITCH FTI Issue Error! Unknown document property name. and when the port flow control type is ATM. the lower limit of RLC retransmission ratio. thus lowering traffic speed and TX power. we begin to loss the packets. the RNC can set restrictions on certain transmission formats based on the transmission quality.Parameter ID Description RENEQ license is activated. When the time of the queue 2 buffer no less than the value of this parameter. we begin to loss the packets. the status of the UE RRC that carrying real-time services can be changed to CELL_FACH at the RNC. this parameter means the packet discard threshold of the NRTVBR queue. that is. When the switch is on.

8-4 MAXBW MAXFRAMELEN MINBW MoniterPrd NodeBLdcAlgoSwitc h PendingTimeA PendingTimeB PQNUM PT RXTRFX SPI SUBFRAMELEN Issue Error! Unknown document property name. the forward congestion alarm is cleared. they are disabled. During the pending time. the forward congestion alarm is emitted. LCG_CREDIT_LDR (Cell group level credit congestion control algorithm): When the cell group level credit load is heavy. ENABLE means that the UDP/IP header is expected to be compressed from the peer end. select them.Parameter ID FWDCONGBW FWDCONGCLRBW FWDHORSVBW IPHC IPHC Description If the available forward bandwidth is less than or equal to this value. no event related to retransmission ratio is reported. Maximum Frame Length. users are assembled in priority order among all the NodeBs and some users are selected for LDR action in order to reduce the NodeB level credit load. IUB_LDR (Iub congestion control algorithm): When the NodeB Iub load is heavy. This parameter is valid only when the port flow control type is IP.) . IUB_OLC (Iub Overload congestion control algorithm): When the NodeB Iub load is Overload. Port Type Receive traffic record index of the SAAL link. If the available forward bandwidth is greater than this value. To enable some of the algorithms above. users are assembled in priority order among all the NodeBs and some users are selected for Olc action in order to reduce the NodeB Iub load. Reserved forward bandwidth for handover user. This parameter specifies the number of pending periods after event A is triggered. Otherwise. During the pending time. Max subframe length. Error! Unknown document property name. Priority queue number of ATM is fixed to 2 and can not be modified. Maximum bandwidth of automatic adjustment for logical ports. no event related to retransmission ratio is reported. DISABLE means that the IP header is not expected to be compressed from the peer end. IP Header Compress. users are assembled in priority order among all the NodeBs and some users are selected for LDR action (such as BE service rate reduction) in order to reduce the NodeB Iub load. users are assembled in priority order among all the NodeBs and some users are selected for LDR action in order to reduce the cell group level credit load. The value 15 indicates the highest priority and the value 0 indicates the lowest. This parameter specifies the number of pending periods after event B is triggered. IP header compress function of the PPP link. This parameter specifies a sampling period of retransmission ratio monitoring after the RLC entity is established or reconfigured. NODEB_CREDIT_LDR (NodeB level credit congestion control algorithm): When the NodeB level credit load is heavy. (Error! Unknown document property name. Minimum bandwidth of automatic adjustment for logical ports. This parameter indicates the scheduling priority.

we cancel port flow control. we cancel port flow control. and when the port flow control type is ATM. When the time of the queue 2 buffer no more than the value of this parameter. Recommended value (default value): 2. and when the port flow control type is ATM. TX traffic record index at the port from which the IPoA PVC goes out of the RNC. and when the port flow control type is ATM. When the time of the queue 0 buffer no more than the value of this parameter. This parameter specifies the user priority. This parameter specifies the number of consecutive periods during which the percentage of retransmitted PDUs is lower than the threshold of event B before event B is triggered.Parameter ID Switch TD TimeToMoniter TimeToTriggerA Description Flow Control Switch Time Delay. the backward congestion alarm is cleared. Based on Quality of Service (QoS). When the time of the queue 4 buffer no more than the value of this parameter. background. this parameter means the recover threshold of the NRTVBR queue. The link is not congested when the delay is lower than this threshold. (Error! Unknown document property name. If the available backward bandwidth is less than or equal to this value. and when the port flow control type is ATM. The TX traffic must have been configured. . this parameter Error! Unknown document property name. this parameter means the recover threshold of the CBR queue. this parameter means the recover threshold of the UBR queue. Automatic bandwidth adjustment switch for logical ports. This parameter specifies the traffic class that the service belongs to. and then Copper. and when the port flow control type is ATM. The user classes in descending order of priority are Gold. this parameter means the recover threshold of the RTVBR queue.) . Silver. This parameter specifies the bearer type of the service. Reserved backward bandwidth for handover user. This parameter specifies the delay time after the RLC entity is established or reconfigured and before the retransmission ratio monitoring is started. we cancel port flow control. This parameter specifies the number of consecutive periods during which the percentage of retransmitted PDUs is higher than the threshold of event A before event A is triggered. If the available backward bandwidth is greater than this value. we cancel port flow control.HSPA: The service is carried on an HSPA channel. there are two traffic classes: interactive.R99: The service is carried on a non-HSPA channel. When the time of the queue 1 buffer no more than the value of this parameter. . we cancel port flow control. 8-5 TimeToTriggerB TrafficClass TXTRFX UserPriority Beartype BWADJ BWDCONGBW BWDCONGCLRBW BWDHORSVBW CONGCLRTHD0 CONGCLRTHD1 CONGCLRTHD2 CONGCLRTHD3 CONGCLRTHD4 Issue Error! Unknown document property name. When the time of the queue 3 buffer no more than the value of this parameter. the backward congestion alarm is emitted.

we begin port flow control. we begin port flow control. this parameter means the congestion threshold of the UBR+ queue. HSPA OFF. 8-6 . When the time of the queue 2 buffer no less than the value of this parameter. this parameter means the congestion threshold of the UBR queue. When the time of the queue 0 buffer no less than the value of this parameter. CONGTHD1 CONGTHD2 CONGTHD3 CONGTHD4 8. this parameter means the congestion threshold of the RTVBR queue. ON Actual Value Range R99. this parameter means the congestion threshold of the CBR queue.Parameter ID Description means the recover threshold of the UBR+ queue. and when the port flow control type is ATM. we begin port flow control.2 Values and Ranges Table 8-2 TRM parameter values and parameter ranges Parameter ID Beartype BWADJ Default Value OFF GUI Value Range R99. CONGCLRTHD5 CONGTHD0 When the time of the queue 5 buffer no more than the value of this parameter. HSPA OFF. ON Unit None None MML Command SET USERGBR(Mandatory) ADD IPLOGICPORT(Option al) ADD AAL2PATH(Optional) ADD AAL2PATH(Optional) ADD AAL2PATH(Optional) ADD PORTFLOWCTRLPAR A(Optional) NE RNC RNC BWDCONG BW BWDCONG CLRBW BWDHORS VBW CONGCLRT HD0 0 0 0 15 0~320000 0~320000 0~320000 10~150 0~320000 0~320000 0~320000 10 to 150 kbit/s kbit/s kbit/s ms RNC RNC RNC RNC Issue Error! Unknown document property name. and when the port flow control type is ATM. we cancel port flow control. we begin port flow control. When the time of the queue 4 buffer no less than the value of this parameter. When the time of the queue 3 buffer no less than the value of this parameter. (Error! Unknown document property name. we begin port flow control. and when the port flow control type is ATM. When the time of the queue 1 buffer no less than the value of this parameter. this parameter means the congestion threshold of the NRTVBR queue.) Error! Unknown document property name. and when the port flow control type is ATM. and when the port flow control type is ATM.

001 Step: None SET HSDPAFLOWCTRLPA Node B 8-7 Issue Error! Unknown document property name.Parameter ID CONGCLRT HD1 CONGCLRT HD2 CONGCLRT HD3 CONGCLRT HD4 CONGCLRT HD5 CONGTHD0 Default Value 15 GUI Value Range 10~150 Actual Value Range 10 to 150 Unit ms MML Command ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) SET DPUCFGDATA(Option al) NE RNC 15 10~150 10 to 150 ms RNC 15 10~150 10 to 150 ms RNC 25 10~150 10 to 150 ms RNC 25 10~150 10 to 150 ms RNC 25 10~150 10 to 150 ms RNC CONGTHD1 25 10~150 10 to 150 ms RNC CONGTHD2 25 10~150 10 to 150 ms RNC CONGTHD3 25 10~150 10 to 150 ms RNC CONGTHD4 50 10~150 10 to 150 ms RNC CONGTHD5 50 10~150 10 to 150 ms RNC DLR99CON GCTRLSWI TCH - OFF(The switch of DL R99 congestion control is off).) Error! Unknown document property name. ON(The switch of DL R99 congestion control is on) 0~1000 OFF. 0. (Error! Unknown document property name. ON None RNC DR 1 0~1. .

) Error! Unknown document property name. DRA_BE_EDC H_TTI_RECF G_SWITCH. DRA_HSDPA_ STATE_TRAN S_SWITCH. DRA_HSUPA_ STATE_TRAN S_SWITCH. DRA_HSUPA_ STATE_TRAN S_SWITCH. DRA_HSUPA_ DCCC_SWITC H. DRA_DCCC_S WITCH. DRA_PS_NON _BE_STATE_ TRANS_SWIT CH. DRA_HSDPA_ DL_FLOW_C ONTROL_SWI TCH. DRA_IU_QOS _RENEG_SWI TCH. DRA_R99_DL _FLOW_CON TROL_SWITC H. DRA_HSDPA_ DL_FLOW_C ONTROL_SWI TCH.Parameter ID Default Value GUI Value Range Actual Value Range Unit MML Command RA(Optional) NE DraSwitch - DRA_AQM_S WITCH. DRA_R99_DL _FLOW_CON TROL_SWITC H. DRA_THROU GHPUT_DCC C_SWITCH 10 to 150 None SET CORRMALGOSWITC H(Optional) RNC DROPPKTT HD0 DROPPKTT HD1 DROPPKTT HD2 60 ms ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR RNC 60 10~150 10 to 150 ms RNC 60 10~150 10 to 150 ms RNC 8-8 Issue Error! Unknown document property name. DRA_PS_NON _BE_STATE_ TRANS_SWIT CH. DRA_THROU GHPUT_DCC C_SWITCH 10~150 DRA_AQM_S WITCH. DRA_HSUPA_ DCCC_SWITC H. DRA_DCCC_S WITCH. DRA_BE_EDC H_TTI_RECF G_SWITCH. DRA_PS_BE_ STATE_TRAN S_SWITCH. DRA_BE_RAT E_DOWN_BF_ HO_SWITCH. DRA_HSDPA_ STATE_TRAN S_SWITCH. . (Error! Unknown document property name. DRA_PS_BE_ STATE_TRAN S_SWITCH. DRA_IU_QOS _RENEG_SWI TCH. DRA_BE_RAT E_DOWN_BF_ HO_SWITCH.

ADD IMAGRP. ADD MPGRP) 0~1999 0 to 1999 RNC Issue Error! Unknown document property name. SET OPT) 0(ADD IPLOGICP ORT. ADD UNILNK. SET ETHPORT.Parameter ID Default Value GUI Value Range Actual Value Range Unit MML Command A(Optional) NE DROPPKTT HD3 DROPPKTT HD4 DROPPKTT HD5 DSCP 60 10~150 10 to 150 ms ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) ADD PORTFLOWCTRLPAR A(Optional) PING IP(Optional) SET DSCPMAP(Mandatory) ADD SCTPLNK(Optional) SET PHBMAP(Mandatory) ADD TYPRABRLC(Optional ) ADD TYPRABRLC(Optional ) ADD FRALNK(Optional) ADD IMAGRP(Optional) SET OPT(Mandatory) SET ETHPORT(Mandatory) ADD MPGRP(Optional) ADD PPPLNK(Optional) ADD UNILNK(Optional) ADD ATMLOGICPORT(Opti onal) ADD PORTFLOWCTRLPAR A(Mandatory) ADD IPLOGICPORT(Option al) RNC 80 10~150 10 to 150 ms RNC 80 10~150 10 to 150 ms RNC 0(PING IP) -(SET PHBMAP.1 RNC FCINDEX 1(ADD ATMLOGI CPORT.S ET DSCPMAP ) 62(ADD SCTPLNK) 160 0~63 0 to 63 None RNC EventAThred 0~1000 0~100. step: 0.1 per cent per cent None RNC EventBThred 80 0~1000 0~100. 8-9 . ADD FRALNK) -(ADD PORTFLO WCTRLPA RA. (Error! Unknown document property name.) Error! Unknown document property name. ADD PPPLNK. step: 0.

ADD UNILNK. ENABLE(The UDP/IP header is expected to be compressed from the peer) 1~1000 None ADD MPGRP(Optional) ADD PPPLNK(Optional) Node B MAXBW - 64~64000 kbit/s ADD RNC 8-10 Issue Error! Unknown document property name. ON Actual Value Range OFF. SET OPT) NO 0 0 0 UDP/IP_H C GUI Value Range OFF. (Error! Unknown document property name.Parameter ID FLOWCTRL SWITCH Default Value ON(ADD ATMLOGI CPORT. ADD IMAGRP. ADD IPLOGICP ORT. ENABLE None None kbit/s kbit/s kbit/s None RNC RNC RNC RNC RNC RNC IPHC ENABLE DISABLE(The IP header is not expected to be compressed from the peer).UDP /IP_HC(Use UDP/IP head compress) DISABLE. ON Unit None MML Command ADD FRALNK(Optional) SET OPT(Optional) ADD PPPLNK(Optional) ADD IMAGRP(Optional) ADD IPLOGICPORT(Option al) ADD MPGRP(Optional) ADD UNILNK(Optional) ADD ATMLOGICPORT(Opti onal) SET ETHPORT(Optional) ADD IPPATH(Optional) ADD ADJMAP(Mandatory) ADD AAL2PATH(Optional) ADD AAL2PATH(Optional) ADD AAL2PATH(Optional) ADD PPPLNK(Optional) NE RNC FPMUXSWI TCH FTI FWDCONG BW FWDCONG CLRBW FWDHORS VBW IPHC NO. UDP/IP_HC NO. ADD FRALNK) -(SET ETHPORT. ADD PPPLNK. . ADD MPGRP.) Error! Unknown document property name. YES 0~33 0~320000 0~320000 0~320000 No_HC. YES 0~33 0~320000 0~320000 0~320000 No_HC(Disabl e head compress).

) Error! Unknown document property name. VALUE(Analo g port) 100~1999 None Node B RXTRFX - None ADD SAALLNK(Mandatory) ADD AAL2PATH(Mandatory ) ADD VPCLCX(Mandatory) ADD IPOAPVC(Optional) SET SPIFACTOR(Mandator y) SET SCHEDULEPRIOMAP (Mandatory) RNC SPI - 0~15 0~15 None RNC Issue Error! Unknown document property name. LCG_CREDIT _LDR. IUB_OLC 0~1000 None RNC PendingTime A PendingTime B PQNUM 1 None ADD TYPRABRLC(Optional ) ADD TYPRABRLC(Optional ) ADD PORTFLOWCTRLPAR A(Mandatory) SET ALMPORT RNC 1 0~1000 0~1000 None RNC - 0~5 0 to 5 None RNC PT - BOOL(Boolean port). VALUE(Analo g port) 100~1999 BOOL(Boolean port). NODEB_CRE DIT_LDR. NODEB_CRE DIT_LDR. IUB_OLC 0~1000 IUB_LDR.Parameter ID Default Value GUI Value Range Actual Value Range step:64 Unit MML Command IPLOGICPORT(Mandat ory) NE MAXFRAM ELEN MINBW 270 - 24~1031 1~1000 24~1031 64~64000 step:64 40~60000 byte kbit/s ADD IPPATH(Optional) ADD IPLOGICPORT(Mandat ory) ADD TYPRABRLC(Optional ) ADD NODEBALGOPARA(O ptional) RNC RNC MoniterPrd 1000 40~60000 ms RNC NodeBLdcAl goSwitch - IUB_LDR. 8-11 . LCG_CREDIT _LDR. (Error! Unknown document property name.

) Error! Unknown document property name. NO_BW_SHA PING. It is recommended that the RNC in compliance with R6 should perform this function. The RNC use the R6 switch to perform this function. BW_SHAPING _ONOFF_TOG GLE Unit byte None MML Command ADD IPPATH(Optional) SET HSDPAFLOWCTRLPA RA(Optional) NE RNC Node B Issue Error! Unknown document property name. 8-12 . To perform this function.Parameter ID SUBFRAME LEN Switch Default Value 127 BW_SHAP ING_ONO FF_TOGG LE GUI Value Range 16~1023 DYNAMIC_B W_SHAPING: According to the flow control of STATIC_BW_ SHAPING. the reverse flow control switch must be enabled by the RNC. DYNAMIC_B W_SHAPING. NO_BW_SHA PING: The NodeB does not allocate bandwidth according to the configuration or delay on the Iub interface. The link Actual Value Range 16~1023 STATIC_BW_ SHAPING. (Error! Unknown document property name. The RNC allocates the bandwidth according to the bandwidth on the Uu interface reported by the NodeB. traffic is allocated to HSDPA users when the delay and packet loss on the Iub interface are taken into account.

and NO_BW_SHA PING are flow Actual Value Range Unit MML Command NE Issue Error! Unknown document property name. the system automatically selects DYNAMIC_B W_SHAPING or NO_BW_SHA PING on the basis of the NodeB congestion detection mechanism. 8-13 . DYNAMIC_B W_SHAPING is selected when congestion is detected. BW_SHAPING _ONOFF_TOG GLE: If BW_SHAPING _ONOFF_TOG GLE is selected. BW_SHAPING _ONOFF_TOG GLE. (Error! Unknown document property name.Parameter ID Default Value GUI Value Range is not congested when the delay is lower than this threshold. DYNAMIC_B W_SHAPING.) Error! Unknown document property name. In other words. NO_BW_SHA PING is selected when there is no congestion within a specific time. The link is not congested when frame loss ratio is no higher than this threshold.

SILVER.) Error! Unknown document property name. 8-14 . BACKGROUN D INTERACTIV E. Actual Value Range Unit MML Command NE TD 4 0~100 0~500. (Error! Unknown document property name.Parameter ID Default Value GUI Value Range control strategies applied at the NodeB port. COPPER GOLD. COPPER None RNC Issue Error! Unknown document property name. BACKGROUN D None RNC TXTRFX - 100~1999 100 to 1999 None RNC UserPriority - GOLD. 5ms 0~500000 Step: ms SET HSDPAFLOWCTRLPA RA(Optional) ADD TYPRABRLC(Optional ) ADD TYPRABRLC(Optional ) ADD TYPRABRLC(Optional ) SET SCHEDULEPRIOMAP (Mandatory) SET USERGBR(Mandatory) SET FACHBANDWIDTH( Mandatory) SET USERHAPPYBR(Mand atory) SET DTXDRXPARA(Manda tory) SET HSSCCHLESSOPPAR A(Mandatory) ADD IPOAPVC(Optional) ADD AAL2PATH(Mandatory ) ADD SAALLNK(Mandatory) ADD VPCLCX(Mandatory) SET SCHEDULEPRIOMAP (Mandatory) SET USERGBR(Mandatory) Node B RNC TimeToMoni ter TimeToTrigg erA TimeToTrigg erB TrafficClass 5000 0~500000 ms 2 1~100 1~100 None RNC 14 1~100 1~100 None RNC - INTERACTIV E. SILVER.

(Error! Unknown document property name.) Error! Unknown document property name. The "-" symbol indicates no default value. 8-15 . Issue Error! Unknown document property name.Parameter ID Default Value GUI Value Range Actual Value Range Unit MML Command SET FACHBANDWIDTH( Mandatory) SET USERHAPPYBR(Mand atory) NE The Default Value column is valid for only the optional parameters.

423 "UTRAN Iur interface RNSAP signaling" 14.1” RFC1661 “The Point-to-Point Protocol (PPP). 7.426 "UTRAN Iur and Iub Interface Data Transport" 15. TRM Reference Documents The following lists the reference documents related to the feature: ITU-T Recommendation I.366.361 “B-ISDN ATM Layer Specification” ITU-T Recommendation I.001 “Inverse Multiplexing for ATM (IMA) Specification Version 1.) Error! Unknown document property name.1” AF-PHY-0086. provides a standard method for transporting multi-protocol datagrams over point-to-point links” RFC1662 "PPP in HDLC-link Framing" RFC1990 "The PPP Multilink Protocol (ML-PPP)" RFC2686 "The Multi-Class Extension to Multi-link PPP (MC-PPP)" 10.5 Issue Error! Unknown document property name.1 “Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2” AF-TM-0121. 4.0 V1. 3GPP TS 25. 3GPP TS 25. 8.363. RFC894 "Standard for the Transmission of IP Datagrams over Ethernet Networks" 12.2 “ATM Adaptation layer specification: Type 2 AAL” ITU-T Recommendation I. 5. 3.0 V1. 2. 3GPP TS 25.427 "UTRAN Iur and Iub Interface User Plane Protocols for DCH Data Streams" 16. (Error! Unknown document property name.212 "Multiplexing and Channel Coding" 17. RFC3153 "PPP Multiplexing (PPPmux)" 11. Optional Feature Description of Huawei UMTS RAN11.221 "Physical Channels and Mapping of Transport Channels onto Physical Channels" 18. 3GPP TS 25.000 “Traffic Management 4. 3GPP TS 25. 9-1 .5 19.9 1. 6. 9. RFC1042 "A Standard for the Transmission of IP Datagrams over IEEE 802 Networks" 13. Basic Feature Description of Huawei UMTS RAN11.

(Error! Unknown document property name. .10 Table 10-1 Default TRMMAP table for the ATM-based Iub and Iur interfaces TC/THP Gold Primary Common channel SRB SIP AMR R99 CS conversational R99 CS streaming R99 PS conversational R99 PS streaming R99 PS high-priority interactive R99 PS medium-priority interactive R99 PS low-priority interactive R99 PS background HSDPA SRB HSDPA SIP Issue Error! Unknown document property name.1 Default TRMMAP Table for the ATM-Based Iub and Iur Interfaces Silver Secondary None None None None None None None None None None None None None None Primary – – – RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR NRT_VB R NRT_VB R NRT_VB R NRT_VB R RT_VBR RT_VBR Secondary – – – None None None None None None None None None None None Copper Primary – – – RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR NRT_VB R NRT_VB R NRT_VB R NRT_VB R RT_VBR RT_VBR Secondar y – – – None None None None None None None None None None None 10-1 RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR NRT_VB R NRT_VB R NRT_VB R NRT_VB R RT_VBR RT_VBR Error! Unknown document property name.) Appendix 10.

(Error! Unknown document property name.) Silver Secondary None Primary – Secondary – Copper Primary – Secondary – 10-2 EF Error! Unknown document property name.2 Default TRMMAP Table for the IP-Based Iub and Iur Interfaces Table 10-2 Default TRMMAP table for the IP-based Iub and Iur interfaces TC/THP Gold Primary Common channel Issue Error! Unknown document property name.TC/THP Gold Primary Secondary None None None None None None None None None None None None None None None None Silver Primary RT_VBR RT_VBR RT_VBR UBR UBR UBR UBR RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR UBR UBR UBR UBR Secondary None None None None None None None None None None None None None None None None Copper Primary RT_VBR RT_VBR RT_VBR UBR UBR UBR UBR RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR UBR UBR UBR UBR Secondar y None None None None None None None None None None None None None None None None HSDPA voice HSDPA conversational HSDPA streaming HSDPA high-priority interactive HSDPA medium-priority interactive HSDPA low-priority interactive HSDPA background HSUPA SRB HSUPA SIP HSUPA voice HSUPA conversational HSUPA streaming HSUPA high-priority interactive HSUPA medium-priority interactive HSUPA low-priority interactive HSUPA background RT_VBR RT_VBR RT_VBR UBR UBR UBR UBR RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR UBR UBR UBR UBR 10. .

(Error! Unknown document property name. 10-3 .) Error! Unknown document property name.TC/THP Gold Primary Secondary None None None None None None None None None None None None None None None None None None None None None None None None None Silver Primary – – EF AF43 AF33 AF43 AF33 AF33 AF33 AF33 AF13 – – AF43 AF43 AF33 AF11 AF11 AF11 BE – – AF43 AF43 AF33 Secondary – – None None None None None None None None None – – None None None None None None None – – None None None Copper Primary – – EF AF43 AF33 AF43 AF33 AF33 AF33 AF33 AF13 – – AF43 AF43 AF33 AF11 AF11 AF11 BE – – AF43 AF43 AF33 Secondary – – None None None None None None None None None – – None None None None None None None – – None None None SRB SIP AMR R99 CS conversational R99 CS streaming R99 PS conversational R99 PS streaming R99 PS high-priority interactive R99 PS medium-priority interactive R99 PS low-priority interactive R99 PS background HSDPA SRB HSDPA SIP HSDPA voice HSDPA conversational HSDPA streaming HSDPA high-priority interactive HSDPA medium-priority interactive HSDPA low-priority interactive HSDPA background HSUPA SRB HSUPA SIP HSUPA voice HSUPA conversational HSUPA streaming EF EF EF AF43 AF33 AF43 AF33 AF33 AF33 AF33 AF13 EF EF AF43 AF43 AF33 AF11 AF11 AF11 BE EF EF AF43 AF43 AF33 Issue Error! Unknown document property name.

.) Error! Unknown document property name.3 Default TRMMAP Table for the ATM&IP-Based Iub Interface Table 10-3 Default TRMMAP table for the ATM&IP-based Iub interface TC/THP Gold Primary Common channel SRB SIP AMR R99 CS conversational R99 CS streaming R99 PS conversational R99 PS streaming R99 PS high-priority interactive R99 PS mediumpriority interactive R99 PS low-priority interactive R99 PS background HSDPA SRB RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR NRT_VBR NRT_VBR NRT_VBR NRT_VBR EF Secondary EF EF EF EF AF43 AF33 AF43 AF33 AF33 AF33 AF33 AF13 RTVBR Silver Primary – – – RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR NRT_VBR NRT_VBR NRT_VBR NRT_VBR – Secondary – – – EF AF43 AF33 AF43 AF33 AF33 AF33 AF33 AF13 – Copper Primary – – – RT_VBR RT_VBR RT_VBR RT_VBR RT_VBR NRT_VBR NRT_VBR NRT_VBR NRT_VBR – Secondary – – – EF AF43 AF33 AF43 AF33 AF33 AF33 AF33 AF13 – 10-4 Issue Error! Unknown document property name. (Error! Unknown document property name.TC/THP Gold Primary Secondary None None None None Silver Primary AF23 AF23 AF23 AF13 Secondary None None None None Copper Primary AF23 AF23 AF23 AF13 Secondary None None None None HSUPA high-priority interactive HSUPA medium-priority interactive HSUPA low-priority interactive HSUPA background AF23 AF23 AF23 AF13 10.

(Error! Unknown document property name. 10-5 .TC/THP Gold Primary Secondary RTVBR AF43 AF43 AF33 UBR UBR UBR UBR RTVBR RTVBR AF43 AF43 AF33 UBR UBR UBR UBR Silver Primary – RT_VBR RT_VBR RT_VBR AF23 AF23 AF23 AF13 – – RT_VBR RT_VBR RT_VBR AF23 AF23 AF23 AF13 Secondary – AF43 AF43 AF33 UBR UBR UBR UBR – – AF43 AF43 AF33 UBR UBR UBR UBR Copper Primary – RT_VBR RT_VBR RT_VBR AF23 AF23 AF23 AF13 – – RT_VBR RT_VBR RT_VBR AF23 AF23 AF23 AF13 Secondary – AF43 AF43 AF33 UBR AF11 AF11 UBR – – AF43 AF43 AF33 UBR AF11 AF11 UBR HSDPA SIP HSDPA voice HSDPA conversational HSDPA streaming HSDPA high-priority interactive HSDPA mediumpriority interactive HSDPA low-priority interactive HSDPA background HSUPA SRB HSUPA SIP HSUPA voice HSUPA conversational HSUPA streaming HSUPA high-priority interactive HSUPA mediumpriority interactive HSUPA low-priority interactive HSUPA background EF RT_VBR RT_VBR RT_VBR AF23 AF23 AF23 AF13 EF EF RT_VBR RT_VBR RT_VBR AF23 AF23 AF23 AF13 Issue Error! Unknown document property name.) Error! Unknown document property name.

(Error! Unknown document property name.10.) Error! Unknown document property name. 10-6 .4 Default TRMMAP Table for the Hybrid-IP-Based Iub Interface Table 10-4 Default TRMMAP table for the hybrid-IP-based Iub interface TC/THP Gold Primary Common channel SRB SIP AMR R99 CS conversational R99 CS streaming R99 PS conversational R99 PS streaming R99 PS high-priority interactive R99 PS medium-priority interactive R99 PS low-priority interactive R99 PS background HSDPA SRB HSDPA SIP HSDPA voice HSDPA conversational HSDPA streaming HSDPA high-priority interactive HSDPA medium-priority interactive HSDPA low-priority interactive HSDPA background HSUPA SRB EF EF EF EF AF43 AF33 AF43 AF43 AF33 AF33 AF33 AF13 EF EF AF33 AF33 AF33 AF23 AF23 AF23 AF13 EF Secondary LQEF LQEF LQEF LQEF LQAF43 LQAF33 LQAF43 LQAF43 LQAF33 LQAF33 LQAF33 LQAF13 LQEF LQEF LQAF33 LQAF33 LQAF33 LQAF23 LQAF23 LQAF23 LQAF13 LQEF Silver Primary – – – EF AF43 AF33 AF43 AF43 AF33 AF33 AF33 AF13 – – AF33 AF33 AF33 AF23 AF23 AF23 AF13 – Secondary – – – LQEF LQAF43 LQAF33 LQAF43 LQAF43 LQAF33 LQAF33 LQAF33 LQAF13 – – LQAF33 LQAF33 LQAF33 LQAF23 LQAF23 LQAF23 LQAF13 – Copper Primary – – – EF AF43 AF33 AF43 AF43 AF33 AF33 AF33 AF13 – – AF33 AF33 AF33 AF23 AF23 AF23 AF13 – Secondary – – – LQEF LQAF43 LQAF33 LQAF43 LQAF43 LQAF33 LQAF33 LQAF33 LQAF13 – – LQAF33 LQAF33 LQAF33 LQAF23 LQAF23 LQAF23 LQAF13 – Issue Error! Unknown document property name.

TC/THP Gold Primary Secondary LQEF LQAF33 LQAF33 LQAF33 LQAF23 LQAF23 LQAF23 LQAF13 Silver Primary – AF33 AF33 AF33 AF23 AF23 AF23 AF13 Secondary – LQAF33 LQAF33 LQAF33 LQAF23 LQAF23 LQAF23 LQAF13 Copper Primary – AF33 AF33 AF33 AF23 AF23 AF23 AF13 Secondary – LQAF33 LQAF33 LQAF33 LQAF23 LQAF23 LQAF23 LQAF13 HSUPA SIP HSUPA voice HSUPA conversational HSUPA streaming HSUPA high-priority interactive HSUPA medium-priority interactive HSUPA low-priority interactive HSUPA background EF AF33 AF33 AF33 AF23 AF23 AF23 AF13 10. . (Error! Unknown document property name.6 Default TRMMAP Table for the IP-Based Iu-CS Interface Table 10-6 Default TRMMAP table for the IP-based Iu-CS interface TC/THP Gold Primary AMR EF Secondary None Silver Primary EF Secondary None Copper Primary EF Secondary None 10-7 Issue Error! Unknown document property name.5 Default TRMMAP Table for the ATM-Based Iu-CS Interface Table 10-5 Default TRMMAP table for the ATM-based Iu-CS interface TC/THP Gold Primary AMR CS conversational CS streaming RT_VBR RT_VBR RT_VBR Secondary None None None Silver Primary RT_VBR RT_VBR RT_VBR Secondary None None None Copper Primary RT_VBR RT_VBR RT_VBR Secondary None None None 10.) Error! Unknown document property name.

(Error! Unknown document property name. 10-8 .7 Default TRMMAP Table for the Iu-PS Interface Table 10-7 Default TRMMAP table for the Iu-PS interface TC/THP Gold Primary SIP PS conversational PS streaming PS high-priority interactive PS medium-priority interactive PS low-priority interactive PS background EF AF43 AF43 AF33 AF33 AF33 AF13 Secondary None None None None None None None Silver Primary – AF43 AF43 AF33 AF33 AF33 AF13 Secondary – None None None None None None Copper Primary – AF43 AF43 AF33 AF33 AF33 AF13 Secondary – None None None None None None Issue Error! Unknown document property name.TC/THP Gold Primary Secondary None None Silver Primary AF43 AF33 Secondary None None Copper Primary AF43 AF33 Secondary None None CS conversational CS streaming AF43 AF33 10.) Error! Unknown document property name.