Common Transmission Resource Management On MBSC (SRAN6.0 - 01)

Common Transmission Resource Management
on MBSC
SRAN6.0
Feature Parameter Description

Issue 01
Date 2012-06-30

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2012. 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 purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute the warranty of any kind, express or implied.

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

SingleRAN
Common Transmission Resource Management on
MBSC Contents

Issue 01 (2012-06-30) Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd
i

Contents
1 Introduction ................................................................................................................................ 1-1
1.1 Scope ............................................................................................................................................ 1-1
1.2 Intended Audience ........................................................................................................................ 1-1
1.3 Change History .............................................................................................................................. 1-1
2 Overview of Co-TRM ................................................................................................................ 2-1
2.1 Definition ....................................................................................................................................... 2-1
2.2 Networking Requirements ............................................................................................................. 2-1
2.3 Benefits ......................................................................................................................................... 2-1
2.4 Feature Contents ........................................................................................................................... 2-1
3 Transmission Resources ........................................................................................................ 3-1
3.1 IP Physical Transmission Resources ............................................................................................ 3-1
3.2 IP LP Resources ........................................................................................................................... 3-1
3.3 IP Path Resources ........................................................................................................................ 3-2
4 Load Control .............................................................................................................................. 4-1
4.1 Common Load Thresholds ............................................................................................................ 4-1
4.2 Admission Control ......................................................................................................................... 4-1
4.2.2 Admission Decision .............................................................................................................. 4-2
4.2.3 Preemption ........................................................................................................................... 4-3
4.2.4 Queuing ................................................................................................................................ 4-3
4.3 Congestion Control and Overload Control .................................................................................... 4-3
4.3.1 Congestion Detection ........................................................................................................... 4-4
4.3.2 Overload Detection ............................................................................................................... 4-4
4.3.3 Congestion and Overload Handling ..................................................................................... 4-4
5 Engineering Guidelines ........................................................................................................... 5-1
6 Parameters ................................................................................................................................. 6-1
7 Counters ...................................................................................................................................... 7-1
8 Glossary ...................................................................................................................................... 8-1
9 Reference Documents ............................................................................................................. 9-1

SingleRAN
MBSC 1 Introduction

1-1

1 Introduction
1.1 Scope
This document describes the common management of transmission resources shared by GSM and
WCDMA networks over the Abis and Iub interfaces. The management process, known as common
transmission resource management (Co-TRM), covers the shared transmission resources, common
load control, and related parameters. Certain concepts or functions that are inherited from the original
GSM and WCDMA features are not described in detail in this document.
Co-TRM corresponds to feature MRFD-211503 Co-Transmission Resources Management on MBSC.
1.2 Intended Audience
This document is intended for:

Persons who need to understand the Common Transmission Resource Management on MBSC
feature

Engineers working on Huawei products

A good understanding of the functions of Transmission Resource Management (TRM) of GSM and WCDMA is presumed,
before this document is read. This knowledge can be achieved through the Transmission Resource Management Feature
Parameter Description of the GSM BSS and the Transmission Resource Management Feature Parameter Description of
the WCDMA RAN.
1.3 Change History
This section provides information on the changes in different document versions.
There are two types of changes, which are defined as follows:

Feature change: refers to the change in the Common Transmission Resource Management on MBSC
feature of a specific product version.

Editorial change: refers to the change in wording or the addition of the information that was not
described in the earlier version.
Document Issues
The document issues are as follows:

01 (2012-06-30)
01 (2012-06-30)
This is a new document.
This document is split from the Transmission Resource Management Feature Parameter Description of
issue 01 (2011-03-30) of SRAN6.0.
SingleRAN
MBSC 2 Overview of Co-TRM

2-1

2 Overview of Co-TRM
2.1 Definition
Co-TRM refers to the common management of transmission resources when the IP transmission
bandwidth is shared by the GSM and UMTS services of the MBTS. Co-TRM improves the usage of
transmission resources and ensures the transmission quality of services (QoS).
In the Co-TRM feature,

The GSM and UMTS services of the MBTS share one IP logical port (LP) if the IP over FE/GE is
adopted

The GSM and UMTS services of the MBTS share the PPP link/MLPPP group if the IP over E1/T1 is
adopted.
MBSC uniformly implement load control and traffic shaping in the shared IP LPs, PPP links, or MLPPP
group.
2.2 Networking Requirements
The Co-TRM networking must meet the following requirements:

The GSM+UMTS dual-mode controllers and the GSM+UMTS dual-mode base stations are deployed.

The GSM+UMTS dual-mode base stations share IP transmission resources over the Abis and Iub
interfaces.
For details about the common transmission networking, see the Common Transmission Feature
Parameter Description.
2.3 Benefits
The bandwidth resources are shared by the GSM and UMTS services between the MBSC and the
MBTS in resource pool manner. The uniform management of the bandwidth resources provides the
following benefits:
In case of a burst of GSM and UMTS services on the MBTS, the required transmission bandwidth
increases abruptly. In such a case, the MBSC performs the control and thus effectively reduces the
possibility of congestion.
For the bandwidth allocated to the GSM and UMTS services on the same MBTS, the MBSC uses
appropriate allocation policies to increase the usage of the transmission bandwidth.
2.4 Feature Contents
The main contents of the Co-TRM feature are as follows:

Transmission resources: In Co-TRM, the transmission resources, including IP LPs and IP physical
resources, are shared by the Abis and Iub interfaces. For details, see chapter 3 "Transmission
Resources."

Load control: Common load control is implemented within the IP LPs/PPP links/MLPPP groups on the
Abis and Iub interfaces. As the QoS is ensured, more users are admitted. For details, see chapter 4
"Load Control."
SingleRAN
MBSC 3 Transmission Resources

3-1

3 Transmission Resources
IP transmission resources include IP path resources, IP Logical Port (LP) resources, and physical
transmission resources. In the case of Co-TRM, the Abis and Iub interfaces share IP LPs/PPP
links/MLPPP groups, and IP LPs/PPP links/MLPPP groups share IP physical transmission resources.
Figure 3-1 shows examples of all types of transmission resources and the relations between the
resources.
Figure 3-1 Examples of transmission resources in the case of Co-TRM

3.1 IP Physical Transmission Resources
The IP physical transmission resources are as follows:

FE/GE Ethernet port

GE Ethernet port

Channelized STM-1/OC-3 port
Table 3-1 lists the shared interface boards for IP transmission in Co-TRM.
Table 3-1 Shared interface boards for IP transmission in Co-TRM
IP Interface Board IP Transmission Port at the
Physical Layer
Transmission Protocol at
the Data Link Layer
FG2c FE/GE port IP over Ethernet
GOUc GE port
POUc Channelized STM-1/OC-3 port PPP
MLPPP
3.2 IP LP Resources
IP LPs are used to configure bandwidth for transmission nodes and perform bandwidth-based admission
and traffic shaping to prevent congestion. Co-TRM allows the services on the Abis and Iub interfaces to
share the bandwidth within a logical port, thus implementing common admission control and traffic
shaping. For details about IP LPs, see the Transmission Resource Management Feature Parameter
SingleRAN
MBSC 3 Transmission Resources

3-2

Description of the WCDMA RAN and the Transmission Resource Management Feature Parameter
Description of the GSM BSS.

NOTE

In Co-TRM, IP LPs support five levels of aggregation.
3.3 IP Path Resources
In Co-TRM, GSM IP paths and WCDMA IP paths are independent of each other. They are not described
in this document. For details about IP path resources, see the Transmission Resource Management
Feature Parameter Description of the WCDMA RAN and the Transmission Resource Management
Feature Parameter Description of the GSM BSS.
SingleRAN
MBSC 4 Load Control

4-1

4 Load Control
The load control algorithm manages the transmission bandwidth and controls the transmission load. As
the QoS is ensured, more users are admitted. This document focuses on the common load control
performed within the IP LPs/PPP links/MLPPP groups on the Abis and Iub interfaces.
Load control applies to the admission process based on transmission resources. With the change of
transmission bandwidth, different load control functions are used. Load control involves admission
control, congestion control, and overload control.
4.1 Common Load Thresholds
In the admission process based on transmission resources, load and threshold are compared to
determine whether the admission is successful. Transmission load and admission threshold are
compared to determine whether the admission of a new user is successful; transmission load and
congestion control threshold are compared to trigger the congestion control process; transmission load
and overload control threshold are compared to trigger the overload control process. The common load
control of IP LPs/PPP links/MLPPP groups is based on common load thresholds.

Common handover reserved threshold (common admission control of a new user)

Common congestion control thresholds

Common overload control thresholds
For details about admission control thresholds, congestion control thresholds, and overload control
thresholds, see sections 4.2 "Admission Control" and 4.3 "Congestion Control and Overload Control."
A load threshold index list can be configured for a group of LPs/PPP links/MLPPP groups through the
ADD TRMLOADTH command.
4.2 Admission Control
Admission control is used to determine whether the transmission resources are sufficient to accept the
admission request from a user. If the transmission resources are sufficient, the admission request is
admitted; otherwise, the request is rejected.
Figure 4-1 shows the admission control during the request for transmission resources.
SingleRAN
MBSC 4 Load Control

4-2

Figure 4-1 Admission control during the request for transmission resources

As shown in Figure 4-1, when the users request transmission resources, the admission control process
is as follows:
1. The admission of transmission resources is decided. If the admission is successful, a user can obtain
transmission resources. If the admission fails, go to step 2. For details about admission decision, see
section 4.2.2 "Admission Decision."
2. The attempt to preempt resources is made. If the preemption is successful, a user can obtain
transmission resources. If the preemption fails or the preemption function is not supported, go to step
3. For details about preemption, see section 4.2.3 "Preemption."
3. The attempt for queuing is made. If the queuing is successful, a user can obtain transmission
resources. If the queuing fails or the queuing function is not supported, the admission based on
transmission resources fails. For details about queuing, see section 4.2.4 "Queuing."
4.2.2 Admission Decision
MBSC provides a common handover reserved threshold. When the transmission bandwidth exceeds the
threshold, the threshold-based admission of the newly accessed GSM and UMTS user is prohibited.
This avoids the situation that the handover cannot be performed and the call quality of the accessed
users is affected because the transmission resources are exhausted.
When the transmission bandwidth exceeds the threshold and there is bandwidth available for the
transmission, the GSM and UMTS handover users can still perform the threshold-based admission.
SingleRAN
MBSC 4 Load Control

4-3

4.2.3 Preemption
In the case of preemption, a high-priority user preempts the bandwidth from an admitted low-priority user
for admission of transmission resources.
If the admission based on IP LP/PPP link/MLPPP group resources fails, the GSM and WCDMA networks
trigger the preemption function separately when the following conditions are met:

The user who requests transmission resources supports preemption as defined in the user request.

The preemption function is enabled. The preemption switches of the GSM and WCDMA networks are
set separately.

In the GSM network, the preemption function is enabled through the ENPREEMPTTRANSADMT
parameter.
In the WCDMA network, the preemption function is enabled through the PreemptAlgoSwitch
parameter.
The preemption function works separately in the GSM and WCDMA networks. That is, a high-priority
GSM user preempts only a low-priority GSM user, and a high-priority WCDMA user preempts only a
low-priority WCDMA user.
The Co-TRM feature inherits the preemption function from the original GSM and WCDMA features. They
are not described in this document. For details about preemption, see the Transmission Resource
Management Feature Parameter Description of the WCDMA RAN and the Transmission Resource
Management Feature Parameter Description of the GSM BSS.
4.2.4 Queuing
In the queuing function, the user that requests transmission resources in the GSM or WCDMA network is
put in a separate queue to wait for free transmission resources.
If the user that requests transmission resources does not support the preemption function or the
preemption function fails, the GSM and WCDMA networks trigger the queuing function separately when
the following conditions are met:

The user that requests transmission resources supports queuing as defined in the user request.

The queuing function is enabled. The queuing switches of the GSM and WCDMA networks are set
separately.
In the GSM network, the queuing function is enabled through the ENQUETRANSADMT parameter.
In the WCDMA network, the queuing function is enabled through the QueueAlgoSwitch parameter.
The Co-TRM feature inherits the queuing function from the original GSM and WCDMA features. They
are not described in this document. For details about queuing, see the Transmission Resource
Management Feature Parameter Description of the WCDMA RAN and the Transmission Resource
Management Feature Parameter Description of the GSM BSS.
4.3 Congestion Control and Overload Control
Congestion control is used to prevent overload, reduce the transmission load, and increase the access
success rate. Overload control is used to quickly eliminate overload when transmission overload occurs,
and to reduce the adverse impact on high-priority users.
In Co-TRM, IP LPs/PPP links/MLPPP groups implement common congestion detection and overload
detection and define common congestion control thresholds.
This section describes the congestion control and overload control of IP LP/PPP link/MLPPP group
resources. The congestion control and overload control include:
SingleRAN
MBSC 4 Load Control

4-4

Congestion detection

Overload detection

Congestion and overload handling
4.3.1 Congestion Detection
The Co-TRM feature defines the common congestion control thresholds, based on which IP LPs/PPP
links/MLPPP groups implement common congestion detection.
The congestion control thresholds are as follows:

Congestion remain threshold: When the usage of transmission resources exceeds the congestion
remain threshold, the system considers that congestion occurs.

Congestion clear remain threshold: When the usage of transmission resources falls below the
congestion clear remain threshold, the system considers that congestion is cleared.
For parameters associated with the congestion detection thresholds, see section 4.1 "Common Load
Thresholds."
4.3.2 Overload Detection
The Co-TRM feature defines common overload control thresholds, based on which IP LPs/PPP
links/MLPPP groups implement common overload detection.
The overload control thresholds are as follows:

Overload remain threshold: When the usage of transmission resources exceeds the overload remain
threshold, the system considers that overload occurs.

Overload clear remain threshold: When the usage of transmission resources falls below the overload
clear remain threshold, the system considers that overload is cleared.

For parameters associated with the overload detection thresholds, see section 4.1 "Common Load
Thresholds."
4.3.3 Congestion and Overload Handling
When transmission resource congestion occurs, congestion control is started. During the congestion
control, the bandwidth requested by new GSM users and the bandwidth occupied by the admitted GSM
and WCDMA users are reduced. When transmission resource congestion is cleared, congestion control
is stopped.
When transmission resource overload occurs, overload control is started. During the overload control,
the admission of GSM and WCDMA users is prohibited and the bandwidth occupied by low-priority users
is released. When overload is cleared, overload control is stopped.
When the bandwidth is released, GSM and WCDMA networks reserve bandwidth according to the
configured proportion and also release the occupied bandwidth. If the bandwidth in one network cannot
be released and overload is not cleared, the bandwidth in the other network is released. The bandwidth
reservation proportion of the GSM and WCDMA networks is specified by the GSMBWRATE parameter.
In Co-TRM, congestion and overload of the GSM and WCDMA networks are handled separately. The
Co-TRM feature inherits the congestion and overload handling methods from the original GSM and
WCDMA features. They are not described in this document. For details about congestion and overload
handling see the Transmission Resource Management Feature Parameter Description of the WCDMA
RAN and the Transmission Resource Management Feature Parameter Description of the GSM BSS.
SingleRAN
MBSC 5 Engineering Guidelines

5-1

5 Engineering Guidelines
The requirements for co-transmission networking at the MBSC are as follows:

GSM+UMTS dual-mode base station controllers and GSM+UMTS dual-mode base stations are
deployed.

GSM+UMTS multi-mode base stations share IP LP/PPP/MLPPP transmission resources over the Abis
and Iub interfaces.
In Co-TRM networking, the GSM and UMTS services share LP/PPP/MLPPP resources. It is
recommended that the GSM and UMTS services use a common LP. The principles of configuring
bandwidth for an LP are as follows:

If an LP is carried on an Ethernet port (ETHER), the bandwidth of the LP should be lower than or equal
to that of ETHER. Assume that the bandwidth of ETHER could be 5 Mbit/s. Then, the bandwidth of the
LP could be 4 Mbit/s.

If an LP is carried on the PPP link, the bandwidth of the LP should be lower than or equal to that of
PPP link.

If an LP is carried on the MLPPP link, the bandwidth of the LP should be lower than or equal to that of
MLPPP link.
SingleRAN
MBSC 6 Parameters

6-1

6 Parameters
Table 6-1 Parameter description
Parameter ID NE MML Command Feature ID Feature Name Description
ENPREEMPTTRA
NSADMT
BSC6900 SET
BSCBASIC(Option
al)
GBFD-118605 IP QOS Meaning: When this
parameter is set to
"ON", if there are no
available Abis
transmission
resources, a
high-priority user
can preempt the
transmission
resources of a
low-priority user. If
the preemption
succeeds, a call
drop occurs at the
low-priority user.
GUI Value Range:
OFF(Off), ON(On)
Actual Value Range:
OFF, ON
Default Value: ON
Unit: None
ENQUETRANSAD
MT
BSC6900 SET
BSCBASIC(Option
al)
GBFD-118605 IP QOS Meaning: When this
parameter is set to
"ON", if there are no
available Abis
transmission
resources, the
BSC6900 starts the
queuing procedure
for the services to
wait for available
transmission
resources.
GUI Value Range:
OFF(Off), ON(On)
Actual Value Range:
OFF, ON
Default Value: ON
Unit: None
GSMBWRATE BSC6900 ADD
TRMLOADTH(Opti
onal)
MRFD-211503 GSM and
UMTS
Co-Transmissi
on Resources
Management
on MBSC
Meaning: Ratio of
bandwidth for GSM
services to the total
bandwidth in G/U
co-transmission.
During the overload
SingleRAN
MBSC 6 Parameters

6-2

handling, the
bandwidth of GSM
services and that of
UMTS services are
reduced based on
this ratio. If overload
persists when one
mode has no
bandwidth to
release, bandwidth
of the other mode
will be reduced.
GUI Value Range:
0~100
Actual Value Range:
0~100
Default Value: 80
Unit: %
PreemptAlgoSwitch BSC6900 SET
UQUEUEPREEMP
T(Optional)
WRFD-010505 Queuing and
Pre-Emption
Meaning:
Determines whether
preemption is
supported. When
this switch is
enabled, the RNC
allows privileged
users or services to
preempt cell
resources from the
users or services
with the preempted
attributes and lower
priority in the case of
cell resource
insufficiency. When
the switch is
disabled, the RNC
terminates the
service for the user
due to the failure in
cell resource
application.
GUI Value Range:
OFF, ON
Actual Value Range:
OFF, ON
Default Value: OFF
Unit: None
QueueAlgoSwitch BSC6900 SET
UQUEUEPREEMP
WRFD-010505 Queuing and
Pre-Emption
Meaning: Indicating
whether queue is
SingleRAN
MBSC 6 Parameters

6-3

T(Optional) supported. When a
user initiates a call,
if cell resources are
insufficient and the
user is queue
supportive, the RNC
tries to arrange this
user to join the
queue to increase
access success
ratio.
GUI Value Range:
OFF, ON
Actual Value Range:
OFF, ON
Default Value: OFF
Unit: None

SingleRAN
MBSC 7 Counters

7-1

7 Counters
There are no specific counters associated with this feature.
SingleRAN
MBSC 8 Glossary

8-1

8 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
SingleRAN
MBSC 9 Reference Documents

9-1

9 Reference Documents
[1] Transmission Resource Management Feature Parameter Description of the WCDMA RAN
[2] Transmission Resource Management Feature Parameter Description of the GSM BSS
[3] Common Transmission Feature Parameter Description of the SingleRAN

Common Transmission Resource Management On MBSC (SRAN6.0 - 01)

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Common Transmission Resource Management On MBSC (SRAN6.0 - 01)

Enviado por

Direitos autorais:

Formatos disponíveis

Common Transmission Resource Management

Você também pode gostar