Transmission Resource Management Description(2008!05!30)

RAN

Transmission Resource Management Description Issue 01

Date 2008-05-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

http://www.huawei.com/

mailto:[email protected]

RAN Transmission Resource Management Description Contents

Issue 01 (2008-05-30) Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

i

Contents

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

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

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

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

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

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

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

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

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

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

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

Contents RAN

Transmission Resource Management Description

ii Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd

Issue 01 (2008-05-30)

3.10.1 Multi-Level Admission Control Policy............................................................................................3-19 3.10.2 Admission Control Algorithm..........................................................................................................3-20 3.10.3 Admission Procedure .......................................................................................................................3-23

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

4 TRM Reference Documents .....................................................................................................4-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

01 (2008-05-30) 10.0 V200R010C01B051 V100R010C01B049V200R010C01B040

Draft (2008-03-20) 10.0 V200R010C01B050 V100R010C01B045

nagement feature of a specific product version.

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

01 (2008-05-30This is the document for the first commercial release of RAN10.0.

C d with draft (2008-03-20) of RAN10.0, issue 01 (2008-05-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

addition of information that is not provided in the previous ver

)

ompareorpor

Change Change Description Parameter Change Type

The DSCP values of QOSPATH have increased. For details, see DiffServ Based on DSCP in 3.6 Differentiated Service.

None Feature change

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

None

1 TRM Change History RAN


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

Issue 01 (2008-05-30)

Change Change Description Parameter Change Type

Editorial change

General documentation change: The Transmission Resource Management Parameters is removed because of the creation of RAN10.0 parameter reference.

The structure is optimized.

None

Draft (2008-03-20) This 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.

Change Type Change Description Parameter Change

The topic 3.2.3 IP Logical Port Shaping is added.

The following parameters are added:

Logic port No. Resource Management Mode

Feature change

The topic 3.2.4 IP Performance Management is added.


Auto adjust bandwidth switch

Min bandwidth [64kbps]

Max bandwidth [64kbps]

RAN Transmission Resource Management Description 1 TRM Change History


1-3


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


Type of the virtual port

The Virtual Port Number

The bearing type of the virtual port

The Upper Virtual port Number

Forward bandwidth [kpbs]

Backward bandwidth [kpbs]

Bearing VP No.

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

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.

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


Resource Management Mode

CN Operator index

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:

The command for setting the mapping relationship between the traffic types and transmission resources is changed from ADD ADJNODE to ADD ADJMAP.

λ 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

1 TRM Change History RAN



Issue 01 (2008-05-30)


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. For information on how to implement TRM, see Configuring Transmission Resource Management in RAN Feature Configuration Guide.

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

ub,

d Iu-CS interfaces.

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 ance

ance.

atures

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 Perform

This feature has no impact on system perform

Impact on Other Fe

This 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 01 (2008-05-30)

UE NodeB RNC MSC Server MGW SGSN GGSN HLR

NOTE: –: not involved √: 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 parameters and algorithms used, the transmission resources in the different modes and the mapping between the transmission resources and traffic types. The TRM principles also

about functions like Differentiated Services (DiffServ), admission control

About Thi

T e conten

provide information and activity factors.

s Chapter

he following table lists th ts of this chapter.

Section Describes

3.1 ATM Transmission The ATM transmission resources consist of the physical Resources layer resources and the AAL2 path resources. ATM

Virtual Port (VP) shaping is used to solve downlink Iub congestion problems.

3.2 IP Transmission Resourcesources.

ort (LP) shaping is used to solve downlink Iub congestion problems and IP Performance

The IP transmission resources consist of the physical, and data link layer resources as well as the IP path resIP Logical P

Management (PM) is used to ensure that the total transmit rate does not exceed the current actual available bandwidth.

3.3 Iub ATM/IP TransmissioResources

n sport part. The ATM and IP transmission

The Iub ATM/IP mode consists of the ATM transport part and the IP tranresources are independent and configured separately.

3.4 Paths on the Iur, Iu-Cand Iu-PS

S, Interfaces Iub interface.

TRM of the Iur, Iu-CS and Iu-PS is similar to TRM of the

3.5 Traffic Type and Transmission Resource Mapping

The mapping between traffic types and transmission resources can be configured for each adjacent node.

3 TRM Principles RAN



Issue 01 (2008-05-30)

Section Describes

3.6 Differentiated Service The Differentiated Service (DiffServ) is a method of providing different services with different transmission priorities.

3.7 Transport Layer Group Bandwidth Management b

Transport Layer Group Bandwidth Management is used to manage different types of paths configured on the Iuinterface.

3.8 Activity Factoractive periods

ol to increase the transmission

Due to the discontinuity of traffic, there are active periods during which data is transmitted and induring which no data is transmitted. The activity factor is used by the admission contrresource usage during these periods.

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

3.10 Admission Controlenough to accept a new user's access

r's

rejected.

Admission Control is used to determine whether the system resources are request. If the system resources are enough, the new useaccess request is accepted; otherwise, the user will be

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



3-3

3.1 ATM Transmission Resources The ATM transmission resources consist of the physical layer resources and the AAL2 path resources. ATM Virtual Port (VP) shaping is used to solve downlink Iub congestion problems.

3.1.1 ATM Physical Layer Resources In ATM mode, the user plane data for the Iub/Iur/Iu-CS interfaces is carried on AAL2 paths, and data for the Iu-PS interface is carried on the IP over ATM (IPoA) Permanent Virtual Channel (PVC).

Data for the terrestrial interfaces is transmitted on the physical layer in one of the following transmission modes:

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

transmission. Unchannelized STM-1/OC-3c: Optical ports of the UOIa board are used for data

transmission.

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

Table 3-1 ATM interface boards

Board Description Transmission Mode

AEUa AEUa refers to the RNC 32-port ATM over E1/T1 interface unit (REV: a). The AEUa supports interfaces such as Iu-CS, Iur, and Iub.

UNI IMA Fractional ATM Fractional IMA Virtual Port (VP)

AOUa AOUa refers to the RNC 2-port ATM over channelized optical STM-1/OC-3 interface unit (REV: a). The AOUa supports interfaces such as Iu-CS, Iur, and Iub.

UNI IMA Virtual Port (VP)

UOIa UOIa refers to the RNC 4-port ATM/packet over unchannelized optical STM-1/OC-3c interface unit (REV: a). The UOIa supports interfaces such as Iu-CS, Iu-PS, Iu-BC, Iur, and Iub.

NCOPT

Table 3-2 describes the Virtual Path Identifier (VPI) and Virtual Channel Identifier (VCI) range as well as the service types for the ATM interface boards.




Issue 01 (2008-05-30)

Table 3-2 VPI/VCI range and service types for ATM interface boards

Board VPI /VCI Range Service Type

AEUa VPI: 0 to 255 VCI: 32 to 65535

CBR RTVBR NRTVBR UBR UBR_PLUS

AOUa VPI: 0 to 255 VCI: 32 to 65535


UOIa VPI: 0 to 255 VCI: 32 to 65535


UBR_PLUS is the UBR configured with Minimum Cell Rate (MCR).

3.1.2 AAL2 Path Resources AAL2 Path Recourses describes the AAL2 path resource parameters, and the mappings between AAL2 path type and service type parameters.

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

RT NRT HSDPA_RT HSDPA_NRT HSUPA_RT HSUPA_NRT

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

The AAL2 path type is related to the Service type parameter. The mapping between AAL2 path type and Service type parameters is determined by TX traffic record index or RX traffic record index parameter.

Table 3-3 describes the recommended mapping between AAL2 path type and Service type parameters. The service type priority in descending order is: CBR > RTVBR > NRTVBR > UBR or UBR_PLUS.



3-5

Table 3-3 Mapping between AAL2 path type 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

3.1.3 ATM Virtual Port Shaping ATM VP shaping is applied on the port of ATM interface boards and is used to solve downlink Iub congestion problems, which decrease the risk of transmission congestion and packet loss.

To avoid congestion in the ATM network:

Configure a leaf VP aiming at each NodeB. The VP shaping rate is the Iub bandwidth corresponding to each NodeB. The shaping bandwidth of each VP is configured to avoid 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 shaping rate of the hub VP is lower than or equal to the Iub bandwidth of the Hub NodeB.

Ensure that the actual rate of the VPs does not exceed the bandwidth of the physical port. 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.

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 problems. One principle of RNC back pressure algorithm is congestion detection, which requires the shaping function at the transport layer. For details, see 3.10 Admission Control, 3.11 Congestion Control and Flow Control Algorithm 2 for Iub Overbooking.

Solution to Congestion Based on VP Shaping The RNC supports multi-level shaping (up to level-5 shaping), which has both leaf VPs and hub VPs.

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




Issue 01 (2008-05-30)

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

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

Multiple NodeBs are converged at the Iub interface. The convergence may occur in the transport network (such as NB1 and NB4 in Figure 3-1) or in the Hub NodeB (for example, NB2 and NB3 are converged at NB1, as shown in Figure 3-1). The VPs must be configured to provide an appropriate convergence solution.

The leaf VP actual rate is restricted by the leaf VP shaping rate, and scheduling rates of the hub VP and physical port.

The VP shaping parameters involved are as follows:

Type of the virtual port The Virtual Port Number The bearing type of the virtual port The Upper Virtual port Number Forward bandwidth [kpbs] Backward bandwidth [kpbs] Bearing VP No.

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



3-7

congestion problems and IP Performance Management (PM) is used to ensure that the total transmit rate does not exceed the current actual available bandwidth.

3.2.1 Physical and Data Link Layer Resources The IP transmission resources include the physical layer and data link layer resources.

In IP mode, the user plane data of the Iub, Iur, Iu-CS, and Iu-PS interfaces is carried on UDP/IP.

Data for the terrestrial interfaces is transmitted on the physical layer in one of the following transmission modes:

E1/T1: Electrical ports of the PEUa board are used for data transmission. FE/GE: Electrical ports of the FG2a board are used for data transmission. Optical GE: Optical GE ports of the GOUa board are used for data transmission. Unchannelized STM-1/OC-3c: Optical ports of the UOIa board are used for data

transmission

Table 3-4 describes the IP interface boards.

Table 3-4 IP interface boards

Board Description Transmission Mode

PEUa PEUa refers to the RNC 32-port packet over E1/T1 interface unit (REV: a). The PEUa supports the IP-based Iub, Iur, and Iu-CS interfaces.

PPP MLPPP MCPPP PPPMux IPHC (RFC2507)

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

IP over Ethernet

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

IP over Ethernet

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

PPP PPPMux

POUa POUa refers to the RNC 2-port packet over channelized optical STM-1/OC-3 interface unit (REV: a). The POUa provides two IP over channelized STM-1/OC-3 optical ports and supports IP over E1/T1 over SDH/SONET.

PPP PPPMux MLPPP Supporting 42 MLPPP groups in E1 mode

Supporting 64 MLPPP groups in T1 mode




Issue 01 (2008-05-30)

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.

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:

Point to Point Protocol (PPP) Multi-link PPP (MLPPP) PPP Multiplexing (PPPMux) Multi-Class PPP (MCPPP)

The compression of the address and control or protocol fields can be applied on the PPP/MLPPP/PPPMux link. In addition, the IP header compression technology can also be used to save the transmission 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 3-2.

Figure 3-2 Encapsulation format of the Ethernet data

The data encapsulation complies with RFC894 and RFC1042 (IEEE 802).

3.2.2 IP Path Resources IP Path Resources describes the IP path type parameters, and the mappings between the IP path type and traffic type.

Table 3-5 describes the mapping between IP path type and the recommended traffic type.

Table 3-5 Mapping between IP path type and traffic type

IP Path Type Recommended Traffic Type

HQ_RT LQ_RT

Common channel messages Signaling Radio Bearer (SRB) AMR voice CS conversational and streaming services PS conversational and streaming services established on DCHs

HQ_NRT LQ_NRT

PS BE services established on DCHs

HQ_HSDPART LQ_HSDPART

PS conversational and streaming services established on HSDPA channels



3-9

IP Path Type Recommended Traffic Type

HQ_HSDPANRT LQ_HSDPANRT

PS interactive and background services established on HSDPA channels

HQ_HSUPART LQ_HSUPART

PS conversational and streaming services established on HSUPA channels

HQ_HSUPANRT LQ_HSUPANRT

PS interactive and background services established on HSUPA channels

HQ_QOSPATH LQ_QOSPATH

Any service type can be carried on the QOSPATH. The transmission priority of the QOSPATH is configurable, so different service types can be transmitted with different priorities.

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 Ethernet transport. This difference is due to the fact that compared with IP transport, E1/T1 transport has low transmission delay, thus featuring a high quality.

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

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 downlink Iub congestion problems, which will decrease the risk of transmission congestion and packets loss.

To avoid congestion in the IP network:

Configure an LP aiming at each NodeB. The LP shaping rate is the Iub bandwidth corresponding to NodeB. The shaping bandwidth of each LP is configured to avoid congestion occurring on each NodeB and access point of the transport network.

Ensure that the actual rate of the LPs does not exceed the bandwidth of the physical port. Otherwise, congestion may occur on the physical port.


LP shaping also supports admission control, congestion control and back pressure algorithm. The RNC back pressure algorithm can be applied to LP shaping, which will solve Iub congestion problems. One principle of RNC back pressure algorithm is congestion detection, which requires the shaping function in the transmission layer. For details, see 3.10 Admission Control, 3.11 Congestion Control and Flow Control Algorithm 2 for Iub Overbooking.

Solution to Congestion Based on LP Shaping Table 3-6 describes the interface board capacity of LP shaping and IP Performance Management (PM).




Issue 01 (2008-05-30)

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

Bearing Type Board Type Capacity of LP Shaping Remarks

PEUa Does not support LP. None

POUa Does not support LP. None

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

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

IP

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

The LPs (LP1, LP2, LP3, and LP4) aim at each NodeB. The shaping rate of the leaf LP is equal to the Iub bandwidth of each NodeB.

The bandwidth of the four LPs must be equal to or less than the bandwidth of the physical port.

The configured LP can exceed the bandwidth of the physical port (with a convergence based on the admission algorithm), but the sum of the actual traffic will not exceed the traffic of upper-level LP.

The LP shaping parameters involved are as follows:



3-11

Logic port No. Resource management mode

3.2.4 IP Performance Management In the actual network, bandwidth-varying scenario exists. In this scenario, the IP PM is introduced on the basis of LP back pressure.

IP PM is used to dynamically detect the actual available bandwidth and ensure that the total transmit rate does not exceed the current actual available bandwidth.

The solution is the following:

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

− The RNC sends a Forward Monitoring (FM) packet including the send packet count and time stamp to the NodeB.

− The NodeB adds the receive packet count and time stamp on the FM packet to generate a Backward Reporting (BR) packet and then sends it to RNC.

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

The dynamic adjustment of the LP 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 bandwidth of the LP according to the Iub transmission quality information obtained by the IP PM.

The estimated available bandwidth is also used for admission algorithms. For details, see 3.10 Admission Control.


Other IP PM parameters involved are as follows:

Max bandwidth [64kbps] Min bandwidth [64kbps]

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

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

If the Auto adjust bandwidth switch parameter is set to OFF, you can only configure the bandwidth of a fixed logical port.

3.3 Iub ATM/IP Transmission Resources The 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 ATM transmission resources, see 3.1 ATM Transmission Resources, and for more information about the IP transmission resources, see 3.2 IP Transmission Resources.




Issue 01 (2008-05-30)

3.4 Paths on the Iur, Iu-CS, and Iu-PS Interfaces TRM of the Iur, Iu-CS and Iu-PS is similar to TRM of the Iub interface.

3.4.1 Paths on Iur Interface Services carried on the Iur interface are diversified. Therefore, the types of paths configured on the Iur interface are the same as those on the Iub interface.

3.4.2 Paths on 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 HQ_RT and LQ_RT as well as HQ_QOSPATH and LQ_QOSPATH types need to be configured in IP mode.

3.4.3 Paths on Iu-PS Interface For the resource management of the Iu-PS interface, the IP paths of NRT or HQ_QOSPATH and LQ_QOSPATH types are used in ATM or IP mode.

3.5 Traffic Type and Transmission Resource Mapping The mapping between traffic types and transmission resources can be configured for each adjacent node.

When an adjacent mapping is added, different mapping indexes are assigned to users with different priorities. The RNC provides default mapping tables (TRMMAP tables). The mapping between the traffic types, including traffic handling priority, and the transport bearer is configured through the ADD TRMMAP command, and the mapping of the gold, silver, or bronze type is configured through the ADD ADJMAP command.

3.5.1 ATM Mapping Table Table 3-7 shows the mapping recommended for the ATM-based Iub/Iur/Iu-CS interfaces. Primary path type refers to the preferred path type and secondary path type is used when the admission to the primary path type fails.

Table 3-7 Mapping recommended for the ATM-based Iub/Iur/Iu-CS interfaces

Traffic Type Primary Path Type Secondary 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



3-13


R99 PS streaming ATMRT NULL

R99 PS interactive high priority ATMNRT NULL

R99 PS interactive middle priority ATMNRT NULL

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 ATMHUNRT NULL

HSUPA interactive middle priority ATMHUNRT NULL

HSUPA interactive low priority ATMHUNRT NULL

HSUPA background ATMHUNRT NULL

3.5.2 IP Mapping Table Table 3-8 shows the mapping recommended for the IP-based Iub/Iur/Iu-CS interfaces. Primary path type refers to the preferred path type and secondary path type is used when the admission to the primary path type fails.

Table 3-8 Mapping recommended for the IP-based Iub/Iur/Iu-CS interfaces


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




Issue 01 (2008-05-30)


R99 PS conversational HQ_IPRT NULL

R99 PS streaming HQ_IPRT NULL

R99 PS interactive high priority HQ_IPNRT NULL

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 HQ_IPHUNRT NULL

HSUPA interactive middle priority HQ_IPHUNRT NULL

HSUPA interactive low priority HQ_IPHUNRT NULL

HSUPA background HQ_IPHUNRT NULL

3.5.3 ATM/IP Mapping Table Table 3-9 shows the mapping recommended for the ATM/IP-based Iub interface. Primary path type refers to the preferred path type and secondary path type is used when the admission to the primary path type fails.

Table 3-9 Mapping recommended for the ATM/IP-based Iub interface


Common channel ATMRT HQ_IPRT

SRB ATMRT HQ_IPRT

AMR voice ATMRT HQ_IPRT

R99 CS conversational ATMRT HQ_IPRT



3-15


R99 CS streaming ATMRT HQ_IPRT

R99 PS conversational ATMRT HQ_IPRT

R99 PS streaming ATMRT HQ_IPRT

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

HSUPA interactive HQ_IPHUNRT ATMHUNRT

HSUPA background HQ_IPHUNRT ATMHUNRT

The default TRMMAP tables can be modified with the SET DEFAULTTRMMAP command. A new mapping table index is added with the ADD TRMMAP command, and the mapping table index is modified with the MOD TRMMAP command.

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

TRMMAP ID Gold user TRMMAP index Silver user TRMMAP index Bronze user TRMMAP index

3.6 Differentiated Service The Differentiated Service (DiffServ) is a method of providing different services with different transmission priorities.




Issue 01 (2008-05-30)

3.6.1 DiffServ 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 requirements for transmission error rate and reduce the overhead processing.

The PS BE service such as e-mail or FTP is less sensitive to delay and jitter but does not allow 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 transmission errors.

3.6.2 DiffServ Based on HSDPA If the NodeB supports HSDPA, the flow control of the channels that carry HSDPA services is managed by the NodeB.

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 services. 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:

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

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

3.6.3 DiffServ Based on ATM PVC In ATM mode, the ATM PVC priority is applied to implement the DiffServ. Different types of service 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 path type uses low-priority PVC such as NRTVBR.

3.6.4 DiffServ Based on DSCP In IP mode, the Differentiated Service Code Point (DSCP) is applied to implement the DiffServ. DSCP is a field in an IP packet that enables different services to be transmitted with different priorities on the network. In the same network environment, the greater the DSCP value is, the higher priority the traffic has.

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 the default DSCP values for IP paths of non-QOSPATH type, run the ADD IPPATH command or MOD IPPATH command.

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



3-17

transmission priorities from high to low are EF > AF43 >= AF42 >= AF41 > AF33 >= AF32 >= AF31 >= AF23 >= AF22 >= AF21 > AF13 >= AF12 >= AF11 > BE. The default DSCP values for them are as follows:

EF: 46 AF43 / AF42 / AF41: 38 AF33 / AF32 / AF31: 30 AF23 / AF22 / AF21: 18 AF13 / AF12 / AF11: 10 BE: 0

The DSCP for the IP path of QOSPATH type is determined by the traffic mapping, and the DSCP for the IP path of non-QOSPATH type is configured on the IP path. The mapping between the DSCP values and IP port queues is set through the SET QUEUEMAP command.

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 Transport Layer Group Bandwidth Management is used to manage different types of paths configured on the Iub interface.

Transmission resource group multiplexes and converges the transport layer resources through admission control. For example, the bandwidth of all the paths under one transmission resource group can be configured as the same as the bandwidth of the group. That is, all the paths can share the bandwidth of the transmission resource group.

When you configure a physical link (for example, IMA, UNI, and FRAATM), or a logical port (VP or LP), the bandwidth for the control and management planes (including the signaling NCP/CCP/ALCAP and the OAM flow) is reserved, and the remaining bandwidth is used by the user plane.

The transport layer admission 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 bandwidth for the physical link mentioned above refers to the bandwidth for the user plane of the transport layer.

3.7.1 Bandwidth Reserved for Control and Management Planes The bandwidth reserved in ATM transport and in IP transport is different:

In ATM transport, the bandwidth of the signaling NCP/CCP/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

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




Issue 01 (2008-05-30)

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

Application Type Factor

3.7.2 Transmission Resource Group The path, transmission resource group, and physical port constitute the structure of the RNC transmission resource management, as Figure 3-4 shown.

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

Run the ADD PORTCTRLER command to add port resource controllers for IMA, UNI, FRAATM, NCOPT, ETHER, PPP, and MLPPP. Run the ADD LGCPORT, ADD VP, and ADD RSCGRP commands to add the transmission resource groups on the RNC. In the broad sense, a port controller also serves as a resource group, namely, a top-level resource group.

The port controller and transmission resource group (including the VP, LP, or customized resource group) are related to transmission resource admission control. For details, see 3.10 Admission Control.

3.8 Activity Factor Due to the discontinuity of traffic, there are active periods during which data is transmitted and inactive periods during which no data is transmitted. The activity factor is used by the admission control to increase the transmission resource usage during these periods.

The activity factors can be applied on the Iub, Iur, Iu-CS, and Iu-PS interfaces and by adjusting the activity factor, more users of a service can be admitted.

In most cases, when a service is established, the service admission bandwidth is equal to the required transmission bit rate multiplied by the service activity factor. For the PS Best Effort (BE) service, the service admission bandwidth is the same as the Guaranteed Bit Rate (GBR) multiplied by the service activity factor.

The activity factors for all users for common channel and SRB are the same. For details, refer to Iub Overbooking Key Principles.



3-19

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 Admission Control is used to determine whether the system resources are enough to accept a new user's access request. If the system resources are enough, the new user's access request is accepted; otherwise, the user will be rejected.

3.10.1 Multi-Level Admission Control Policy The admission control of the RNC transmission resources adopts a bottom-up multi-level admission control policy.

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.




Issue 01 (2008-05-30)

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:

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.

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:

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

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



3-21

For a rate upsizing user, the following requirements apply:

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

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




Issue 01 (2008-05-30)



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



3-23




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

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:

Forward handover reserved bandwidth[KBIT/S] 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




Issue 01 (2008-05-30)

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



3-25

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.




Issue 01 (2008-05-30)

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:

Bandwidth adjustment because of resource allocation, modification or release. Change in the configured bandwidth or the congestion threshold. 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:

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

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

The congestion occurs on the path when CON + USED ≥ AVE. 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.

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

Congestion on other interface is described:



3-27

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

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 Reference Documents


4-1

4 TRM Reference Documents

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

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

g for ATM (IMA) Specification Version 1.1 ides a standard method for

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

ITU-T Recommendation I.363.2: ATM Adap 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

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

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)

Transmission Resource Management Description(2008!05!30)

Documents

Transcript of Transmission Resource Management Description(2008!05!30)