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

SingleRAN
Common Transmission Resource

Management on MBSC Feature
Parameter Description
Issue
01
Date
2012-04-30
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. 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 a 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
Issue 01 (2012-04-30)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
SingleRAN
Common Transmission Resource Management on MBSC
Feature Parameter Description
Contents
Contents
1 About This Document..................................................................................................................1
1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
2 Overview.........................................................................................................................................3
2.1 Definition........................................................................................................................................................................3
2.2 Networking Requirements..............................................................................................................................................3
2.3 Benefits...........................................................................................................................................................................3
2.4 Feature Contents.............................................................................................................................................................4
3 Transmission Resources...............................................................................................................5
3.1 IP Physical Transmission Resources..............................................................................................................................6
3.2 IP LP Resources..............................................................................................................................................................6
3.3 IP Path Resources...........................................................................................................................................................6
4 Load Control...................................................................................................................................7
4.1 Common Load Thresholds.............................................................................................................................................8
4.2 Admission Control..........................................................................................................................................................8
4.2.1 Admission Decision.....................................................................................................................................................9
4.2.2 Preemption.................................................................................................................................................................10
4.2.3 Queuing.....................................................................................................................................................................10
4.3 Congestion Control and Overload Control...................................................................................................................11
4.3.1 Congestion Detection................................................................................................................................................11
4.3.2 Overload Detection....................................................................................................................................................11
4.3.3 Congestion and Overload Handling..........................................................................................................................11
5 Engineering Guidelines.............................................................................................................13
6 Parameters.....................................................................................................................................14
7 Counters........................................................................................................................................20
8 Glossary.........................................................................................................................................21
9 Reference Documents.................................................................................................................22
Issue 01 (2012-04-30)

ii
SingleRAN
1 About This Document
About This Document
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 personnel who:
l
Need to understand the features described herein
Work with Huawei products

NOTE
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 WCDMA
RAN.
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l
Feature change
Changes in features of a specific product version
l
Issue 01 (2012-04-30)
Editorial change
SingleRAN
1 About This Document
Changes in wording or addition of information that was not described in the earlier version
01 (2012-04-30)
This document is created for SRAN7.0.
This document is split from the Transmission Resource Management Feature Parameter
Description of issue Draft A (2012-02-15) of SRAN7.0.
Issue 01 (2012-04-30)

SingleRAN
2 Overview
Overview
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 Multimode Base Station. Co-TRM
improves the usage of transmission resources and ensures the transmission quality of services
(QoS).
In the Co-TRM feature,
l
The GSM and UMTS services of the Multimode Base Station share one IP logical port (LP)
if the IP over FE/GE is adopted
The GSM and UMTS services of the Multimode Base Station 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:
l
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 Multimode Base Station in resource pool manner. The uniform management of the bandwidth
resources provides the following benefits:
Issue 01 (2012-04-30)

SingleRAN
2 Overview
In case of a burst of GSM and UMTS services on the Multimode Base Station, 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 Multimode Base
Station, 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:
l
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."
Issue 01 (2012-04-30)

SingleRAN
3 Transmission Resources
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
Issue 01 (2012-04-30)

SingleRAN
3 Transmission Resources
3.1 IP Physical Transmission Resources

The IP physical transmission resources are as follows:
l
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 Description of the WCDMA RAN and 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 GSM BSS.
Issue 01 (2012-04-30)

SingleRAN
4 Load Control
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.
Issue 01 (2012-04-30)

SingleRAN
4 Load 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.
l
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.
Issue 01 (2012-04-30)

SingleRAN
4 Load Control
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 2. For details about
admission decision, see section "4.2.1 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 3. For details about preemption, see section "4.2.2 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 4.2.3 Queuing.
4.2.1 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.
Issue 01 (2012-04-30)

SingleRAN
4 Load Control
4.2.2 Preemption
In the case of preemption, a high-priority user preempts the bandwidth from an admitted lowpriority 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:
l
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 highpriority 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 GSM BSS.
4.2.3 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:
l
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 GSM BSS.
Issue 01 (2012-04-30)

10
SingleRAN
4 Load Control
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:
l
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:
l
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:
l
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.
Issue 01 (2012-04-30)

11
SingleRAN
4 Load Control
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 GSM BSS.
Issue 01 (2012-04-30)

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

l
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 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:
l
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.
Issue 01 (2012-04-30)

13
SingleRAN
6 Parameters
Parameters
Table 6-1 Parameter description

Parameter ID
NE
MML
Command
Feature ID
Feature Name
Description
PreemptAlgoSwitch
BSC6910
SET
UQUEUEPREE
MPT
WRFD-010660
MBMS Phase 2
WRFD-010661
MBMS over Iur
WRFD-010662
Dynamic Power
Estimation for
MTCH
Meaning:Wheth
er preemption is
supported.
When this
switch is turned
on, 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 this
switch is turned
off, the RNC
terminates the
service for the
user due to the
failure in cell
resource
application.
WRFD-010663
WRFD-010665
WRFD-010505
WRFD-010660
04
WRFD-010616
06
WRFD-010660
02
WRFD-010660
03
WRFD-010660
01
MBMS Channel
Audience
Rating Statistics
Queuing and
Pre-Emption
Inter-Frequency
Neighboring
Cell Selection
for MBMS PTP
Users
WRFD-010616
01
Streaming
Service on
MBMS
WRFD-010616
03
MBMS P2P
over HSDPA
WRFD-010616
02
MBMS
Admission
Enhancement
WRFD-010616
05
WRFD-010616
04
Issue 01 (2012-04-30)
MSCH
Scheduling
MBMS
Enhanced
Broadcast Mode

GUI Value
Range:OFF, ON
Unit:None
14
SingleRAN
Parameter ID
NE
MML
Command
6 Parameters
Feature ID
Feature Name
Description
WRFD-010616
MBMS
Broadcast Mode
Actual Value
Range:OFF, ON
MBMS Load
Control
Default
Value:OFF
WRFD-010616
08
WRFD-010626
WRFD-010627
MBMS
Admission
Control
MBMS
Transport
Resource
Management
MBMS Soft/
Selective
Combining
MBMS
Introduction
Package
16/32/64/128Kb
ps Channel Rate
on MBMS
MBMS FLC
(Frequency
Layer
Convergence)/
FLD(Frequency
Layer
Dispersion)
FACH
Transmission
Sharing for
MBMS
Issue 01 (2012-04-30)

15
SingleRAN
6 Parameters
Parameter ID
NE
MML
Command
Feature ID
Feature Name
Description
PreemptAlgoSwitch
BSC6900
SET
UQUEUEPREE
MPT
WRFD-010660
MBMS Phase 2
WRFD-010661
MBMS over Iur
WRFD-010662
Dynamic Power
Estimation for
MTCH
Meaning:Wheth
er preemption is
supported.
When this
switch is turned
on, 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 this
switch is turned
off, the RNC
terminates the
service for the
user due to the
failure in cell
resource
application.
WRFD-010663
WRFD-010665
WRFD-010505
WRFD-010660
04
WRFD-010616
06
WRFD-010660
02
WRFD-010660
03
WRFD-010660
01
WRFD-010616
01
WRFD-010616
03
WRFD-010616
02
WRFD-010616
05
WRFD-010616
04
MSCH
Scheduling
MBMS Channel
Audience
Rating Statistics
Queuing and
Pre-Emption
Inter-Frequency
Neighboring
Cell Selection
for MBMS PTP
Users
Streaming
Service on
MBMS
MBMS P2P
over HSDPA
MBMS
Admission
Enhancement
GUI Value
Range:OFF, ON
WRFD-010616
MBMS
Enhanced
Broadcast Mode
WRFD-010616
08
MBMS
Broadcast Mode
Actual Value
Range:OFF, ON
WRFD-010626
MBMS Load
Control
Default
Value:OFF
WRFD-010627
Unit:None
MBMS
Admission
Control
MBMS
Transport
Resource
Management
MBMS Soft/
Selective
Combining
Issue 01 (2012-04-30)

16
SingleRAN
Parameter ID
NE
MML
Command
6 Parameters
Feature ID
Feature Name
Description
MBMS
Introduction
Package
16/32/64/128Kb
ps Channel Rate
on MBMS
MBMS FLC
(Frequency
Layer
Convergence)/
FLD(Frequency
Layer
Dispersion)
FACH
Transmission
Sharing for
MBMS
Issue 01 (2012-04-30)

17
SingleRAN
6 Parameters
Parameter ID
NE
MML
Command
Feature ID
Feature Name
Description
QueueAlgoSwit
ch
BSC6910
SET
UQUEUEPREE
MPT
WRFD-010505
Queuing and
Pre-Emption
Meaning:Wheth
er queuing is
supported.
When this
switch is turned
on and a
queuing-capable
PS user initiates
a call, the RNC
tries to enable
this user to join
the queue to
increase the
access success
rate if cell
resources are
insufficient and
preemption
fails. When this
switch is turned
off, queuing is
not supported if
cell resources
are insufficient.
GUI Value
Range:OFF, ON
Unit:None
Actual Value
Range:OFF, ON
Default
Value:OFF
Issue 01 (2012-04-30)

18
SingleRAN
6 Parameters
Parameter ID
NE
MML
Command
Feature ID
Feature Name
Description
QueueAlgoSwit
ch
BSC6900
SET
UQUEUEPREE
MPT
WRFD-010505
Queuing and
Pre-Emption
Meaning:Wheth
er queuing is
supported.
When this
switch is turned
on and a
queuing-capable
PS user initiates
a call, the RNC
tries to enable
this user to join
the queue to
increase the
access success
rate if cell
resources are
insufficient and
preemption
fails. When this
switch is turned
off, queuing is
not supported if
cell resources
are insufficient.
GUI Value
Range:OFF, ON
Unit:None
Actual Value
Range:OFF, ON
Default
Value:OFF
Issue 01 (2012-04-30)

19
SingleRAN
7 Counters
Counters
There are no specific counters associated with this feature.
Issue 01 (2012-04-30)

20
SingleRAN
8 Glossary
Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
Issue 01 (2012-04-30)

21
SingleRAN
9 Reference Documents
Reference Documents
1.
Transmission Resource Management Feature Parameter Description for WCDMA RAN

and GSM BSS
2.
Common Transmission Feature Parameter Description or SingleRAN
Issue 01 (2012-04-30)

22

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

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

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

Загружено:

Авторское право:

Доступные форматы

SingleRAN

Common Transmission Resource

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

1 About This Document

About This Document

1.2 Intended Audience

Need to understand the features described herein

Work with Huawei products

1.3 Change History

1 About This Document

Huawei Proprietary and Confidential

2.2 Networking Requirements

Huawei Proprietary and Confidential

2.4 Feature Contents

Transmission resources: In Co-TRM, the transmission resources, including IP LPs and IP

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

3.1 IP Physical Transmission Resources

FE/GE Ethernet port

Channelized STM-1/OC-3 port

In Co-TRM, IP LPs support five levels of aggregation.

3.3 IP Path Resources

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

4.1 Common Load Thresholds

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

Common congestion control thresholds

Common overload control thresholds

4.2 Admission Control

Huawei Proprietary and Confidential

The admission of transmission resources is decided. If the admission is successful, a user

4.2.1 Admission Decision

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

4.3 Congestion Control and Overload Control

Congestion and overload handling

4.3.1 Congestion Detection

4.3.2 Overload Detection

4.3.3 Congestion and Overload Handling

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

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

GSM+UMTS multi-mode base stations share IP LP/PPP/MLPPP transmission resources

If an LP is carried on an Ethernet port (ETHER), the bandwidth of the LP should be lower

Huawei Proprietary and Confidential

Table 6-1 Parameter description

MBMS over Iur

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

MBMS over Iur

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

Huawei Proprietary and Confidential

There are no specific counters associated with this feature.