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

TRM in the RAN Sharing Scenario GBSS14.0

Feature Parameter Description

Issue

01

Date

2012-04-28

HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2012. All rights reserved. No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders.

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

Huawei Technologies Co., Ltd. Address:

Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of China

Website:

http://www.huawei.com

Email:

[email protected]

GSM BSS 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 Non-Convergence Transmission Network Over the Iub and Abis Interfaces ................................ 6-1 6.1.1 Dedicated Bandwidths .......................................................................................................... 6-1 6.1.2 Shared Bandwidth ................................................................................................................ 6-3 6.2 Convergence Transmission Network Over the Iub and Abis Interf aces........................................ 6-4 6.2.1 Dedicated Bandwidths .......................................................................................................... 6-4 6.2.2 Shared Bandwidth ................................................................................................................ 6-5

7 Parameters..................................................................................................................................7-1 8 Counters ......................................................................................................................................8-1 9 Glossary ......................................................................................................................................9-1 10 Reference Documents .........................................................................................................10-1

Issue 01 (2012-04-28)

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

i


1 Introduction

1 Introduction 1.1 Scope This document describes policies for transmission resource management (TRM) over the Iub and Abis interfaces 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 of the GSM BSS or RAN Sharing Feature Parameter Description of the WCDMA RAN. For details about TRM, see the SingleRAN Transmission Resource Management Feature Parameter Description.

1.2 Intended Audience This document is intended for: 

Personnel who understand WCDMA and GSM 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 issues are as follows: 

01 (2012-04-28)



Draft A (2012-02-15)

01 (2012-04-28) This is the first release of GBSS14.0. Compared with issue draft A (2012-02-15) of GBSS14.0, issue 01 (2012-04-28) of GBSS14.0 has no change.

Draft A (2012-02-15) This is the draft release of GBSS14.0. Compared with issue 02 (2011-12-30) of GBSS13.0, issue draft A (2012-02-15) of GBSS14.0 has no change.

Issue 01 (2012-04-28)


1-1


2 Overview of Transmission Resource Management for RAN Sharing

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 and Abis interfaces 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. TRM policies for the Iub and Abis interfaces involve admission control on the control plane and flow control on the user plane. Table 2-1 lists these policies, which are configured through parameters. Table 2-1 TRM policies for the Iub and Abis interfaces Interface

TRM Policy Centralized admission and centralized flow control

Individual admission and individual flow control

Individual admission and centralized flow control

Abis



-



Iub







Remarks  is

used to mark supported policies, and - is used to mark unsupported policies.

The TRM policies are described as follows: 

Individual admission means that the transmission bandwidth requested by an operator's users can be taken only from that operator's dedicated bandwidth. For details about admission process, 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.



Individual flow control means that the RNC or BSC performs individual congestion detection over each operator's dedicated bandwidth. When detecting congestion over an operator's dedicated bandwidth, the RNC or BSC imposes flow control only on that operator's users.



Centralized flow control means that the RNC or BSC performs congestion detection over the total bandwidth without distinguishing between operators. When detecting congestion, the RNC or BSC imposes flow control on all operators' users.

In this document, transmission resources over the Iub and Abis interfaces refer to the physical resources (fractional IMA links, UNI links, IMA groups, PPP links, and MP groups), logical resources (logical ports), and path resources (ATM and IP paths). The NCP, CCPs, and ALCAP links between the RNC and the NodeB are shared among all operators. The OML between the BSC and the BTS is also shared among all operators.

Issue 01 (2012-04-28)


2-1


3 Individual Admission and Centralized Flow Control

3 Individual Admission and Centralized Flow Control This policy corresponds to the features WRFD-02130501 Dedicated Iub Transmission Control and GBFD-118704 Abis Independent Transmission. In this policy, admission decision is made on an operator's users over this operator's dedicated bandwidth, 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 (PPP link)/OPSEPFLAG (FRA link)/OPSEPFLAG (UNI link)/OPSEPFLAG (IMA group)/OPSEPFLAG (IP logical port) parameter for the ports be set to ON. As a result, each operator has dedicated bandwidths and load thresholds for the ports. Figure 3-1 shows how bandwidth is allocated in a situation where two operators (OPA and OPB) share a NodeB or BTS. The bandwidth allocation proportion and load thresholds for each operator are configured by using the MML command ADD OPSEPINFO. Figure 3-1 Allocating bandwidth

When a user requests transmission resources, admission decision is first made over the serving operator's dedicated bandwidth. If the request is admitted, admission decision is then made over the total bandwidth. Specifically, admission decision is made successively on paths, operators' dedicated bandwidths over logical ports, the total bandwidth over logical ports, operators' dedicated bandwidths 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. Congestion occurs when the bandwidth occupied by admitted users reaches a preset congestion threshold. The RNC or BSC triggers load reshuffling (LDR) when it detects congestion. The RNC or BSC performs congestion detection on each port in the following ways: 

Monitors the usage of operators' dedicated bandwidths. When the RNC or BSC 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-28)


3-1

GSM BSS TRM in the RAN Sharing Scenario 

3 Individual Admission and Centralized Flow Control

Monitors the usage of the total bandwidth. When the RNC or BSC 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 and Port Congestion

LDR Objects An operator's users and then all users LDR is first performed on an operator's u sers. If congestion persists after the congestion caused by these users is lifted, LDR will be performed on all users.

OP Congestion

An operator's users

Port Congestion

All users

Overload occurs when the bandwidth occupied by admitted users over a port exceeds the sending capabilities of that port. The RNC or BSC checks the usage of the total bandwidth for the port. When the bandwidth usage reaches the overload threshold for the port, the RNC or BSC performs overload control (OLC) on all users to quickly lift overload.

Issue 01 (2012-04-28)


3-2


4 Centralized Admission and Centralized Flow Control

4 Centralized Admission and Centralized Flow Control This policy corresponds to the features WRFD-02130406 Transmission Resource Sharing on the Iub/Iur Interface and GBFD-118701 BSS Sharing. The R s c M n g M o d e parameter for the Iub interface needs to be set to SHARE and the SptTRMShare parameter for the Abis interface needs to be set to YES. 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 or BTS. Figure 4-1 Allocating bandwidth

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 or BSC centrally monitors the bandwidth usage over paths, logical ports, and physical ports. When the RNC or BSC detects that the bandwidth usage over a path, logical port, or physical port has reached the congestion threshold, it performs LDR on all users. When the RNC or BSC detects that the bandwidth usage over a path, logical port, or physical port has reached the overload threshold, it performs OLC on all users.

Issue 01 (2012-04-28)


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 R s c M 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. 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

When a user requests transmission resources, admission decision is made over operators' dedicated bandwidths. Specifically, admission decision is made successively on operators' dedicated bandwidths over paths, operators' dedicated bandwidths over logical ports, 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. The RNC monitors the bandwidth usage over each operator's dedicated paths and logical ports. W hen the RNC detects that the bandwidth occupied by an operator's admitted users has reached the congestion threshold for this operator, 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 operator, it performs OLC on this operator's users.

Issue 01 (2012-04-28)


5-1


6 Engineering Guidelines

6 Engineering Guidelines When ATM/IP transmission is used, transmission networks are classified into convergence and non-convergence transmission networks. This chapter assumes that two operators share a NodeB or BTS. For details about transmission convergence, see the Transmission Resource Management Feature Parameter Description.

6.1 Non-Convergence Transmission Network Over the Iub and Abis Interfaces 6.1.1 Dedicated Bandwidths Overview As shown in Figure 6-1, two operators share a RAN and have dedicated transmission bandwidths over the Iub and Abis interfaces. Figure 6-1 Shared RAN and dedicated transmission bandwidths over the Iub and Abis interfaces

BW: Bandwidth

BS: Base station

Configuring Individual Admission and Centralized Flow Control for ATM/IP Networking When individual admission and centralized flow control are implemented, each operator has dedicated bandwidths on PPP and MLPPP links if the Iub and Abis interfaces use IP transmission. When individual admission and centralized flow control are implemented, each operator has dedicated 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:

Issue 01 (2012-04-28)


6-1





On the RNC side, set the R s c M n g M o d e parameter to EXCLUSIVE when running the MML command ADD UNODEB.



On the BSC side, set the SptTRMShare parameter to NO when running the MML command SET BTSSHARING.



On PPP links, MLPPP links, fractional IMA links, UNI links, and IMA links, perform the following steps to allocate 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 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 Centralized Flow Control for TDM Networking In Abis over TDM mode, operators have dedicated E1 links over the Abis interface. The operation and maintenance link (OML) between the BSC and the BTS is shared among all operators. The OML is only carried on the primary operator's E1 link. To enable operators to manage their respective dedicated transmission-resources over the Abis interface, set parameters as follows: 

When running the MML command SET BTSSHARING, set the SptTRMShare parameter to NO.



When running the MML command ADD BTSCONNECT, specify an operator name (O P N A M E) for each E1 link.



When running the MML command SET BTSOMLTS, set the PN , CN , SR N , and SN parameters to the values of the INPN , INCN , INSRN , and INSN parameters set in the MML command ADD BTSCONNECT, respectively.

Configuring Individual Admission and Individual Flow Control for ATM/IP Networking This policy is applicable only to the Iub interface. 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 R s c M n g M o d e 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:

Issue 01 (2012-04-28)


6-2



− When

running the MML command ADD IPPATH, set the C A R R Y F L A G parameter to IPLGCPORT and specify TRM load threshold tables for IP paths.

− When

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 f or 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.

6.1.2 Shared Bandwidth Overview As shown in Figure 6-2, two operators share a RAN and transmission bandwidths over the Iub and Abis interfaces. Figure 6-2 Shared RAN and shared transmission bandwidths over the Iub and Abis interfaces

BW: Bandwidth

BS: Base station

Configuring Centralized Admission and Centralized Flow Control for ATM/IP Transmission In this policy, operators share paths and physical resources. To achieve centralized resource management over the Iub and Abis interfaces, set parameters as follows: 

On the RNC side, set the R s c M n g M o d e parameter to SHARE when running the MML command ADD UNODEB.



On the BSC side, set the SptTRMShare parameter to YES when running the MML command SET BTSSHARING.

Issue 01 (2012-04-28)


6-3



Configuring Centralized Admission and Centralized Flow Control for TDM Transmission In Abis over TDM mode, operators share E1 links over the Abis interface. To achieve centralized resource management over the Abis interface, set parameters as follows: 

When running the MML command SET BTSSHARING, set the SptTRMShare parameter to YES.



When running the MML command ADD BTSCONNECT, do not specify an operator name (OPNAME ) for any E1 link.

6.2 Convergence Transmission Network Over the Iub and Abis Interfaces 6.2.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. 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 for IP Networking To enable operators to manage their respective dedicated transmission-resources over logical ports, set parameters as follows: 

On the RNC side, set the R s c M n g M o d e parameter to EXCLUSIVE when running the MML command ADD UNODEB.



On the BSC side, set the SptTRMShare parameter to NO when running the MML command SET BTSSHARING.

Issue 01 (2012-04-28)


6-4

GSM BSS TRM in the RAN Sharing Scenario 


On logical ports, perform the following steps to allocate 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 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 for ATM/IP Networking See "Configuring Individual Admission and Individual Flow Control for ATM/IP Networking" in section 6.1.1.

6.2.2 Shared Bandwidth As shown in Figure 6-4, two operators share a RAN and transmission bandwidths over the Iub and Abis interfaces. Figure 6-4 Shared RAN and shared transmission bandwidths over the Iub and Abis interfaces

BW: Bandwidth

BS: Base station

To achieve centralized resource management over the Iub and Abis interfaces, set parameters as follows: 

On the RNC side, set the R s c M n g M o d e parameter to SHARE when running the MML command ADD UNODEB.



On the BSC side, set the SptTRMShare parameter to YES when running the MML command SET BTSSHARING.



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-28)


6-5


7 Parameters

7 Parameters Table 7-1 Parameter description Parameter ID

NE

MML Command

CARRYFLAG

BSC6900

ADD IPPATH MOD IPPATH

Description 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 Default Value: NULL(NULL) Unit: None

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,

Issue 01 (2012-04-28)


7-1


Parameter ID

7 Parameters

NE

MML Command

Description ATMLOGICPORT, NULL Default Value: None Unit: None

CN

BSC6900

SET BTSOMLTS

Meaning: Number of the cabinet where the port is located. GUI Value Range: 0~62;255 Actual Value Range: 0~62, 255 Default Value: None Unit: 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 Default Value: None Unit: None

INCN

BSC6900

MOD BTSCONNECT

Meaning: Number of the in-port cabinet on a BTS

RMV BTSCONNECT

GUI Value Range: 0~62

ADD BTSCONNECT

Actual Value Range: 0~62 Default Value: None Unit: None INPN

BSC6900

MOD BTSCONNECT

Meaning: Number of a BTS port

RMV BTSCONNECT


ADD BTSCONNECT

Actual Value Range: 0~23 Default Value: None Unit: None INSN

BSC6900

MOD BTSCONNECT

Meaning: Number of the in-port slot on a BTS

RMV BTSCONNECT


ADD BTSCONNECT

Actual Value Range: 0~23 Default Value: None Unit: None INSRN

Issue 01 (2012-04-28)

BSC6900

ADD BTSCONNECT


Meaning: Number of the

7-2


Parameter ID

7 Parameters

NE

MML Command

Description

MOD BTSCONNECT

in-port subrack on a BTS

RMV BTSCONNECT

GUI Value Range: 0~254 Actual Value Range: 0~254 Default Value: None Unit: None

OPNAME

BSC6900

ADD BTSCONNECT MOD BTSCONNECT

Meaning: Name of the operator. This parameter uniquely identifies an operator. GUI Value Range: 0~255 characters Actual Value Range: 0~255 characters Default Value: None Unit: None

OPSEPFLAG

BSC6900

ADD IPLOGICPORT MOD IPLOGICPORT

Meaning: Operator Separated Flag. GUI Value Range: OFF(OFF), ON(ON) Actual Value Range: OFF, ON Default Value: OFF(OFF) Unit: None

OPSEPFLAG

BSC6900

ADD PPPLNK MOD PPPLNK


OPSEPFLAG

BSC6900

ADD FRALNK MOD FRALNK


OPSEPFLAG

BSC6900

ADD UNILNK MOD UNILNK

Meaning: Operator Separated Flag. GUI Value Range:

Issue 01 (2012-04-28)


7-3


Parameter ID

7 Parameters

NE

MML Command

Description OFF(OFF), ON(ON) Actual Value Range: OFF, ON Default Value: OFF(OFF) Unit: None

OPSEPFLAG

BSC6900

ADD IMAGRP MOD IMAGRP


OPSEPINDEX

BSC6900

ADD FRALNK MOD FRALNK

Meaning: Operator Separated Index. The value can be queried by the "LST OPSEPINFO" command. GUI Value Range: 0~199 Actual Value Range: 0~199 Default Value: None Unit: None

OPSEPINDEX

BSC6900

ADD UNILNK MOD UNILNK


OPSEPINDEX

BSC6900

ADD IMAGRP MOD IMAGRP


Issue 01 (2012-04-28)


7-4


7 Parameters

Parameter ID

NE

MML Command

OPSEPINDEX

BSC6900

ADD PPPLNK MOD PPPLNK

Description Meaning: Operator Separated Index. The value can be queried by the "LST OPSEPINFO" command. GUI Value Range: 0~199 Actual Value Range: 0~199 Default Value: None Unit: None

OPSEPINDEX

BSC6900

ADD IPLOGICPORT MOD IPLOGICPORT


PN

BSC6900

SET BTSOMLTS

Meaning: Number of the port on the BTS side. GUI Value Range: 0~23;255 Actual Value Range: 0~23, 255 Default Value: None Unit: None

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 Default Value: None Unit: None

RSCMNGMODE

Issue 01 (2012-04-28)

BSC6900

ADD ATMLOGICPORT Meaning: Resource management mode of


7-5


Parameter ID

7 Parameters

NE

MML Command

Description logical port GUI Value Range: SHARE, EXCLUSIVE Actual Value Range: SHARE, EXCLUSIVE Default Value: None Unit: 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 Default Value: SHARE(Share) Unit: None

SN

BSC6900

SET BTSOMLTS

Meaning: Number of the slot where the port is located. GUI Value Range: 0~23;255 Actual Value Range: 0~23, 255 Default Value: None Unit: None

SRN

BSC6900

SET BTSOMLTS

Meaning: Number of the subrack where the port is located. GUI Value Range: 0~255 Actual Value Range: 0~255 Default Value: None Unit: None

SptTRMShare

BSC6900

SET BTSSHARING

Meaning: Whether to allow the operator to share the transmission resource. GUI Value Range: NO(NO), YES(YES) Actual Value Range: NO, YES Default Value: YES(YES)

Issue 01 (2012-04-28)


7-6


Parameter ID

NE

7 Parameters

MML Command

Description Unit: None

Issue 01 (2012-04-28)


7-7


8 Counters

8 Counters There are no specific counters associated with this feature.

Issue 01 (2012-04-28)


8-1


9 Glossary

9 Glossary For the acronyms, abbreviations, terms, and definitions, see the Glossary .

Issue 01 (2012-04-28)


9-1


10 Reference Documents

10 Reference Documents [1] RAN Sharing Feature Parameter Description of the WCDMA RAN [2] Transmission Resource Management Feature Parameter Description [3] RAN Sharing Feature Parameter Description of the GSM BSS

Issue 01 (2012-04-28)


10-1

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

Recommend Documents