TRM in the RAN Sharing Scenario(RAN14.0_01)

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

1/22

TRM in the RAN Sharing ScenarioRAN14.0

Feature Parameter Description

Issue 01

Date 2012-04-30

HUAWEI TECHNOLOGIES CO., LTD.

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

2/22

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 priorwritten 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 respectiveholders.

NoticeThe purchased products, services and features are stipulated by the contract made between Huawei andthe customer. All or part of the products, services and features described in this document may not bewithin 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 orrepresentations of any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations 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: [email protected]

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

3/22

WCDMA RANTRM in the RAN Sharing Scenario Contents

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright 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 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

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

4/22

WCDMA RANTRM in the RAN Sharing Scenario 1 Introduction

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

1-1

1 Introduction 1.1 Scope

This document describes policies for transmission resource management (TRM) over the Iub interface insituations 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 theRAN Sharing Feature Parameter Description . For details about TRM, see the Transmission Resource ManagementFeature 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 notdescribed 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.

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

5/22

WCDMA RANTRM in the RAN Sharing Scenario

2 Overview of Transmission Resource Managementfor RAN Sharing

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

2-1

2 Overview of Transmission Resource Management forRAN Sharing

When RAN sharing is implemented, operators that share the same base station can use transmissionresources over the Iub interface in a shared or exclusive way. These transmission resources can bemanaged on a centralized or individual basis. Centralized management improves bandwidth efficiencyand lowers costs for operators and individual management provides better QoS guarantees for eachoperator's users.

The Iub interface transmission resources that an operator can use exclusively vary by the transmissionmode, as shown in Table 2-1 .

Table 2-1 Iub interface transmission resources that an operator can use exclusively

Transmissionmode

Resources that an Operator Can Use Exclusively

IP transmission Physical resources (PPP links and MP groups), logical resources(IP logical ports), and path resources (IP paths)

TDMtransmission

physical resources (fractional IMA links, UNI links, IMA groups),logical resources (ATM logical ports), and path resources (ATMpaths)

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 onthe 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 betaken only from that operator's dedicated bandwidth. Accordingly, the RNC performs admission controlfor each operator in a individual manner. For details about admission control, see TransmissionResource Management Feature Parameter Description .

Centralized admission means that the transmission bandwidth requested by all operators' users istaken from the total bandwidth. Accordingly, the RNC performs admission control for all operators in acentralized manner.

Individual flow control means that the RNC performs individual congestion detection over eachoperator'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 bandwidthwithout distinguishing between operators. When detecting congestion, the RNC imposes flow controlon all operators' users.

Table 2-2 lists the TRM policy over the Iub interface in RAN Sharing mode. The policy is selectedthrough configuration.

Table 2-2 TRM policies for the Iub interface

BandwidthOccupationMode

TRM Policy

Individual admissionand centralized flowcontrol

Centralizedadmission andcentralized flowcontrol

Individual admissionand individual flowcontrol

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

6/22

WCDMA RANTRM in the RAN Sharing Scenario

2 Overview of Transmission Resource Managementfor RAN Sharing

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

2-2

BandwidthOccupationMode

TRM Policy

Individual admissionand centralized flowcontrol

Centralizedadmission andcentralized flowcontrol

Individual admissionand individual flowcontrol

Dedicatedbandwidths

-

Sharedbandwidths

- -

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 operatorseparately. This reduces the resource usage.

Individual admission and centralized flow control separately manage the Iub transmission bandwidthof each operator during UE admission. Compared with the policy of individual admission and individualflow control, this TRM policy has higher bandwidth utilization.

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

7/22

WCDMA RANTRM in the RAN Sharing Scenario 3 Individual Admission and Centralized Flow Control

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

3-1

3 Individual Admission and Centralized Flow Control This policy corresponds to the feature WRFD-02130501 Dedicated Iub Transmission Control. In thispolicy, 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 networkingis adopted for transmission, this policy is not supported if the links carried on E1/T1 links are PPP linksand 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 (PPPlink)/OPSEPFLAG (FRA link) /OPSEPFLAG (UNI link) /OPSEPFLAG (IMA group) parameter for the portsbe set to ON . As a result, each operator has a certain proportion of bandwidths and load thresholds onthe ports. The bandwidth allocation proportion and load thresholds for each operator are configured byusing the MML command ADD OPSEPINFO . The RNC has a list that specifies the default load thresholdfor 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 servingoperator'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' dedicatedbandwidth range over logical ports, the total bandwidth over logical ports, operators' dedicatedbandwidth range over physical ports, the total bandwidth over physical ports, and boards. If the requestis rejected, the user can only preempt transmission resources that are occupied by another user servedby 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 thefollowing 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 hasreached the congestion threshold for this operator, it regards this operator's admitted users as havingcaused congestion. This is known as OP Congestion.

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

8/22

WCDMA RANTRM in the RAN Sharing Scenario 3 Individual Admission and Centralized Flow Control

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

3-2

Monitors the usage of the total bandwidth.

When the RNC detects that the usage of the bandwidth occupied by all admitted users has reachedthe congestion threshold for this port, it regards all admitted users as having caused congestion. Thisis 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 LDR Objects

OP Congestion An operator's users

Port Congestion All users

OP Congestion and PortCongestion

LDR is first performed on an operator's users. If congestionpersists after the congestion caused by these users is lifted, LDRwill be performed on all users.

Overload occurs when the bandwidth occupied by admitted users over a port exceeds the sendingcapabilities of that port. The RNC checks the usage of the total bandwidth for the port. When thebandwidth 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 ParameterDescription .

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

9/22

WCDMA RANTRM in the RAN Sharing Scenario

4 Centralized Admission and Centralized FlowControl

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

4-1

4 Centralized Admission and Centralized Flow Control This policy corresponds to the feature WRFD-02130406 Transmission Resource Sharing on the Iub/IurInterface. The RscM n g M o d e 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 sharebandwidths over paths, logical ports, and physical ports. They also share load thresholds, such as thecongestion 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 sharebandwidths over logical ports.

Figure 4-1 shows how bandwidth is allocated in a situation where two operators (OPA and OPB) share aNodeB.

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 totalbandwidth over logical ports, physical ports, and boards.

The RNC centrally monitors the bandwidth usage over paths, logical ports, and physical ports. When theRNC detects that the bandwidth usage over a path, logical port, or physical port has reached thecongestion threshold for this path, logical port, or physical port, it performs LDR on all users. When theRNC detects that the bandwidth usage over a path, logical port, or physical port has reached theoverload threshold for this path, logical port, or physical port, it performs OLC on all users.

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

10/22

WCDMA RANTRM in the RAN Sharing Scenario 5 Individual Admission and Individual Flow Control

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

5-1

5 Individual Admission and Individual Flow Control This policy corresponds to the feature WRFD-021305 RAN Sharing Phase 2. In this policy, eachoperator individually manages its dedicated transmission resources over the Iub interface. The

RscM n g M o d e 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. Thisrequires that the RSCMNGMODE (ATM logical port) or RSCMNGMODE (IP logical port) parameter forlogical ports be set to EXCLUSIVE and each operator's dedicated path be carried on its dedicatedlogical port. As a result, each operator has dedicated load thresholds and dedicated bandwidths overpaths and logical ports.

Figure 5-1 shows how bandwidth is allocated in a situation where two operators (OPA and OPB) share aNodeB.

Figure 5-1 Allocating bandwidth

In cases where admission decision is made on each operator' dedicated bandwidth, when a userrequests transmission resources, admission decision is made successively on paths (based onoperators' dedicated bandwidths), logical ports (based on operators' dedicated bandwidths), physicalports, and boards. If the request is rejected, the user can only preempt transmission resources that areoccupied 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. Whenthe RNC detects that the bandwidth occupied by an operator's admitted users has reached thecongestion threshold for this path or logical port, it performs LDR on this operator's users. When theRNC detects that the bandwidth occupied by an operator's admitted users has reached the overloadthreshold 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 acertain resource item reaches the corresponding load threshold, load control (LDR or OLC) is triggered on the resourceitem.

Assume that the LDR trigger threshold for a physical port is 8 Mbit/s, the physical port carries two logical ports (LP1 andLP2), 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 LDRon 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 physicalport is 6 Mbit/s, which does not reach the LDR trigger threshold of the physical port. Therefore, the RNC does not triggerLDR on the physical port.

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

11/22

WCDMA RANTRM in the RAN Sharing Scenario 6 Engineering Guidelines

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

6-1

6 Engineering Guidelines 6.1 Overview

This chapter provides engineering guidelines for TRM when RAN sharing is used in differenttransmission scenarios. When ATM/IP transmission is used, transmission networks are classified intoconvergence 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 nodesexist in the transmission network. In a non-convergence network, the bandwidth is the same for the RNCand the NodeB, and no congestion node exists in the transmission network. For details abouttransmission convergence, see the Transmission Resource Management Feature ParameterDescription .

6.2 Non-Convergence Transmission Network Over the IubInterface

6.2.1 Dedicated Bandwidths

Overview

As shown in Figure 6-1 , two operators share a RAN and have dedicated transmission bandwidths overthe Iub interface.

Figure 6-1 Shared RAN and dedicated transmission bandwidths over the Iub interface

Configuring Individual Admission and Centralized Flow Control

When individual admission and centralized flow control are implemented, each operator has dedicatedbandwidths on PPP and MLPPP links if the Iub interface uses IP transmission. When individual

BW: Bandwidth BS: Base station

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

12/22

WCDMA RANTRM in the RAN Sharing Scenario 6 Engineering Guidelines

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

6-2

admission and centralized flow control are implemented, each operator has a certain proportion ofbandwidths 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, setparameters as follows:

On the RNC side, set the RscM n g M o d e parameter to EXCLUSIVE when running the MML commandADD UNODEB .

On PPP links, MLPPP links, fractional IMA links, UNI links, and IMA links, perform the following stepsto allocate a certain proportion of bandwidths to operators and configure dedicated load thresholdtables for these operators:

1. Run the MML command ADD TRMLOADTH to configure TRM load threshold tables for operatorsand 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 thresholdtables 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 (IMAgroup) parameter to ON , set the OPSEPINDEX (PPP link) /OPSEPINDEX (FRAlink)/OPSEPINDEX (UNI link) /OPSEPINDEX (IMA group) parameter to the index of the informationtable 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 logicalports, set parameters as follows:

When running the MML command ADD UNODEB , set the RscM n g M o d e parameter to EXCLUSIVE . Perform the following steps to configure dedicated logical ports for operators and to configurededicated 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 foroperators' dedicated logical ports and paths.

2. When running the MML command ADD ATMLOGICPORT or ADD IPLOGICPORT , set theRSCMNGMODE ( ATM logical port) /RSCMNGMODE (IP logical port) parameter to EXCLUSIVE andspecify 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 running the MML command ADD IPPATH , set the CARRYFLAG parameter to IPLGCPORT and specify TRM load threshold tables for IP paths.

When running the MML command ADD AAL2PATH , set the CARRYT parameter toATMLOGICPORT and specify TRM load threshold tables for AAL2 paths.

(Optional) Perform the following steps to configure dedicated TRM mappings and TRM factor tablesfor 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.

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

13/22

WCDMA RANTRM in the RAN Sharing Scenario 6 Engineering Guidelines

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

6-3

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

In this policy, operators share paths and physical resources.

To achieve centralized resource management over the Iub interface, set parameters as follows: on theRNC side, set the RscM n g M o d e parameter to SHARE when running the MML command ADDUNODEB .

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 overlogical ports for the congestion node.

BW: Bandwidth BS: Base station

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

14/22

WCDMA RANTRM in the RAN Sharing Scenario 6 Engineering Guidelines

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

6-4

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, setparameters as follows:

On the RNC side, set the RscM n g M o d e 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 operatorsand configure dedicated load threshold tables for these operators:

1. Run the MML command ADD TRMLOADTH to configure TRM load threshold tables for operatorsand 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 thresholdtables for each operator.

When running the MML command ADD IPLOGICPORT , set the RSCMNGMODE parameter toSHARE , set the OPSEPFLAG parameter to ON , set the OPSEPINDEX parameter to the index of theinformation 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.

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

15/22

WCDMA RANTRM in the RAN Sharing Scenario 6 Engineering Guidelines

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

6-5

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 RscM n g M o d e parameter to SHARE when running the MML command ADDUNODEB .

Set the RSCMNGMODE ( ATM logical port) /RSCMNGMODE (IP logical port) parameter to SHARE when running the MML command ADD ATMLOGICPORT or ADD IPLOGICPORT .

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

16/22

WCDMA RANTRM in the RAN Sharing Scenario 7 Parameters

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

7-1

7 ParametersTable 7-1 Parameter description

Parameter ID NE MML Command Description

CARRYFLAG BSC6900 ADD IPPATH

MOD IPPATH

Meaning:Carry Flag of IP path

IPLGCPORT: indicates that the IP Path is carried on theIP logic port;

RSCGRP: indicates that the IP Path is carried on theresource group;

NULL: indicates that the IP Path is carried on thephysics port.

GUI Value Range:NULL(NULL), IPLGCPORT(IP LogicPort), RSCGRP(Resource Group)

Actual Value Range:NULL, IPLGCPORT, RSCGRP

Unit:None

Default Value:NULL(NULL)

CARRYT BSC6900 ADD AAL2PATH

MOD AAL2PATH

Meaning:Lower layer link type of bearing the Path.

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

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

17/22

WCDMA RANTRM in the RAN Sharing Scenario 7 Parameters

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

7-2

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

Meaning:Operator Separated Flag.

GUI Value Range:OFF(OFF), ON(ON)

Actual Value Range:OFF, ON

Unit:None

Default Value:OFF(OFF)

OPSEPFLAG BSC6900 ADDIPLOGICPORT

MODIPLOGICPORT

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 UNILNK

MOD UNILNK

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 FRALNK

MOD FRALNK

Meaning:Operator Separated Flag.

GUI Value Range:OFF(OFF), ON(ON)

Actual Value Range:OFF, ON

Unit:None

Default Value:OFF(OFF)

OPSEPINDEX BSC6900 ADD UNILNK

MOD UNILNK

Meaning:Operator Separated Index. The value can bequeried by the "LST OPSEPINFO" command.

GUI Value Range:0~199

Actual Value Range:0~199

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

18/22

WCDMA RANTRM in the RAN Sharing Scenario 7 Parameters

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

7-3

Parameter ID NE MML Command Description

Unit:None

Default Value:None

OPSEPINDEX BSC6900 ADD IMAGRP

MOD IMAGRP

Meaning:Operator Separated Index. The value can bequeried by the "LST OPSEPINFO" command.

GUI Value Range:0~199

Actual Value Range:0~199

Unit:None

Default Value:None

OPSEPINDEX BSC6900 ADD

IPLOGICPORT MODIPLOGICPORT

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 PPPLNK

MOD PPPLNK

Meaning:Operator Separated Index. The value can bequeried by the "LST OPSEPINFO" command.

GUI Value Range:0~199

Actual Value Range:0~199

Unit:None

Default Value:None

OPSEPINDEX BSC6900 ADD FRALNK

MOD FRALNK

Meaning:Operator Separated Index. The value can bequeried by the "LST OPSEPINFO" command.

GUI Value Range:0~199

Actual Value Range:0~199

Unit:None

Default Value:None

RSCMNGMODE BSC6900 ADDIPLOGICPORT

Meaning:Resource management mode. The logical portworking in the SHARE mode can be shared by multiplecarriers. The logical port working in the EXCLUSIVEmode can be used by only one carrier.

GUI Value Range:SHARE, EXCLUSIVE

Actual Value Range:SHARE, EXCLUSIVE

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

19/22

WCDMA RANTRM in the RAN Sharing Scenario 7 Parameters

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

7-4

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

ATMLOGICPORT

Meaning:Resource management mode of logical port

GUI Value Range:SHARE, EXCLUSIVE

Actual Value Range:SHARE, EXCLUSIVE

Unit:None

Default Value:None

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

20/22

WCDMA RANTRM in the RAN Sharing Scenario 8 Counters

Issue 01 (2012-04-30) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd

8-1

8 CountersThere are no specific counters associated with this feature.

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

21/22

8/13/2019 TRM in the RAN Sharing Scenario(RAN14.0_01)

22/22

WCDMA RANTRM in the RAN Sharing Scenario 10 Reference Documents

Issue 01 (2012-04-30) Huawei Proprietary and Confidential 10-1

10 Reference Documents[1] WCDMA RAN RAN Sharing Feature Parameter Description

[2] Transmission Resource Management Feature Parameter Description