transmission resource management description

RAN

Transmission Resource Management Description Issue 02

Date 2008-07-30

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

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: http://www.huawei.com

Email: [email protected]

Copyright Huawei Technologies Co., Ltd. 2008. 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.

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

RAN Transmission Resource Management Description Contents

Issue 02 (2008-07-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

iii

Contents

1 TRM Change History ................................................................................................................1-1

2 TRM Introduction......................................................................................................................2-1

3 TRM Principles...........................................................................................................................3-1 3.1 ATM Transmission Resources.......................................................................................................................3-1

3.1.1 ATM Physical Layer Resources ...........................................................................................................3-1 3.1.2 AAL2 Path Resources ..........................................................................................................................3-3 3.1.3 ATM Virtual Port Shaping....................................................................................................................3-4

3.2 IP Transmission Resources............................................................................................................................3-5 3.2.1 Physical and Data Link Layer Resources.............................................................................................3-6 3.2.2 IP Path Resources.................................................................................................................................3-7 3.2.3 IP Logical Port Shaping .......................................................................................................................3-8 3.2.4 IP Performance Management .............................................................................................................3-10

3.3 Iub ATM/IP Transmission Resources ..........................................................................................................3-10 3.4 Paths on the Iur, Iu-CS, and Iu-PS Interfaces..............................................................................................3-10

3.4.1 Paths on Iur Interface .........................................................................................................................3-11 3.4.2 Paths on Iu-CS Interface ....................................................................................................................3-11 3.4.3 Paths on Iu-PS Interface.....................................................................................................................3-11

3.5 Traffic Type and Transmission Resource Mapping .....................................................................................3-11 3.5.1 ATM Mapping Table ..........................................................................................................................3-11 3.5.2 IP Mapping Table ...............................................................................................................................3-12 3.5.3 ATM/IP Mapping Table......................................................................................................................3-13

3.6 Differentiated Service .................................................................................................................................3-14 3.6.1 DiffServ Based on QoS......................................................................................................................3-15 3.6.2 DiffServ Based on HSDPA ................................................................................................................3-15 3.6.3 DiffServ Based on ATM PVC............................................................................................................3-15 3.6.4 DiffServ Based on DSCP...................................................................................................................3-15

3.7 Transport Layer Group Bandwidth Management........................................................................................3-16 3.7.1 Bandwidth Reserved for Control and Management Planes................................................................3-16 3.7.2 Transmission Resource Group ...........................................................................................................3-17

3.8 Activity Factor.............................................................................................................................................3-17 3.9 Iub Overbooking .........................................................................................................................................3-18 3.10 Admission Control ....................................................................................................................................3-18

Contents RAN

Transmission Resource Management Description

iv Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Issue 02 (2008-07-30)

3.10.1 Multi-Level Admission Control Policy............................................................................................3-18 3.10.2 Admission Control Algorithm..........................................................................................................3-19 3.10.3 Admission Procedure .......................................................................................................................3-22

3.11 Congestion Control....................................................................................................................................3-25 3.11.1 Congestion Detection Method..........................................................................................................3-25 3.11.2 Congestion Handling on the Iub Interface .......................................................................................3-25

4 TRM Parameters.........................................................................................................................4-1

5 TRM Reference Documents .....................................................................................................5-1

RAN Transmission Resource Management Description 1 TRM Change History


1-1

1 TRM Change History TRM Change History provides information on the changes between different document versions.

Document and s

T nt and versions

Product Version

able 1-1 Docume product

Document Version RAN Version RNC Version NodeB Version

02 (2008-07-30) 10.0 V200R010C01B061 V200R010C01B041 V100R010C01B050

01 (2008-05-30) 10.0 V200R010C01B051 V100R010C01B049 V200R010C01B040

Draft (2008-03-20) 10.0 V200R010C01B050 V100R010C01B045

z nagement feature of a specific product version.

Editorial change: refers to changes in information that has already been included, or the n.

02 (2008-07-30This is the document for the second commercial release of RAN10.0.

C d with 01 (2008-05-30) of RAN10.0, issue 02 (2008-07-30) of RAN10.0 inc ates the changes described in the following table.

There are two types of changes, which are defined as follows:

Feature change: refers to the change in the transmission resource ma

zaddition of information that is not provided in the previous versio

)

ompareorpor

Change Change Description Parameter Change Type

Feature change

A parameter list is added. See chapter 4 "TRM Parameters".

None.

1 TRM Change History RAN


1-2 Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

Issue 02 (2008-07-30)

Change Change Description Parameter Change Type

In section 3.6 "Differentiated Service", the default DSCP values for the IP paths of QOSPATH type are changed.

None.

None.

user is

d to Copper user TRMMAP index.

The parameter modified is listed as follow: BronzeTRMMAP indexmodifie

Editorial change

None. None.

01 (2008-05-30This docum mercial release of RAN10.0.

C d with draft (2008-03-20) of RAN10.0, issue 01 (2008-05-30) of RAN10incorporates the changes described in the following table.

) is the

ompare

ent for the first com

.0

Change Change Description Parameter Type Change

The DSCP values of QOSPATH have increased. For details, see .

None. DiffServ Based on DSCP in 3.6 Differentiated Service

Feature

re r. None.

change

The parameter Resource Management Mode used for a source group is changed to be non-configurable paramete

Editorial change

: z Management Parameters is

removed because of the creation of RAN10.0 parameter reference.

z The structure is optimized.

None. General documentation changeThe Transmission Resource

Draft (2008-03This is a draft for the first commercial release of RAN10.0.

Compared with issue 03 (2008-01-20) of RAN6.1, this issue incorporates the changes described in the following table.

-20)

RAN Transmission Resource Management Description 1 TRM Change History


1-3

Change Type Change Description Parameter Change

The topic 3.2.3 IP Logical Port Shaping is added.

The following parameters are added:z Logic port No. z Resource

Management Mode

The topic 3.2.4 IP Performance Management is added.

The following parameters are added:z Auto adjust

bandwidth switchz Min bandwidth

[64kbps] z Max bandwidth

[64kbps]

Multi-level VP shaping is added to 3.1.3 ATM Virtual Port Shaping.

The following parameters are added:z Type of the

virtual port z The Virtual Port

Number z The bearing type

of the virtual portz The Upper

Virtual port Number

z Forward bandwidth [kpbs]

z Backward bandwidth [kpbs]

z Bearing VP No.

In 3.2 IP Transmission Resources, z A description of two IP interface boards is

added. z The values of the IP path type parameter are

divided into two groups: high-quality types and low-quality types.

The following parameter is changed: IP path type.

Feature change

The support of operator-dependent Iub resource management is described in 3.10 Admission Control.

The following parameters are added:z Resource

Management Mode

z CN Operator index

1 TRM Change History RAN



Issue 02 (2008-07-30)

Change Type Change Description Parameter Change

A new value, UBR_PLUS has been added to the Service Type parameter in 3.1 ATM Transmission Resources.

The following parameter is changed: Service Type.

In 3.5 Traffic Type and Transmission Resource Mapping: z The command for setting the mapping

relationship between the traffic types and transmission resources is changed from ADD ADJNODE to ADD ADJMAP.

z Traffic Type of interactive service in the TRMMAP tables has been changed.

None

The command for setting the factor is changed from ADD ADJNODE to ADD ADJMAP in 3.8 Activity Factor.

None

The R99 and HSPA service admission control algorithm is added in 3.10 Admission Control.

None

More detailed technical description of group bandwidth management is added in 3.7 Transport Layer Group Bandwidth Management, such as description of transmission resource group.

None

Description of multi-level admission control policy is added in 3.10 Admission Control.

None

A new parameter has been added in 3.11 Congestion Control.

The following parameter is added: NodeB name.

Editorial change General documentation change: Implementation information has been moved to a separate document.

None

RAN Transmission Resource Management Description 2 TRM Introduction


2-1

2 TRM Introduction Transmission Resource Management (TRM) is used to manage user plane resoIub, Iur, and Iu interfaces in the Radio Network Controller (RNC). By using

urces on the TRM, it is

ss(QoS

z ub,

z d Iu-CS interfaces.

z GPRS Tunneling Protocol for User Plane (GTP-U) resources, IP over ATM (IPoA) bandwidth resources, and IP path bandwidth resources on the Iu-Packet Switched (PS)

Impact z

This feature has no impact on system performance. r Features

Network ElemT -1 th o s) in

Table 2-1 Es involv in TR

po ible to increase the transmission resource usage and to guarantee the Quality of Service ).

The following transmission resources are managed by the TRM modules:

Channel Identifier (CID) resources, and bandwidth resources for AAL2 paths on the IIur, and Iu-Circuit Switched (CS) interfaces. User Datagram Protocol (UDP) resources, and bandwidth resources for IP paths on the Iub, Iur, an

interface.

Impact on System Performance

z Impact on OtheThis feature has no impact on other features.

ents Involved able 2 describes e Netw rk Elements (NE involved TRM.

N ed M

UE NodeB RNC MSC Server MGW SGSN GGSN HLR

2 TRM Introduction RAN



Issue 02 (2008-07-30)

UE NodeB RNC MSC Server MGW SGSN GGSN HLR

NOTE: z : not involved z : involved UE = User Equipment, RNC = Radio Network Controller, MSC = Mobile Service Switching Center, MGW = Media Gateway, SGSN = Serving GPRS Support Node, GGSN = Gateway GPRS Support Node, HLR = Home Location Register

RAN Transmission Resource Management Description 3 TRM Principles


3-1

3 TRM Principles The TRM principles provide information about the technical aspects of TRM, including the

urces in the different modes and the affic types. The TRM principles also

v like Differentiated Services (DiffServ), admission control a d a

e ter.

on Resources

Transmission Resource Mapping ice

Bandwidth Management

z Iub Overbooking z Admission Control

3.1 ATM Transmission Resources the physical layer resources and the AAL2 path

3.1.1 ATM P yer Resources

interface is carried on the IP over ATM (IPoA) Permanent Virtual an

llowing trans :

parameters and algorithms used, the transmission resomapping between the transmission resources and trpro ide information about functions n ctivity factors.

Th following lists the contents of this chap

z ATM Transmission Resources z IP Transmission Resources z Iub ATM/IP Transmissiz Paths on the Iur, Iu-CS, and Iu-PS Interfaces z Traffic Type andz Differentiated Servz Transport Layer Group z Activity Factor

z Congestion Control

The ATM transmission resources consist of resources. ATM Virtual Port (VP) shaping is used to solve downlink Iub congestion problems.

hysical LaIn ATM mode, the user plane data for the Iub/Iur/Iu-CS interfaces is carried on AAL2 paths, and data for the Iu-PSCh nel (PVC).

Data for the terrestrial interfaces is transmitted on the physical layer in one of the fomission modes

z E1/T1: Electrical ports of the AEUa board are used for data transmission.

3 TRM Principles RAN



Issue 02 (2008-07-30)

z Channelized STM-1/OC-3: Optical ports of the AOUa board are used for data transmission.

-3c: Optical ports of the UOIa board are used for data

Table 3-1 describes the ATM interface boards and their transmission mode

T

z Unchannelized STM-1/OCtransmission.

s.

able 3-1 ATM interface boards

Description Transmission Mode

Board

AEUa AEUa refers to the RNC 32-port ATM over E1/T1 interface unit (REV: a). z

onal ATMnal IMA

The AEUa supports interfaces such as Iu-CS, Iur, and Iub.

z UNI IMA

z Fractiz Fractioz Virtual Port

(VP)

AOUa AOUa refers to the RNC 2-port ATM over channeoptical STM-1/OC-3 interface unit (REV: a).

lized z IMA z Virtual Port

(VP) The AOUa supports interfaces such as Iu-CS, Iur, and Iub.

z UNI

UOIa UOIa refers to the RNC 4-port ATM/packet over unchannelized optical STM-1/OC-3c interface unit (REV: a).

NCOPT

The UOIa supports interfaces such as Iu-CS, Iu-PS, Iu-BC, Iur, and Iub.

T describes t tifier (VPI) an el Identifier (VCI) range as well as the service types for the ATM interface boards.

Table 3-2 VPI/VCI r for ATM int

able 3-2 he Virtual Path Iden d Virtual Chann

ange and service types erface boards

Board VPI /VCI Range Service Type

AEUa z VPI: 0 to 255 z 35 z

S

VCI: 32 to 655

z CBR RTVBR

z NRTVBR z UBR z U PLUBR_

AOUa z VPI: 0 to 255 z 35 z

S

VCI: 32 to 655

z CBR RTVBR

z NRTVBRz UBR z UBR_PLU



3-3

Board VPI /VCI Range Service Type

UOIa z VPI: 0 to 255 z VCI: 32 to 65535

z CBR z RTVBR z NRTVBR z UBR z UBR_PLUS

figured with Minimum Cell Rate (MCR).

3.1.2 AAL2 Path Resources L rses describes the AAL2 path resource parameters, and the mappings

type and service type parameters.

z HSUPA_RT

acket Access (HSDPA) and High Speed Uplink Packet Access (HSUPA) traffic can be carried on the same AAL2 path. HSDPA is carried on the downlink

T ervic 2 p Service type parameters is determined by TX traffic record index or RX traffic r index parameter.

Ta 3-3 describes the recommended mappi and Service type p ters. The service type priority in desc r is: CBR > RTVBR > NRTVBR > UBR or UBR_PLUS.

T g between AAL2 path type

UBR_PLUS is the UBR con

AA 2 Path Recoubetween AAL2 path

In ATM mode, the AAL2 path types are as follows:

z RT z NRT z HSDPA_RT z HSDPA_NRT

z HSUPA_NRT

High Speed Downlink P

and HSUPA is carried on the uplink.

he AAL2 path type is related to the Sath type and

ecord

e type parameter. The mapping between AAL

ble ng between AAL2 path typearame ending orde

able 3-3 Mappin and service type parameters

Values for the AAL2 Path Type Parameter

Values for the Service Type Parameter

RT CBR, or RTVBR

NRT NRTVBR

HSDPA_RT CBR, or RTVBR

HSDPA_NRT NRTVBR, UBR, or UBR_PLUS

HSUPA_RT CBR, or RTVBR

HSUPA_NRT NRTVBR, UBR, or UBR_PLUS




Issue 02 (2008-07-30)

3.1.3 ATM VirtATM

wn nd pack

To a

z ping rate is the Iub bandwidth corresponding to each NodeB. The shaping bandwidth of each VP is configured to avoid

z g rate of the hub VP is lower

z Ensure that the actual rate of the VPs does not exceed the bandwidth of the physical port.

ual Port Shaping VP shaping is applied on the port of ATM interface boards and is used to solve

do link Iub congestion problems, which decrease the risk of transmission congestion aet loss.

void congestion in the ATM network:

Configure a leaf VP aiming at each NodeB. The VP sha

congestion occurring on each NodeB and access point of the transport network. Configure a hub VP aiming at each Hub NodeB. The VP connecting to the hub VP corresponds to the actual NodeB networking. The shapinthan or equal to the Iub bandwidth of the Hub NodeB.

Otherwise, congestion may occur on the physical port.

The sum of the configured VP bandwidth can exceed the bandwidth of the upper-level VP (or of the physical port) because the VPs can be converged upon admission. For the actual traffic, however, the sum of VP traffic will not exceed the traffic of the upper-level VP.

If these conditions are met, congestion will not occur on the NodeB Iub interface.

problems. One principle of RNC back pressure algorithm is congestion detection, , see 3.10 Admission ub Overbooking.

Solution to Congestion th leaf VPs and

VP shaping also supports admission control, congestion control and back pressure algorithm. The RNC back pressure algorithm can be applied to VP shaping, which will solve Iub congestion which requires the shaping function at the transport layer. For detailsControl, 3.11 Congestion Control and Flow Control Algorithm 2 for I

Based on VP Shaping The RNC supports multi-level shaping (up to level-5 shaping), which has bohub VPs.

Figure 3-1 shows the VPs corresponding to the multi-level NodeB.



3-5

Figure 3-1 VPs corresponding to multi-level NodeB.

NB = NodeB, BW = bandwidth, BW0 = bandwidth of the physical port

e convergence may occur in the ) or in the Hub NodeB (for

must

s of ub VP and physical port.

z

3.2 IP Transmission Resources The IP transmission resources consist of the physical, and data link layer resources as well as the IP path resources. IP Logical Port (LP) shaping is used to solve downlink Iub congestion problems and IP Performance Management (PM) is used to ensure that the total transmit rate does not exceed the current actual available bandwidth.

z Multiple NodeBs are converged at the Iub interface. Thtransport network (such as NB1 and NB4 in Figure 3-1example, NB2 and NB3 are converged at NB1, as shown in Figure 3-1). The VPs be configured to provide an appropriate convergence solution.

z The leaf VP actual rate is restricted by the leaf VP shaping rate, and scheduling ratethe h

The VP shaping parameters involved are as follows:

z Type of the virtual portz The Virtual Port Number z The bearing type of the virtual port z The Upper Virtual port Number

Forward bandwidth [kpbs] z Backward bandwidth [kpbs] z Bearing VP No.




Issue 02 (2008-07-30)

3.2.1 Physic Layer Resources T ns ces include the physical layer and da

I de, Iu-PS ces is carried on UDP/IP.

Data for the cal layer in one of the following transmission m

z E1/T1: Electrical ports of the PEUa board are used for datz /GE daz Optica sed for data transmission. z Uncha are used for data

transm

Ta desc

Table 3-4 IP

al and Data Link he IP tra mission resour ta link layer resources.

n IP mo the user plane data of the Iub, Iur, Iu-CS, and interfa

terrestrial interfaces is transmitted on the physiodes:

a transmission. FE : Electrical ports of the FG2a board are used for

l GE: Optical GE ports of the GOUa board are unnelized ST

ta transmission.

M-1/OC-3c: Optical ports of the UOIa board ission

ble 3-4 ribes the IP interface boards.

interface boards

Board Description Transmission Mode

PEUa PEUa refers to the RNC 32-port packet oE1/T1 interface unit (REV: a). The PEUa supports the

ver

IP-based Iub, Iur, and z MCPPP ux

C2507)

Iu-CS interfaces.

z PPP z MLPPP

z PPPMz IPHC (RF

FG2a

The FG2a supports the IP-based Iub, Iur, Iu-CS, and Iu-PS interfaces.

FG2a refers to the RNC packet over electronic 8-port FE or 2-port GE Ethernet interface unit (REV: a).

IP over Ethernet

GOUa GOUa refers to the RNC 2-port packet over IP over Ethernet optical GE Ethernet interface unit (REV: a). The GOUa supports the IP-based Iub, Iur, Iu-CS, and Iu-PS interfaces.

UOIa The board provides four unchannelized STM-1/OC-3c optical ports and supports IP

z PPP z PPPMux

over SDH/SONET.

P Ua POUa refers to the O port packet over M-1/OC-3 interface unit

z PPP z PPPMux z MLPPP

PP

groups in T1 mode

RNC 2-channelized optical ST(REV: a). The POUa provides two IP over channelized STM-1/OC-3 optical ports and supports IP over E1/T1 over SDH/SONET.

z Supporting 42 MLPgroups in E1 mode

z Supporting 64 MLPPP



3-7

The user plane data of Iub, Iur, and Iu-CS interfaces is encapsulated through the UDP, IP, and layer 2 (L2). An independent UDP port is allocated to each data flow.

Multi-link PPP (MLPPP)

(MCPPP)

address and control or protocol fields can be applied on the

n resources when the E1 is used on the Iub interface. For details about the data link layer, refer to IP RAN Header Compression.

If L2 is carried on the Ethernet, the data can be encapsulated in the format shown in Figure

F sulat

L2 can be carried on either the E1 or the Ethernet (FE/GE). If L2 is carried on the E1, the data can be encapsulated on the basis of the following protocols:

z Point to Point Protocol (PPP) zz PPP Multiplexing (PPPMux) z Multi-Class PPP

The compression of thePPP/MLPPP/PPPMux link. In addition, the IP header compression technology can also be used to save the transmissio

3-2.

igure 3-2 Encap ion format of the Ethernet data

The 802).

3.2.2 IP Path Resources I des IP p c t

T h pe.

Tab between

data encapsulation complies with RFC894 and RFC1042 (IEEE

P Path Resources cribes the IP path type parameters, and the mappings between theype. ath type and traffi

able 3-5 describes t e mapping between IP path type and the recommended traffic ty

le 3-5 Mapping IP path type and traffic type

IP Path Type Recommended Traffic Type

HQ_RT LQ_RT

Common channel messages Signaling Radio Bearer (SRB)

tablished on DCHs

AMR voice CS conversational and streaming services PS conversational and streaming services es

HQ_NRT LQ_NRT

PS BE services established on DCHs

HQLQ

_HSDPART _HSDPART

PS conversational and streaming services established on HSDPA channels

HQ_HSDPANRT PS interactive and background services established on HSDPA channels LQ_HSDPANRT




Issue 02 (2008-07-30)

IP Path Type Recommended Traffic Type

HQ_HSUPART LQ_HSUPART

PS conversatichannels

onal and streaming services established on HSUPA

HQ_HSUPANRT LQ_HSUPANRT

PS interactive and background services established on HSUPA channels

HQ_QOSPATH Any service type cpriority of the QOLQ_QOSPATH

an be carried on the QOSPATH. The transmission SPATH is configurable, so different service types

can be transmitted with different priorities.

et transport. This difference is ission

nlink Iub ckets

z a bandwidth g e sha to avoid

congestion oc on each t of th port network. z Ensure that th rate of the b th of the physical port.

Otherwise, co may oc

If these conditions t, congest cur on the Nod

LP shaping also su dmissio estion control The RNC back pre gorithm to LP shapingcongestion problem ple of pressure algori tection,

hich requires the shaping function in the transmission layer. For details, see 3.10 Admission , 3.11 Congestion Control and Flow Control Algorithm 2 for Iub Overbooking.

Solution to CoTable 3-6 describes the interface board capacity of LP shaping and IP Performance Management (PM).

Table 3-6 Interface board capacity of LP shaping and IP PM

z High Quality (HQ) and Low Quality (LQ) differ in bearer type. HQ is based on IP over E1/T1 transport, whereas LQ is based on IP over Etherndue to the fact that compared with IP transport, E1/T1 transport has low transmdelay, thus featuring a high quality.

z The IP path also needs to be configured, even if the Iu-PS interface adopts IPoA for transmission.

z HSDPA and HSUPA traffic can be carried on the same IP path. HSDPA is carried on the downlink and HSUPA is carried on the uplink.

3.2.3 IP Logical Port Shaping IP LP shaping is applied on the port of IP interface boards, and is used to solve dowcongestion problems, which will decrease the risk of transmission congestion and paloss.

To avoid congestion in the IP network:

Configure ancorrespondin

LP aiming at ea to NodeB. Th

ch NodeB. The LP shaping rping bandwidth of each LP

te is the Iub is configured

curring NodeB and access poin e transe actualngestion

the LPs does not exceedcur on the physical port.

andwid

are me ion will not oc eB Iub interface.

pports a n control, cong and back pressure algorithm. ssure als. One princi

can be appliedRNC back

, which will solve Iub thm is congestion de

wControl

ngestion Based on LP Shaping

Bearing Type Board Type Capacity of LP Shaping Remarks

IP PEUa Does not support LP. None



3-9

Bearing Type Board Type Capacity of LP Shaping Remarks

POUa Does not support LP. None

FG2a Supports LP. LP level-1 shaping + IP PM

GOUa Supports LP. LP level-1 shaping + IP PM

UOIa Supports LP. LP level-1 shaping

For details about IP PM, see 3.2.4 IP Performance Management.

Figure 3-3 shows the back pressure solution of LP level-1 shaping.

Figure 3-3 Back pressure solution of LP level-1 shaping

NB = NodeB, BW = bandwidth, BW0 = bandwidth of the physical port

aim at each NodeB. The shaping rate of the leaf LP is

qual to or less than the bandwidth of the physical port.

z The LPs (LP1, LP2, LP3, and LP4)equal to the Iub bandwidth of each NodeB.

z The bandwidth of the four LPs must be e

The configured LP can exceed the bandwidth of the physical port (with a convergence based

, but the sum of the actual traffic will not exceed the traffic of upper-level LP.

e

z z Re

on the admission algorithm)

Th LP shaping parameters involved are as follows:

Logic port No. source management mode




Issue 02 (2008-07-30)

3.2.4 IP PerformaIn th cintroduc back pressure.

to dynamically detect the actual available bandwidth and ensure that the total tran

The

z

ard Monitoring (FM) packet including the send packet count and time stamp to the NodeB.

et to erate a Backward Reporting (BR) packet and then sends it to RNC.

nce Management e a tual network, bandwidth-varying scenario exists. In this scenario, the IP PM is

ed on the basis of LP

IP PM is usedsmit rate does not exceed the current actual available bandwidth.

solution is the following:

If LP back pressure is implemented, congestion and packet loss do not occur at the LP. z The RNC and NodeB work together to implement IP PM in the following way:

The RNC sends a Forw

The NodeB adds the receive packet count and time stamp on the FM packgen

The RNC estimates the available bandwidth, depending on the BR packet, and adjusts the LP rate.

e dynamic adjustment of the LP Th depends on the IP PM detection result. If the Auto adjust

bandwidth switch parameter is set to ON when configuring the LP, the IP PM of all the IP paths bound on this LP must be activated. Then, the system dynamically adjusts the

information obtained by the IP

bandwidth of the LP according to the Iub transmission qualityPM.

z The estimated available bandwidth is also used for admission algorithms. For details, see3.10 Admission Control.

If these conditions are met, congestion will not occur on the NodeB Iub interface.

z If the Auto adjust bandwidth switch parameter is set to ON, you should configure the

Max bandwidth [64kbps] and the Min bandwidth [64kbps]. only configure the

ssion Resources

ATM transmission resources, see3.1 ATM Transmission about the IP transmission resources, see 3.2 IP

3.4 Paths o is similar to TRM of the Iub interface.

z If the Auto adjust bandwidth switch parameter is set to OFF, you canbandwidth of a fixed logical port.

3.3 Iub ATM/IP TransmiThe Iub ATM/IP mode consists of the ATM transport part and the IP transport part. The ATM and IP transmission resources are independent and configured separately.

For more information about the Resources, and for more information Transmission Resources.

n the Iur, Iu-CS, and Iu-PS Interfaces TRM of the Iur, Iu-CS and Iu-PS



3-11

3.4.1 Paths on Iur Interface Services carried on the Iur interface are diversified. Therefore, the types of paths configureon the Iur interfa

d ce are the same as those on the Iub interface.

3.4.2 Paths o

Q_RT and LQ_RT as d LQ_QOSPATH types need to be configured in IP mode.

3.4.3 Paths o

M or IP mode.

3.5 Traffic Transmis cT n traffic types and ion resources gured for each a de.

W t mapping is added, d pping indexe igned to users with d . The RNC provides pping tables AP tables). The m fic types, inc fic handling p the transport bearer is co ADD TRMMA mand, and the m g of the gold, silver, or c ured through the MAP comma

3.5.1 ATM M Ta apping recommended for the ATM-based Iub/I r/Iu-CS interfaces. P erre and seconda pe is used when the adm l

T for sed Iub/Iur/Iu-CS interfaces

n Iu-CS Interface Services carried on the Iu-CS interface are AMR voice services, CS conversational services and CS streaming services, all of which are real-time services. Therefore, the AAL2 paths of RT type need to be configured in ATM mode, and the IP paths of Hwell as HQ_QOSPATH an

n Iu-PS Interface For the resource management of the Iu-PS interface, the IP paths of NRT or HQ_QOSPATHand LQ_QOSPATH types are used in AT

Type and sion Resour e Mapping he mapping betwee transmiss can be confidjacent no

hen an adjacenifferent priorities

ifferent ma default ma

s are ass(TRMM

apping between the trafnfigured through the

luding trafP com

riority, andappin

opper type is config ADD ADJ nd.

apping Tableble 3-7 shows the m u

rimary path type refers to the pref d path type ry path tyission to the primary path type fai s.

able 3-7 Mapping recommended the ATM-ba

Traffic Type Primary Pa Secondth Type ary Path Type

Common channel ATMRT NULL

SRB ATMRT NULL

AMR voice ATMRT NULL

R99 CS conversational ATMRT NULL

R99 CS streaming ATMRT NULL

R99 PS conversational ATMRT NULL

R99 PS streaming ATMRT NULL

R99 PS interactive high priority ATMNRT NULL

R99 PS interactive middle priority ATMNRT NULL




Issue 02 (2008-07-30)

Traffic Type Primary Path Type Secondary Path Type

R99 PS interactive low priority ATMNRT NULL

R99 PS background ATMNRT NULL

HSDPA Signal ATMHDRT NULL

HSDPA conversational ATMHDRT NULL

HSDPA streaming ATMHDRT NULL

HSDPA interactive high priority ATMHDNRT NULL

HSDPA interactive middle priority ATMHDNRT NULL

HSDPA interactive low priority ATMHDNRT NULL

HSDPA background ATMHDNRT NULL

HSUPA Signal ATMHURT NULL

HSUPA conversational ATMHURT NULL

HSUPA streaming ATMHURT NULL

HSUPA interactive high priority T ATMHUNR NULL

HSUPA interactive middle priority T ATMHUNR NULL

HSUPA interactive low priority T ATMHUNR NULL

HSUPA background ATMHUNRT NULL

3.5.2 IP MapTa apping recommended for e IP-based Iub/IP erre d seconda pe is used when the adm l

T for th /Iur/Iu-CS s

ping Table ble 3-8 shows the m th ur/Iu-CS interfaces.

rimary path type refers to the pref d path type an ry path tyission to the primary path type fai s.

able 3-8 Mapping recommended e IP-based Iub interface

Traffic Type Primary Pat Secondh Type ary Path Type

Common channel HQ_IPRT NULL

SRB HQ_IPRT NULL

AMR voice HQ_IPRT NULL

R99 CS conversational HQ_IPRT NULL

R99 CS streaming HQ_IPRT NULL

R99 PS conversational HQ_IPRT NULL

R99 PS streaming HQ_IPRT NULL

R99 PS interactive high priority HQ_IPNRT NULL



3-13


R99 PS interactive middle priority HQ_IPNRT NULL

R99 PS interactive low priority HQ_IPNRT NULL

R99 PS background HQ_IPNRT NULL

HSDPA Signal HQ_IPHDRT NULL

HSDPA conversational HQ_IPHDRT NULL

HSDPA streaming HQ_IPHDNRT NULL

HSDPA interactive high priority HQ_IPHDNRT NULL

HSDPA interactive middle priority HQ_IPHDNRT NULL

HSDPA interactive low priority HQ_IPHDNRT NULL

HSDPA background HQ_IPHDNRT NULL

HSUPA Signal HQ_IPHURT NULL

HSUPA conversational HQ_IPHURT NULL

HSUPA streaming HQ_IPHURT NULL

HSUPA interactive high priority NRT HQ_IPHU NULL

HSUPA interactive middle priority NRT HQ_IPHU NULL

HSUPA interactive low priority NRT HQ_IPHU NULL

HSUPA background HQ_IPHUNRT NULL

3.5.3 ATM/IP le Table 3-9 shows the mapping recommended for the ATM/IP-based Iub interface. Primary path t a path type i admission to the prim

T for th sed Iub inte

Mapping Tab

ype refers to the preferred path type nd secondary s used when theary path type fails.

able 3-9 Mapping recommended e ATM/IP-ba rface

Traffic Type Primary Pa Secondary Pth Type ath Type

Common channel ATMRT HQ_IPRT

SRB ATMRT HQ_IPRT

AMR voice ATMRT HQ_IPRT

R99 CS conversational ATMRT HQ_IPRT

R99 CS streaming ATMRT HQ_IPRT

R99 PS conversational ATMRT HQ_IPRT

R99 PS streaming ATMRT HQ_IPRT




Issue 02 (2008-07-30)


R99 PS interactive high priority ATMNRT HQ_IPNRT

R99 PS interactive middle priority ATMNRT HQ_IPNRT

R99 PS interactive low priority ATMNRT HQ_IPNRT

R99 PS background ATMNRT HQ_IPNRT

HSDPA Signal ATMHDRT HQ_IPHDRT

HSDPA conversational ATMHDRT HQ_IPHDRT

HSDPA streaming ATMHDRT HQ_IPHDRT

HSDPA interactive high priority HQ_IPHDNRT ATMHDNRT

HSDPA interactive middle priority HQ_IPHDNRT ATMHDNRT

HSDPA interactive low priority HQ_IPHDNRT ATMHDNRT

HSDPA background HQ_IPHDNRT ATMHDNRT

HSUPA Signal ATMHURT HQ_IPHURT

HSUPA conversational ATMHURT HQ_IPHURT

HSUPA streaming ATMHURT HQ_IPHURT

HSUP HQ_IPHUNRT ATMHUNRT A interactive high priority

HSUPA interactive middle priority HQ_IPHUNRT ATMHUNRT

HSUPA interactive low priority HQ_IPHUNRT ATMHUNRT

HSUPA background HQ_IPHUNRT ATMHUNRT

The default TRMMAP tables can be modified with the SET DEFAULTTRMMAP command.

The

z z z z

3.6 Differentiated Service ) is a method of providing different services with

different transmission priorities.

A new mapping table index is added with the ADD TRMMAP command, and the mappingtable index is modified with the MOD TRMMAP command.

parameters that are used to modify the mapping are as follows:

TRMMAP ID Gold user TRMMAP index Silver user TRMMAP index

Copper user TRMMAP index

The Differentiated Service (DiffServ



3-15

3.6.1 DiffSe

z

ements for transmission error rate and reduce the overhead processing. FTP is less sensitive to delay and jitter but does not

ansmission errors.

3.6.2 DiffSee flow control of the channels that carry HSDPA services is

managed by the NodeB.

vices. That is, independent AAL2 paths or IP paths must be configured to carry the services of HSDPA_RT type or HSDPA_NRT type as follows:

BE services established on HSDPA channels are carried on the paths of HSDPA_NRT

3.6.3 DiffSees of

th PVC such as NRTVBR.

3.6.4 DiffSeIP Code Point (DSCP) is applied to implement the ffS et that enables different services to be transmitted with fe he same network environment, the greater the DSCP

value has.

default DSCP values for IP paths of non-QOSPATH type, run the ADD IPP

The DSCP for the IP path of QOSPATH type is classified into EF,AF11,AF12,AF13,AF21,AF22,AF23,AF31,AF32,AF33,AF41,AF42,AF43,BE. The transmission priorities from high to low are EF > AF43 > AF42 > AF41 > AF33 > AF32 >

rv Based on QoS DiffServ is implemented according to different QoS requirements of the different services.

The voice service requires short delay and small jitter but allows a certain rate of transmission errors. To minimize the delay and jitter, the high-quality transmission medium with the shortest path is allocated to the voice service. The Transparent Mode (TM) is applied to meet the requir

z The PS BE service such as e-mail orallow transmission errors. Relatively low-quality transmission medium is allocated to the PS BE service, and the retransmission mechanism of the Acknowledged Mode (AM) ensures no tr

rv Based on HSDPA If the NodeB supports HSDPA, th

Without the differentiated transmission measures, the outburst of HSDPA data transmission can affect both the voice services and the R99 data services. Therefore, differentiated transmission must be applied to HSDPA ser

z PS streaming services established on HSDPA channels are carried on the paths of HSDPA_RT type.

z PStype.

rv Based on ATM PVC In ATM mode, the ATM PVC priority is applied to implement the DiffServ. Different typservice can be carried on different PVCs with different transmission priorities.

For example, the RT path type uses high-priority PVC such as CBR or RTVBR, and NRT patype uses low-priority

rv Based on DSCP In mode, the Differentiated Service Di erv. DSCP is a field in an IP packdif rent priorities on the network. In t

higher priority the traffic is, the

Different IP paths can be configured with different DSCPs, which means that different services can be transmitted by using different DSCPs. For example, the RT path type is configured with high-priority DSCP, and the NRT path type is configured with low-priority DSCP.

To modify theATH command or MOD IPPATH command.




Issue 02 (2008-07-30)

AF31 > AF23 > AF22 > AF21 > AF13 > AF12 > AF11 > BE. The default DSCP vathem are as follows:

lues for

: 34

the

s and IP port queues is set through the SET QUEUEMAP command.

z EF: 46 z AF43: 38 / AF42: 36 / AF41z AF33: 30 / AF32: 28 / AF31: 26 z AF23:22 / AF22: 20 / AF21: 18 z AF13: 14 / AF12: 12 / AF11: 10 z BE: 0

The DSCP for the IP path of QOSPATH type is determined by the traffic mapping, andDSCP for the IP path of non-QOSPATH type is configured on the IP path. The mapping between the DSCP value

If the data is transmitted on the leased lines, the IP address and DSCP values of the IP paths should be configured according to the Service Level Agreement (SLA).

3.7 Transport Layer Group Bandwidth Management Tr sport Layer Group Bandwidth Management is used to manage different types of paths configured on the Iub interface.

an

Tran sources through admi ths under one transmission resou dwidth of the group. That is, all the paths urce group.

Whe and FRAATM), or a logical

signa ndwidth is used by the user plane.

ission control and congestion control described in the following sections are based on the bandwidth for the user plane of the transport layer. For example, the

nd l link mentioned above refers to the bandwidth for the user plane of ayer.

l and Management Planes

CP/ALCAP and the OAM flow is reserved for the control plane: Reserved bandwidth = bandwidth of the NCP x Factor of NBAP_NCP+ bandwidth of the CCP x Factor of NBAP_CCP+ bandwidth of the ALCAP x Factor of ALCAP+ OM bandwidth of the NodeB x Factor of IUB_OAM

z In IP transport, the bandwidth of the OAM flow is reserved for the control plane: Reserved bandwidth = OM bandwidth of the NodeB x Factor of IUB_OAM

smission resource group multiplexes and converges the transport layer ression control. For example, the bandwidth of all the parce group can be configured as the same as the ban can share the bandwidth of the transmission reso

n you configure a physical link (for example, IMA, UNI,port (VP or LP), the bandwidth for the control and management planes (including the

ling NCP/CCP/ALCAP and the OAM flow) is reserved, and the remaining ba

The transport layer adm

ba width for the physicathe transport l

3.7.1 Bandwidth Reserved for ControThe bandwidth reserved in ATM transport and in IP transport is different:

z In ATM transport, the bandwidth of the signaling NCP/C



3-17

The parameters used to calculate the reserved bandwidth for the control and management planes are as follows:

3.7.2 Trand physical port constitute the structure of the RNC

ansmission resource management, as Figure 3-4 shown.

z Application Type z Factor

smission Resource Group The path, transmission resource group, antr

Figure 3-4 The structure of the RNC transmission resource management

Run the ADDNCOPT, ETH

PORTCTRLER command to add port resource controllers for IMA, UNI, FRAATM, ER, PPP, and MLPPP.

e

rce group.

ed tails, see 3.10

Admission Control.

3.8 Activit

data is transmitted. The activity factor is used by the admission control to increase the transmission resource usage during these periods.

n be applied on the Iub, Iur, Iu-CS, and Iu-PS interfaces and by actor, more users of a service can be admitted.

to the vice activity factor. For the PS Best Effort e same as the Guaranteed Bit Rate (GBR)

multiplied by the service activity factor.

sers for common channel and SRB are the same. For details, refer inciples.

Run the ADD LGCPORT, ADD VP, and ADD RSCGRP commands to add the transmission resourcgroups on the RNC. In the broad sense, a port controller also serves as a resource group, namely, a top-level resou

The port controller and transmission resource group (including the VP, LP, or customizresource group) are related to transmission resource admission control. For de

y Factor Due to the discontinuity of traffic, there are active periods during which data is transmitted and inactive periods during which no

The activity factors caadjusting the activity f

In most cases, when a service is established, the service admission bandwidth is equal required transmission bit rate multiplied by the ser(BE) service, the service admission bandwidth is th

The activity factors for all uto Iub Overbooking Key Pr




Issue 02 (2008-07-30)

3.9 Iub Overbooking Iub overbooking is used to increase transmission resource usage on the Iub interface.

For details, refer to Iub Overbooking Description.

3.10 Admission Control resources are enough to accept a

he new user's access request is

he admission control of the RNC transmission resources adopts a bottom-up multi-level ission control policy.

Admission Control is used to determine whether the systemnew user's access request. If the system resources are enough, taccepted; otherwise, the user will be rejected.

3.10.1 Multi-Level Admission Control Policy Tadm

Figure 3-5 shows a bottom-up multi-level admission control policy.

Figure 3-5 Bottom-up multi-level admission control policy

As shown in Figure 3-5, a user accessing the network from a path should go through the admission of the path, resource group, and physical port in turn. The user that passes all the admission can be successfully admitted by the transport layer.

The physical ports correspond to IMA, UNI, FRAATM, NCOPT, ETHER, PPP, and MLPPP. The transmission resource groups are of two types: the one automatically generated in the system and the one manually generated by the user. The latter one can only perform admission control but is not capable of shaping or back pressure.

Figure 3-6 shows the multi-level admission control policy for the RNC transmission resources.



3-19

Figure 3-6 Multi-level admission control policy for the RNC transmission resources

Hub VP1, Leaf VP1, Leaf VP2, and Leaf VP3 are the four VPs configured by users, which correspond to four transmission resource groups. The user accessing the network from the NB2 should go through the admission of AAL2PATH, LeafVP1, HubVP1, physical port, and the user accessing the network from the NB4 should go through the admission of AAL2PATH, Leaf VP3, and physical port.

3.10.2 Admission Control Algorithm This section describes the admission control algorithm and takes the physical link as an example. The admission control policy for the transmission resource group is the same as that for the physical link.

The requirements for the general algorithm for bandwidth admission control vary with whether it is a new user, a handover user, or a rate upsizing user that is requiring admission.

For a new user, the following requirements apply:

z Total bandwidth allocated to the users on the path + required bandwidth for the new user < total bandwidth configured for the path bandwidth reserved for handover.

z Total bandwidth allocated to the users on the physical link + required bandwidth for the new user < total bandwidth of the physical link bandwidth reserved for handover.

For a handover user, the following requirements apply:

z Total bandwidth allocated to the users on the path + required bandwidth for the handover user < total bandwidth configured for the path.

z Total bandwidth allocated to the users on the physical link + required bandwidth for the handover user < total bandwidth of the physical link.

For a rate upsizing user, the following requirements apply:




Issue 02 (2008-07-30)

z Total bandwidth allocated to the users on the path + required bandwidth for the rate upsizing user < total bandwidth configured for the path congestion threshold.

z Total bandwidth allocated to the users on the physical link + required bandwidth for the rate upsizing user < total bandwidth of the physical link congestion threshold.

Physical link users consist of R99 users and HSPA users. For R99 users, the UL and DL control admission together. For HSPA users, the UL and DL control admission separately. First the UL controls admission. If the UL admission for HSPA users is approved, the DL controls admission and if the UL admission for HSPA users is rejected, the DL does not control admission.

Table 3-10 describes the admission control procedures for different combinations of services as well as UL and DL.

Table 3-10 R99 and HSPA service admission control

Service If... Then...

UL admission fails Admission is rejected with the message "RAB ASSIGNMENT RESPONSE" and the reason is "Requested Maximum Bit Rate for UL not Available".

DL admission fails Admission is rejected with the message "RAB ASSIGNMENT RESPONSE" and the reason is "Requested Maximum Bit Rate for DL not Available".

UL R99 + DL R99

Both UL and DL admission fail Admission is rejected with the message "RAB ASSIGNMENT RESPONSE" and the reason is "Requested Maximum Bit Rate not Available".

UL R99 + DL HSDPA UL admission fails Admission is rejected with the message "RAB ASSIGNMENT RESPONSE" and the reason is "Requested Maximum Bit Rate for UL not Available".



3-21



Both UL and DL admission fail Admission is rejected with the message "RAB ASSIGNMENT RESPONSE" and the reason is "Requested Maximum Bit Rate for UL not Available".

UL admission fails Admission is rejected with the message "RAB ASSIGNMENT RESPONSE" and the reason is "Requested Maximum Bit Rate for UL not Available".


UL HSUPA + DL R99


UL HSUPA + DL HSDPA UL admission fails Admission is rejected with the message "RAB ASSIGNMENT RESPONSE" and the reason is "Requested Maximum Bit Rate for UL not Available".




Issue 02 (2008-07-30)




z For a path that belongs to a path group, admission control must be performed at both the path level and the path group level.

z 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 Resource Management Mode parameter is used for configuring a virtual port, or logical port on the Iub interface.

The CN Operator index can be used when setting the Resource Management Mode parameter.

The admission control algorithm has the following requirement for the parameter settings:

Bandwidth reserved for handover congestion threshold congestion resolve threshold

The congestion threshold and the congestion resolve threshold are used to prevent ping-pong effect.

Based on the preceding requirement, the user priorities are as follows:

Handover user > new user > rate upsizing user

The congestion thresholds consist of Forward congestion threshold and Backward congestion threshold, and the congestion resolve thresholds consist of Forward congestion clear threshold and Backward congestion clear threshold. For details, see 3.11 Congestion Control.

The parameters that are used for reserving bandwidth for handover users are as follows:

z Forward handover reserved bandwidth[KBIT/S] z Backward handover reserved bandwidth[KBIT/S]

3.10.3 Admission Procedure Primary and secondary paths are used in admission control. According to the mapping between traffic types and transmission resources, the RNC first selects the primary path for admission. If the admission on the primary path fails, then the admission on the secondary



3-23

path is performed. For details about the mapping between traffic types and transmission resources, see 3.5 Traffic Type and Transmission Resource Mapping.

For example, assume that secondary paths are available for new users, handover users, and rate upsizing users. The following procedures describe the admission of these users on the Iub interface respectively.

The admission procedure for a new user is as follows:

Step 1 The new user tries to be admitted to available bandwidth 1 of the primary path, as shown in 1 of Figure 3-7.

Step 2 If the admission on the primary path is successful, the user is carried on the primary path.

Step 3 If the admission on the primary path fails, the user tries to be admitted to available bandwidth 2 of the secondary path, as shown in 2 of Figure 3-7.

Step 4 If the admission on the secondary path is successful, the user is carried on the secondary path. If not, the bandwidth admission request of the user is rejected.

----End

Figure 3-7 Admission procedure for a new user

Available bandwidth 1 = total bandwidth of the primary path - used bandwidth - handover reserved bandwidth Available bandwidth 2 = total bandwidth of the secondary path - used bandwidth - handover reserved bandwidth

The admission procedure for a handover user is as follows:

Step 1 The handover user tries to be admitted to available bandwidth 1 of the primary path, as shown in 1 of Figure 3-8.




----End




Issue 02 (2008-07-30)

Figure 3-8 Admission procedure for a handover user

Available bandwidth 1 = total bandwidth of the primary path - used bandwidth Available bandwidth 2 = total bandwidth of the secondary path - used bandwidth

The admission procedure for a rate upsizing user is as follows:

Step 1 The rate upsizing user tries to be admitted to available bandwidth 1 of the primary path, as shown in 1 of Figure 3-9.




----End

Figure 3-9 Admission procedure for a rate upsizing user

Available bandwidth 1 = total bandwidth of the primary path - used bandwidth - congestion reserved bandwidth Available bandwidth 2 = total bandwidth of the secondary path - used bandwidth - congestion reserved bandwidth

If no secondary paths are available for the users, the admission is performed only on the primary paths.



3-25

3.11 Congestion Control Congestion Control describes the congestion detection method and the congestion handling on the Iub interface.

3.11.1 Congestion Detection Method The Forward congestion threshold and Backward congestion threshold parameters can be set for congestion detection when a path, port, or resource group is configured. The default value for both of the parameters is 0, which indicates that no congestion detection is performed. If the parameters are specified, the TRM performs congestion detection based on the parameter values. For a path, port, or resource group, it is also possible to set the Forward congestion clear threshold and Backward congestion clear threshold parameters, both of which are used to determine whether the congestion disappears.

Congestion detection can be triggered in either of the following ways:

z Bandwidth adjustment because of resource allocation, modification or release. z Change in the configured bandwidth or the congestion threshold. z Physical link fault.

For example, if the forward parameters of a port for congestion detection are defined as follows, with CLEAR being greater than CON:

z Configured bandwidth: AVE z Forward congestion threshold: CON z Forward congestion clear threshold: CLEAR z Used bandwidth: USED

Then, the mechanism of congestion detection on the port is as follows:

z The congestion occurs on the path when CON + USED AVE. z The congestion disappears from the path when CLEAR + USED < AVE.

The congestion detection for a path or resource group is similar to that for a port.

Generally, congestion thresholds only need to be set for a port or resource group. If different types of AAL2 paths or IP paths require different congestion thresholds, the parameters for the paths are set as required.

If a VP or LP is configured, congestion control is also applied to the VP or LP, and the congestion control mechanism is the same as that of a resource group.

3.11.2 Congestion Handling on the Iub Interface If congestion is detected when NodeB LDC algorithm switch is set to IUB_LDR-1, the RNC triggers the load reshuffling process after receiving the congestion alarm messages.

The congestion alarm only indicates limited bandwidth; it does not indicate that no users can connect to the network. If NodeB LDC algorithm switch is set to IUB_LDR-1, you should run the ADD NODEBLDR command to add NodeB LDR algorithm parameters and run ADD NODEBLDR to specify a unique NodeB name.

For details about the load reshuffling process, refer to Load Reshuffling.




Issue 02 (2008-07-30)

Congestion on other interface is described:

z Congestion detected on the Iur interface may trigger the SRNS relocation. For details, refer to Basic Types of SRNS Relocation.

z During flow control on Iu signaling, when congestion is detected on the signaling link towards a signaling point, the congestion status is reported to the RANAP subsystem. Then, the RANAP subsystem starts to discard user messages for services in the following order: short message > CS and PS call establishment > registration.

RAN Transmission Resource Management Description 4 TRM Parameters


4-1

4 TRM Parameters This chapter provides information on the effective level and configuration of the parameters

T meters .

Tab rs related to

related to TRM.

able 4-1 lists the para related to TRM

le 4-1 Paramete TRM

Parameter Name Effective Level Configuration Parameter IDon...

AAL2 path type PT DD RNC AAL2 Path(AAAL2PATH)

TX traffic record index TXTRFX D RNC IPOAPVC(ADIPOAPVC) AAL2 Path(ADD AAL2PATH)

RX traffic record index

RFX RXT SAAL(ADD SAALLNK) AAL2 Path(ADD AAL2PATH)

RNC

Service type ST SAALLNK/AAL2PATH/IPOAPVC/VPCLCX

RNC

using this ATM traffic record index(ADD ATMTRF)

IP path type PATHT ATH) IP Path(ADD IPP RNC

DSCP DSCP TH) RNC IP Path(ADD IPPA

Application Type rface

CTRLFACTOR)

TYPE control intelink(SET

RNC

Factor FACTOR RNC(SET CTRLFACTOR)

RNC

4 TRM Parameters RAN



Issue 02 (2008-07-30)


Forward handover reserved bandwidth[KBIT/S]

FWDHORSVBW

Port(ADD PORTCTRLER) Transmission resource group(ADD RSCGRP) IP Path(ADD IPPATH) AAL2 Path(ADD AAL2PATH) LGCPORT(ADD LGCPORT) VP(ADD VP)

RNC

Backward handover reserved bandwidth[KBIT/S]

BWDHORSVBW


RNC

CN Operator index CnOpIndex RNC(ACT LICENSE) RNC

Forward congestion threshold[KBIT/S]

FWDCONGBW

AAL2 Path(ADD AAL2PATH) IP Path(ADD IPPATH) Transmission resource group(ADD RSCGRP) Port(ADD PORTCTRLER) VP(ADD VP) LGCPORT(ADD LGCPORT)

RNC

Backward congestion threshold[KBIT/S]

BWDCONGBW


RNC

RAN Transmission Resource Management Description 4 TRM Parameters


4-3


Forward congestion clear threshold[KBIT/S]

FWDCONGCLRBW


RNC

Backward congestion clear threshold[KBIT/S]

BWDCONGCLRBW


RNC

NodeB LDC algorithm switch

NodeBLdcAlgoSwitch

NodeB(ADD NODEBALGOPARA)

RNC

Type of the virtual port

LPNTYPE VP(ADD VP)

RNC

The Virtual Port Number

VP VP(ADD VP)

RNC

The bearing type of the virtual port

CARRYT VP(ADD VP)

RNC

The Upper Virtual port Number

UPPERVP VP(ADD VP)

RNC

Forward bandwidth [kpbs]

TXBW VP(ADD VP)

RNC

Backward bandwidth [kpbs]

RXBW VP(ADD VP)

RNC

Bearing VP No. CARRYVPN AAL2 Path(ADD AAL2PATH) IPOAPVC(ADD IPOAPVC)

RNC

Logic port No. LPN LGCPORT(ADD LGCPORT)

RNC

Resource management mode

RSCMNGMODE

LGCPORT(ADD LGCPORT)

RNC

4 TRM Parameters RAN



Issue 02 (2008-07-30)


Auto adjust bandwidth switch

BWADJ LGCPORT(ADD LGCPORT)

RNC

Max bandwidth [64kbps]

MAXBW LGCPORT(ADD LGCPORT)

RNC

Min bandwidth [64kbps]

MINBW LGCPORT(ADD LGCPORT)

RNC

NodeB name NodeBName NodeB(ADD NODEBLDR)

RNC

TRMMAP ID TMI RNC(ADD TRMMAP) RNC

Gold user TRMMAP index

TMIGLD Adjacent Node(ADD ADJMAP)

RNC

Silver user TRMMAP index

TMISLV Adjacent Node(ADD ADJMAP)

RNC

Copper user TRMMAP index

TMIBRZ Adjacent Node(ADD ADJMAP)

RNC

RAN Transmission Resource Management Description 5 TRM Reference Documents


5-1

5 TRM Reference Documents TRM Reference Documents lists the reference documents related to the feature.

ITU-T Recommendation I.361: B-ISDN ATz M Layer Specification tation layer specification: Type 2 AAL

z g for ATM (IMA) Specification Version 1.1

ides a standard method for

z RFC3153: PPP Multiplexing (PPPmux) z RFC894: Standard for the Transmission of IP Datagrams over Ethernet Networks z RFC1042: A Standard for the Transmission of IP Datagrams over IEEE 802 Networks

z ITU-T Recommendation I.363.2: ATM Adapz ITU-T Recommendation I.366.1: Segmentation and Reassembly Service Specific

Convergence Sublayer for the AAL type 2 AF-TM-0121.000: Traffic Management 4.1

z AF-PHY-0086.001: Inverse Multiplexinz RFC1661: The Point-to-Point Protocol (PPP), prov

transporting multi-protocol datagrams over point-to-point links z RFC1662: PPP in HDLC-link Framing z RFC1990: The PPP Multilink Protocol (ML-PPP) z RFC2686: The Multi-Class Extension to Multi-link PPP (MC-PPP)

1 TRM Change History 2 TRM Introduction 3 TRM Principles 3.1 ATM Transmission Resources 3.1.1 ATM Physical Layer Resources 3.1.2 AAL2 Path Resources 3.1.3 ATM Virtual Port Shaping

IP Transmission Resources 3.2.1 Physical and Data Link Layer Resources 3.2.2 IP Path Resources 3.2.3 IP Logical Port Shaping 3.2.4 IP Performance Management

3.3 Iub ATM/IP Transmission Resources 3.4 Paths on the Iur, Iu-CS, and Iu-PS Interfaces 3.4.1 Paths on Iur Interface 3.4.2 Paths on Iu-CS Interface 3.4.3 Paths on Iu-PS Interface

3.5 Traffic Type and Transmission Resource Mapping 3.5.1 ATM Mapping Table 3.5.2 IP Mapping Table 3.5.3 ATM/IP Mapping Table

3.6 Differentiated Service 3.6.1 DiffServ Based on QoS 3.6.2 DiffServ Based on HSDPA 3.6.3 DiffServ Based on ATM PVC 3.6.4 DiffServ Based on DSCP

3.7 Transport Layer Group Bandwidth Management 3.7.1 Bandwidth Reserved for Control and Management Planes 3.7.2 Transmission Resource Group

3.8 Activity Factor 3.9 Iub Overbooking 3.10 Admission Control 3.10.1 Multi-Level Admission Control Policy 3.10.2 Admission Control Algorithm 3.10.3 Admission Procedure

3.11 Congestion Control 3.11.1 Congestion Detection Method 3.11.2 Congestion Handling on the Iub Interface

4 TRM Parameters 5 TRM Reference Documents

transmission resource management description

Documents

huawei trademarks

huawei proprietary

ip transmission resources

ltdhuawei technologies

atm transmission resources

ip path resources

huawei industrial base

atm physical layer resources