TRM in The RAN Sharing Scenario (RAN14.0 - 01)

TRM in the RAN Sharing Scenario RAN14.
Feature Parameter Description
Issue Date
01 2012-04-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: Email: http://www.huawei.com support@huawei.com
WCDMA RAN TRM in the RAN Sharing Scenario
Contents
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 Transmission Resource Management for RAN Sharing.........................2-1 3 Individual Admission and Centralized Flow Control .......................................................3-1 4 Centralized Admission and Centralized Flow Control ....................................................4-1 5 Individual Admission and Individual Flow Control ..........................................................5-1 6 Engineering Guidelines...........................................................................................................6-1
6.1 Overview ....................................................................................................................................... 6-1 6.2 Non-Convergence Transmission Network Over the Iub Interface ................................................ 6-1 6.2.1 Dedicated Bandwidths .......................................................................................................... 6-1 6.2.2 Shared Bandwidth ................................................................................................................ 6-3 6.3 Convergence Transmission Network Over the Iub Interface ........................................................ 6-3 6.3.1 Dedicated Bandwidths .......................................................................................................... 6-3 6.3.2 Shared Bandwidth ................................................................................................................ 6-4
7 Parameters .................................................................................................................................7-1 8 Counters ......................................................................................................................................8-1 9 Glossary ......................................................................................................................................9-1 10 Reference Documents .........................................................................................................10-1
Issue 01 (2012-04-30)
Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd
1 Introduction
1 Introduction
1.1 Scope
This document describes policies for transmission resource management (TRM) over the Iub interface in situations where operators share a radio access network (RAN).
Familiarize yourself with RAN sharing and TRM before reading this document. For details about RAN sharing, see the RAN Sharing Feature Parameter Description. For details about TRM, see the Transmission Resource Management Feature Parameter Description.
1.2 Intended Audience

This document is intended for:

Personnel who understand WCDMA basics Personnel who need to learn about TRM in the RAN sharing scenario Personnel who work with Huawei products
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 TRM in the RAN sharing scenario. 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 issue is as follows:

01 (2012-04-30) Draft A (2012-02-15)
01 (2012-04-30)
This is the document for the first commercial release of RAN14.0. Compared with issue Draft A (2012-02-15) of RAN14.0, this issue has no change.
Draft A (2012-02-15)
This is the first draft of the document for RAN14.0. This document is split from the TRM in the RAN Sharing Scenario of issue 01 (2011-03-30) of SRAN6.0.
Issue 01 (2012-04-30)
1-1
2 Overview of Transmission Resource Management for RAN Sharing

When RAN sharing is implemented, operators that share the same base station can use transmission resources over the Iub interface in a shared or exclusive way. These transmission resources can be managed on a centralized or individual basis. Centralized management improves bandwidth efficiency and lowers costs for operators and individual management provides better QoS guarantees for each operator's users. The Iub interface transmission resources that an operator can use exclusively vary by the transmission mode, as shown in Table 2-1. Table 2-1 Iub interface transmission resources that an operator can use exclusively Transmission mode IP transmission TDM transmission
Resources that an Operator Can Use Exclusively
Physical resources (PPP links and MP groups), logical resources (IP logical ports), and path resources (IP paths) physical resources (fractional IMA links, UNI links, IMA groups), logical resources (ATM logical ports), and path resources (ATM paths)
The NCP, CCPs, and ALCAP links between the RNC and the NodeB are shared among all operators.
TRM policies for the Iub interface involve admission control on the control plane and flow control on the user plane. In RAN sharing mode, operators support individual admission, centralized admission, individual flow control, and centralized flow control. Individual admission means that the transmission bandwidth requested by an operator's users can be taken only from that operator's dedicated bandwidth. Accordingly, the RNC performs admission control for each operator in a individual manner. For details about admission control, see Transmission Resource Management Feature Parameter Description. Centralized admission means that the transmission bandwidth requested by all operators' users is taken from the total bandwidth. Accordingly, the RNC performs admission control for all operators in a centralized manner. Individual flow control means that the RNC performs individual congestion detection over each operator's dedicated bandwidth. When detecting congestion over an operator's dedicated bandwidth, the RNC imposes flow control only on that operator's users. Centralized flow control means that the RNC performs congestion detection over the total bandwidth without distinguishing between operators. When detecting congestion, the RNC imposes flow control on all operators' users.
Table 2-2 lists the TRM policy over the Iub interface in RAN Sharing mode. The policy is selected through configuration. Table 2-2 TRM policies for the Iub interface Bandwidth Occupation Mode TRM Policy Individual admission and centralized flow control Centralized admission and centralized flow control Individual admission and individual flow control
Issue 01 (2012-04-30)
2-1
Bandwidth Occupation Mode
TRM Policy Individual admission and centralized flow control Centralized admission and centralized flow control Individual admission and individual flow control -
Dedicated bandwidths Shared bandwidths

Remarks

- not involved
The characteristics of the three TRM policies listed in Table 2-2 are as follows:

Centralized admission and centralized flow control maximize the usage of Iub transmission bandwidth. This TRM policy is recommended in RAN sharing scenarios. Individual admission and individual flow control manage the transmission bandwidth of each operator separately. This reduces the resource usage. Individual admission and centralized flow control separately manage the Iub transmission bandwidth of each operator during UE admission. Compared with the policy of individual admission and individual flow control, this TRM policy has higher bandwidth utilization.
Issue 01 (2012-04-30)
2-2
3 Individual Admission and Centralized Flow Control

This policy corresponds to the feature WRFD-02130501 Dedicated Iub Transmission Control. In this policy, admission decision is made on an operator's users over this operator's bandwidth range, and flow control is performed on all users over the total bandwidth. In situations where IP over E1/T1 networking is adopted for transmission, this policy is not supported if the links carried on E1/T1 links are PPP links and port load sharing is enabled for PPP links. Admission decision is individually made on each operator's users over logical ports and physical ports (referred to collectively as ports). This requires that the OPSEPFLAG(IP logical port)/OPSEPFLAG(PPP link)/OPSEPFLAG(FRA link)/OPSEPFLAG(UNI link)/OPSEPFLAG(IMA group) parameter for the ports be set to ON. As a result, each operator has a certain proportion of bandwidths and load thresholds on the ports. The bandwidth allocation proportion and load thresholds for each operator are configured by using the MML command ADD OPSEPINFO. The RNC has a list that specifies the default load threshold for each port and operator. You can run the MML command ADD TRMLOADTH to add a new list. Figure 3-1 shows an example of bandwidth allocation in a port for two operators. Figure 3-1 Bandwidth allocation in a port for two operators
When a user requests transmission resources, admission decision is first made over the serving operator's dedicated bandwidth range. If the request is admitted, admission decision is then made over the total bandwidth. Specifically, admission decision is made successively on paths, operators' dedicated bandwidth range over logical ports, the total bandwidth over logical ports, operators' dedicated bandwidth range over physical ports, the total bandwidth over physical ports, and boards. If the request is rejected, the user can only preempt transmission resources that are occupied by another user served by the same operator. When the bandwidth occupied by admitted users reaches the congestion threshold, load reshuffling (LDR) is triggered to avoid congestion. The RNC performs congestion detection on each port in the following ways:
Monitors the usage of operators' dedicated bandwidth range. When the RNC detects that the usage of the bandwidth occupied by an operator's admitted users has reached the congestion threshold for this operator, it regards this operator's admitted users as having caused congestion. This is known as OP Congestion.
Issue 01 (2012-04-30)
3-1
Monitors the usage of the total bandwidth. When the RNC detects that the usage of the bandwidth occupied by all admitted users has reached the congestion threshold for this port, it regards all admitted users as having caused congestion. This is known as Port Congestion.
As described in Table 3-1, LDR is performed on different objects, depending on the congestion state. Table 3-1 LDR objects Congestion State OP Congestion Port Congestion OP Congestion and Port Congestion LDR Objects An operator's users All users LDR is first performed on an operator's users. If congestion persists after the congestion caused by these users is lifted, LDR will be performed on all users.
Overload occurs when the bandwidth occupied by admitted users over a port exceeds the sending capabilities of that port. The RNC checks the usage of the total bandwidth for the port. When the bandwidth usage reaches the overload threshold for the port, the RNC performs overload control (OLC) on all users to quickly lift overload. For details about LDR and OLC, see the Transmission Resource Management Feature Parameter Description.
Issue 01 (2012-04-30)
3-2
4 Centralized Admission and Centralized Flow Control
4 Centralized Admission and Centralized Flow Control

This policy corresponds to the feature WRFD-02130406 Transmission Resource Sharing on the Iub/Iur Interface. The RscMngMode parameter for the Iub interface needs to be set to SHARE. Admission decision is made on all users over paths, logical ports, and physical ports. All operators share bandwidths over paths, logical ports, and physical ports. They also share load thresholds, such as the congestion threshold and overload threshold. This requires that the RSCMNGMODE (ATM logical port) or RSCMNGMODE (IP logical port) parameter for logical ports be set to SHARE for operators to share bandwidths over logical ports. Figure 4-1 shows how bandwidth is allocated in a situation where two operators (OPA and OPB) share a NodeB. Figure 4-1 Bandwidth sharing
When a user requests transmission resources, admission decision is made over the total bandwidth. Specifically, admission decision is made successively on the total bandwidth over paths, the total bandwidth over logical ports, physical ports, and boards. The RNC centrally monitors the bandwidth usage over paths, logical ports, and physical ports. When the RNC detects that the bandwidth usage over a path, logical port, or physical port has reached the congestion threshold for this path, logical port, or physical port, it performs LDR on all users. When the RNC detects that the bandwidth usage over a path, logical port, or physical port has reached the overload threshold for this path, logical port, or physical port, it performs OLC on all users.
Issue 01 (2012-04-30)
4-1
5 Individual Admission and Individual Flow Control
5 Individual Admission and Individual Flow Control

This policy corresponds to the feature WRFD-021305 RAN Sharing Phase 2. In this policy, each operator individually manages its dedicated transmission resources over the Iub interface. The RscMngMode parameter for the Iub interface needs to be set to EXCLUSIVE. Admission decision is individually made on each operator's users over paths and logical ports. This requires that the RSCMNGMODE (ATM logical port) or RSCMNGMODE (IP logical port) parameter for logical ports be set to EXCLUSIVE and each operator's dedicated path be carried on its dedicated logical port. As a result, each operator has dedicated load thresholds and dedicated bandwidths over paths and logical ports. Figure 5-1 shows how bandwidth is allocated in a situation where two operators (OPA and OPB) share a NodeB. Figure 5-1 Allocating bandwidth
In cases where admission decision is made on each operator' dedicated bandwidth, when a user requests transmission resources, admission decision is made successively on paths (based on operators' dedicated bandwidths), logical ports (based on operators' dedicated bandwidths), physical ports, and boards. If the request is rejected, the user can only preempt transmission resources that are occupied by another user with low service priority served by the same operator. The RNC monitors the bandwidth usage over each operator's dedicated paths and logical ports. When the RNC detects that the bandwidth occupied by an operator's admitted users has reached the congestion threshold for this path or logical port, it performs LDR on this operator's users. When the RNC detects that the bandwidth occupied by an operator's admitted users has reached the overload threshold for this path or logical port, it performs OLC on this operator's users.
Load thresholds can be configured on physical ports, logical ports, and paths. When the RNC detects that the load of a certain resource item reaches the corresponding load threshold, load control (LDR or OLC) is triggered on the resource item. Assume that the LDR trigger threshold for a physical port is 8 Mbit/s, the physical port carries two logical ports (LP1 and LP2), and the LDR trigger threshold of both LP1 and LP2 is 4 Mbit/s. If the load on LP1 is 4 Mbit/s, the RNC triggers LDR on LP1. In this case, if the load on LP2 is 2 Mbit/s, the RNC does not trigger LDR on LP2. The total load on the physical port is 6 Mbit/s, which does not reach the LDR trigger threshold of the physical port. Therefore, the RNC does not trigger LDR on the physical port.
Issue 01 (2012-04-30)
5-1
6 Engineering Guidelines
6.1 Overview
This chapter provides engineering guidelines for TRM when RAN sharing is used in different transmission scenarios. When ATM/IP transmission is used, transmission networks are classified into convergence and non-convergence transmission networks. Operators can use Iub interface bandwidths in a shared or dedicated manner. In a convergence network, the bandwidth is different for the RNC and the NodeB, and congestion nodes exist in the transmission network. In a non-convergence network, the bandwidth is the same for the RNC and the NodeB, and no congestion node exists in the transmission network. For details about transmission convergence, see the Transmission Resource Management Feature Parameter Description.
6.2 Non-Convergence Transmission Network Over the Iub Interface

6.2.1 Dedicated Bandwidths
Overview
As shown in Figure 6-1, two operators share a RAN and have dedicated transmission bandwidths over the Iub interface. Figure 6-1 Shared RAN and dedicated transmission bandwidths over the Iub interface
BW: Bandwidth
BS: Base station
Configuring Individual Admission and Centralized Flow Control

When individual admission and centralized flow control are implemented, each operator has dedicated bandwidths on PPP and MLPPP links if the Iub interface uses IP transmission. When individual
Issue 01 (2012-04-30) Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd 6-1
admission and centralized flow control are implemented, each operator has a certain proportion of bandwidths on fractional IMA links, UNI links, and IMA links if the Iub interface uses ATM transmission. To enable operators to manage their respective dedicated transmission-resources on the links, set parameters as follows:

On the RNC side, set the RscMngMode parameter to EXCLUSIVE when running the MML command ADD UNODEB. On PPP links, MLPPP links, fractional IMA links, UNI links, and IMA links, perform the following steps to allocate a certain proportion of bandwidths to operators and configure dedicated load threshold tables for these operators:
1. Run the MML command ADD TRMLOADTH to configure TRM load threshold tables for operators and links. 2. Run the MML command ADD OPSEPINFO and add an information table for individual admission. This is to allocate a certain proportion of bandwidths to operators and specify TRM load threshold tables for each operator.
When running the MML commands ADD PPPLNK, ADD FRALNK, ADD UNILNK, and ADD IMAGRP, set the OPSEPFLAG(PPP link)/OPSEPFLAG(FRA link)/OPSEPFLAG(UNI link)/OPSEPFLAG(IMA group) parameter to ON, set the OPSEPINDEX(PPP link)/OPSEPINDEX(FRA link)/OPSEPINDEX(UNI link)/OPSEPINDEX(IMA group) parameter to the index of the information table added in step 2 and specify TRM load threshold tables for links.
Configuring Individual Admission and Individual Flow Control

In this policy, operators use dedicated bandwidths over paths and logical ports. To enable operators to manage their respective dedicated transmission-resources over paths and logical ports, set parameters as follows:

When running the MML command ADD UNODEB, set the RscMngMode parameter to EXCLUSIVE. Perform the following steps to configure dedicated logical ports for operators and to configure dedicated TRM load threshold tables for operators' dedicated logical ports and paths.
1. Run the MML command ADD TRMLOADTH to configure dedicated TRM load threshold tables for operators' dedicated logical ports and paths. 2. When running the MML command ADD ATMLOGICPORT or ADD IPLOGICPORT, set the RSCMNGMODE(ATM logical port)/RSCMNGMODE(IP logical port) parameter to EXCLUSIVE and specify TRM load threshold tables for logical ports. 3. When configuring paths, perform the following steps to ensure that paths are carried over operators' dedicated logical ports:
When When
running the MML command ADD IPPATH, set the CARRYFLAG parameter to IPLGCPORT and specify TRM load threshold tables for IP paths. running the MML command ADD AAL2PATH, set the CARRYT parameter to ATMLOGICPORT and specify TRM load threshold tables for AAL2 paths.
(Optional) Perform the following steps to configure dedicated TRM mappings and TRM factor tables for operators:
1. Run the MML command ADD TRMMAP to configure a dedicated TRM mapping for each operator. 2. Run the MML command ADD TRMFACTOR to configure dedicated TRM factors for each operator. 3. Run the MML command ADD ADJMAP to set the CNMNGMODE parameter to EXCLUSIVE and specify the dedicated TRM mapping and TRM factor table for each operator.
Issue 01 (2012-04-30)
6-2
6.2.2 Shared Bandwidth

As shown in Figure 6-2, two operators share a RAN and transmission bandwidths over the Iub interface. Figure 6-2 Shared RAN and shared transmission bandwidths over the Iub interface
BW: Bandwidth
BS: Base station
In this policy, operators share paths and physical resources. To achieve centralized resource management over the Iub interface, set parameters as follows: on the RNC side, set the RscMngMode parameter to SHARE when running the MML command ADD UNODEB.
6.3 Convergence Transmission Network Over the Iub Interface

6.3.1 Dedicated Bandwidths
Overview
As shown in Figure 6-3, two operators share a RAN and have dedicated transmission bandwidths over logical ports for the congestion node.
Issue 01 (2012-04-30)
6-3
Figure 6-3 Shared RAN and dedicated transmission bandwidths over logical ports for the congestion node
BW: Bandwidth
BS: Base station
Configuring Individual Admission and Centralized Flow Control

To enable operators to manage their respective dedicated transmission-resources over logical ports, set parameters as follows:

On the RNC side, set the RscMngMode parameter to EXCLUSIVE when running the MML command ADD UNODEB. On logical ports, perform the following steps to allocate a certain proportion of bandwidths to operators and configure dedicated load threshold tables for these operators:
1. Run the MML command ADD TRMLOADTH to configure TRM load threshold tables for operators and logical ports. 2. Run the MML command ADD OPSEPINFO and add an information table for individual admission. This is to allocate a certain proportion of bandwidths to operators and specify TRM load threshold tables for each operator.
When running the MML command ADD IPLOGICPORT, set the RSCMNGMODE parameter to SHARE, set the OPSEPFLAG parameter to ON, set the OPSEPINDEX parameter to the index of the information table added in step 2, and specify TRM load threshold tables for logical ports.
Configuring Individual Admission and Individual Flow Control

See "Configuring Individual Admission and Individual Flow Control" in section 6.1.1.
6.3.2 Shared Bandwidth

As shown in Figure 6-4, two operators share a RAN and transmission bandwidths over the Iub interface.
Issue 01 (2012-04-30)
6-4
Figure 6-4 Shared RAN and shared transmission bandwidths over the Iub interface
BW: Bandwidth
BS: Base station
To achieve centralized resource management over the Iub interface, set parameters as follows:

On the RNC side, set the RscMngMode parameter to SHARE when running the MML command ADD UNODEB. Set the RSCMNGMODE(ATM logical port)/RSCMNGMODE(IP logical port) parameter to SHARE when running the MML command ADD ATMLOGICPORT or ADD IPLOGICPORT.
Issue 01 (2012-04-30)
6-5
7 Parameters
7 Parameters
Table 7-1 Parameter description Parameter ID CARRYFLAG NE BSC6900 MML Command Description ADD IPPATH MOD IPPATH Meaning:Carry Flag of IP path IPLGCPORT: indicates that the IP Path is carried on the IP logic port; RSCGRP: indicates that the IP Path is carried on the resource group; NULL: indicates that the IP Path is carried on the physics port. GUI Value Range:NULL(NULL), IPLGCPORT(IP Logic Port), RSCGRP(Resource Group) Actual Value Range:NULL, IPLGCPORT, RSCGRP Unit:None Default Value:NULL(NULL) CARRYT BSC6900 ADD AAL2PATH Meaning:Lower layer link type of bearing the Path. MOD AAL2PATH UNI: see"ADD UNILNK"; IMA: see"ADD IMALNK"; FRAATM: see"ADD FRALNK"; NCOPT: see"LST OPT"; ATMLOGICPORT: see"ADD ATMLOGICPORT"; NULL: used when testing. GUI Value Range:UNI(UNI Link), IMA(IMA Group), FRAATM(FRAATM Link), NCOPT(Optical Port), ATMLOGICPORT(ATM Logical Port), NULL(NULL) Actual Value Range:UNI, IMA, FRAATM, NCOPT, ATMLOGICPORT, NULL Unit:None Default Value:None CNMNGMODE BSC6900 ADD ADJMAP MOD ADJMAP RMV ADJMAP Meaning:Resource management mode. GUI Value Range:SHARE(SHARE), EXCLUSIVE(EXCLUSIVE) Actual Value Range:SHARE, EXCLUSIVE Unit:None
Issue 01 (2012-04-30)
7-1
7 Parameters
Parameter ID
NE
MML Command Description Default Value:None
OPSEPFLAG
BSC6900
ADD IMAGRP MOD IMAGRP
Meaning:Operator Separated Flag. GUI Value Range:OFF(OFF), ON(ON) Actual Value Range:OFF, ON Unit:None Default Value:OFF(OFF)
OPSEPFLAG
BSC6900
ADD PPPLNK MOD PPPLNK
OPSEPFLAG
BSC6900
ADD IPLOGICPORT MOD IPLOGICPORT
OPSEPFLAG
BSC6900
ADD UNILNK MOD UNILNK
OPSEPFLAG
BSC6900
ADD FRALNK MOD FRALNK
OPSEPINDEX
BSC6900
ADD UNILNK MOD UNILNK
Meaning:Operator Separated Index. The value can be queried by the "LST OPSEPINFO" command. GUI Value Range:0~199 Actual Value Range:0~199
Issue 01 (2012-04-30)
7-2
7 Parameters
Parameter ID
NE
MML Command Description Unit:None Default Value:None
OPSEPINDEX
BSC6900
ADD IMAGRP MOD IMAGRP
Meaning:Operator Separated Index. The value can be queried by the "LST OPSEPINFO" command. GUI Value Range:0~199 Actual Value Range:0~199 Unit:None Default Value:None
OPSEPINDEX
BSC6900
ADD IPLOGICPORT MOD IPLOGICPORT
OPSEPINDEX
BSC6900
ADD PPPLNK MOD PPPLNK
OPSEPINDEX
BSC6900
ADD FRALNK MOD FRALNK
RSCMNGMODE BSC6900
ADD IPLOGICPORT
Meaning:Resource management mode. The logical port working in the SHARE mode can be shared by multiple carriers. The logical port working in the EXCLUSIVE mode can be used by only one carrier. GUI Value Range:SHARE, EXCLUSIVE Actual Value Range:SHARE, EXCLUSIVE
Issue 01 (2012-04-30)
7-3
7 Parameters
Parameter ID
NE
MML Command Description Unit:None Default Value:None
RscMngMode
BSC6900
ADD UNODEB MOD UNODEB
Meaning:Indicating the resource management mode GUI Value Range:SHARE(Share), EXCLUSIVE(Exclusive) Actual Value Range:SHARE, EXCLUSIVE Unit:None Default Value:SHARE(Share)
RSCMNGMODE BSC6900
ADD Meaning:Resource management mode of logical port ATMLOGICPORT GUI Value Range:SHARE, EXCLUSIVE Actual Value Range:SHARE, EXCLUSIVE Unit:None Default Value:None
Issue 01 (2012-04-30)
7-4
8 Counters
8 Counters
There are no specific counters associated with this feature.
Issue 01 (2012-04-30)
8-1
9 Glossary
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
Issue 01 (2012-04-30)
9-1
10 Reference Documents
10 Reference Documents
[1] WCDMA RAN RAN Sharing Feature Parameter Description [2] Transmission Resource Management Feature Parameter Description
Issue 01 (2012-04-30)
10-1

TRM in The RAN Sharing Scenario (RAN14.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

TRM in The RAN Sharing Scenario (RAN14.0 - 01)

Enviado por

Direitos autorais:

Formatos disponíveis

TRM in the RAN Sharing Scenario RAN14.

Feature Parameter Description

HUAWEI TECHNOLOGIES CO., LTD.

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

Trademarks and Permissions

Huawei Technologies Co., Ltd.

WCDMA RAN TRM in the RAN Sharing Scenario

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

1.2 Intended Audience

1.3 Change History

01 (2012-04-30) Draft A (2012-02-15)

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

2 Overview of Transmission Resource Management for RAN Sharing

2 Overview of Transmission Resource Management for RAN Sharing

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

2 Overview of Transmission Resource Management for RAN Sharing

Bandwidth Occupation Mode

Dedicated bandwidths Shared bandwidths

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

3 Individual Admission and Centralized Flow Control

3 Individual Admission and Centralized Flow Control

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

3 Individual Admission and Centralized Flow Control

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

4 Centralized Admission and Centralized Flow Control

4 Centralized Admission and Centralized Flow Control

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

5 Individual Admission and Individual Flow Control

5 Individual Admission and Individual Flow Control

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

6.2 Non-Convergence Transmission Network Over the Iub Interface

BS: Base station

Configuring Individual Admission and Centralized Flow Control

WCDMA RAN TRM in the RAN Sharing Scenario

Configuring Individual Admission and Individual Flow Control

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

6.2.2 Shared Bandwidth

BS: Base station

6.3 Convergence Transmission Network Over the Iub Interface

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

BS: Base station

Configuring Individual Admission and Centralized Flow Control

Configuring Individual Admission and Individual Flow Control

6.3.2 Shared Bandwidth

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

BS: Base station

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

Huawei Proprietary and Confidential Copyright Huawei Technologies Co., Ltd

WCDMA RAN TRM in the RAN Sharing Scenario

MML Command Description Default Value:None

ADD IMAGRP MOD IMAGRP