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 the property of Huawei Technologies Co., Ltd. All othertrademarks 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 commercial contract made betweenHuawei and the customer. All or partial products, services and features described in this document maynot be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, allstatements, 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 thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.
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 Interfaces........................................ 6-4 6.2.1 Dedicated Bandwidths .......................................................................................................... 6-4 6.2.2 Shared Bandwidth ................................................................................................................ 6-5
This document describes policies for transmission resource management (TRM) over the Iub and Abisinterfaces 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 theRAN Sharing Feature Parameter Description of the GSM BSS or RAN Sharing Feature Parameter Description of theWCDMA RAN. For details about TRM, see the SingleRAN Transmission Resource Management Feature ParameterDescription.
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 (2011-03-30)
01 (2011-03-30)
This is the document for the first commercial release of SRAN6.0.
Compared with Draft A (2010-12-30) for RAN13.0, this issue incorporates the following changes:
Change Type Description Parameter Change
Feature change Added TRM over the Abis interface forRAN sharing on a GSM network.
Added the following parameters:
OPSEPFLAG
OPSEPINDEX
SptTRMShare
OPNAME
Editorial change Added description of TRM over the Abisinterface for RAN sharing on a GSMnetwork.
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 and Abis interfaces in a shared or exclusive way. These transmission resourcescan be managed on a centralized or individual basis. Centralized management improves bandwidthefficiency and lowers costs for operators and individual management provides better QoS guarantees foreach operator's users.
TRM policies for the Iub and Abis interfaces involve admission control on the control plane and flowcontrol 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 flowcontrol
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 betaken only from that operator's dedicated bandwidth. For details about admission process, seeTransmission Resource Management Feature Parameter Description.
Centralized admission means that the transmission bandwidth requested by all operators' users istaken from the total bandwidth.
Individual flow control means that the RNC or BSC performs individual congestion detection over eachoperator'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 totalbandwidth without distinguishing between operators. When detecting congestion, the RNC or BSCimposes 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 theNodeB are shared among all operators. The OML between the BSC and the BTS is also shared amongall operators.
3 Individual Admission and Centralized Flow Control
This policy corresponds to the features WRFD-02130501 Dedicated Iub Transmission Control andGBFD-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 usersover the total bandwidth. In situations where IP over E1/T1 networking is adopted for transmission, thispolicy is not supported if the links carried on E1/T1 links are PPP links and port load sharing is enabledfor 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 (FRAlink)/OPSEPFLAG (UNI link)/OPSEPFLAG (IMA group)/OPSEPFLAG (IP logical port) parameter for theports be set to ON. As a result, each operator has dedicated bandwidths and load thresholds for theports.
Figure 3-1 shows how bandwidth is allocated in a situation where two operators (OPA and OPB) share aNodeB 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
In cases where admission decision is made on each operator' dedicated bandwidth, when a userrequests 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 overlogical 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 preempttransmission 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 or BSC performs congestion detection on each port inthe 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 admittedusers 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.
When the RNC or BSC detects that the usage of the bandwidth occupied by all admitted users hasreached the congestion threshold for this port, it regards all admitted users as having causedcongestion. 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 LDR Objects
OP Congestion and PortCongestion
An operator's users and then all users
LDR is first performed on an operator's users. If congestion persists afterthe congestion caused by these users is lifted, LDR will be performed onall 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 sendingcapabilities of that port. The RNC or BSC checks the usage of the total bandwidth for the port. When thebandwidth usage reaches the overload threshold for the port, the RNC or BSC performs overload control(OLC) on all users to quickly lift overload.
For details about LDR and OLC, see the Transmission Resource Management Feature ParameterDescription.
4 Centralized Admission and Centralized Flow Control
This policy corresponds to the features WRFD-02130406 Transmission Resource Sharing on the Iub/IurInterface and GBFD-118701 BSS Sharing. The RscMngMode 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 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 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 totalbandwidth 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 hasreached the congestion threshold, it performs LDR on all users. When the RNC or BSC detects that thebandwidth usage over a path, logical port, or physical port has reached the overload threshold, itperforms OLC on all users.
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
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. 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 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 sameoperator.
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 operator, it performs LDR on this operator's users. When the RNC detectsthat 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.
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 into
convergence and non-convergence transmission networks. This chapter assumes that two operatorsshare a NodeB or BTS.
For details about transmission convergence, see the Transmission Resource Management FeatureParameter Description.
6.1 Non-Convergence Transmission Network Over the Iub andAbis Interfaces
6.1.1 Dedicated Bandwidths
Overview
As shown in Figure 6-1, two operators share a RAN and have dedicated transmission bandwidths overthe Iub and Abis interfaces.
Figure 6-1 Shared RAN and dedicated transmission bandwidths over the Iub and Abis interfaces
Configuring Individual Admission and Centralized Flow Control for ATM/IPNetworking
When individual admission and centralized flow control are implemented, each operator has dedicatedbandwidths on PPP and MLPPP links if the Iub and Abis interfaces use IP transmission. When individualadmission and centralized flow control are implemented, each operator has dedicated bandwidths onfractional 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 RscMngMode parameter to EXCLUSIVE when running the MML commandADD UNODEB.
On the BSC side, set the SptTRMShare parameter to NO when running the MML command SETBTSSHARING.
On PPP links, MLPPP links, fractional IMA links, UNI links, and IMA links, perform the following stepsto 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 operatorsand 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 (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 Centralized Flow Control for TDMNetworking
In Abis over TDM mode, operators have dedicated E1 links over the Abis interface. The operation andmaintenance link (OML) between the BSC and the BTS is shared among all operators. The OML is onlycarried on the primary operator's E1 link.
To enable operators to manage their respective dedicated transmission-resources over the Abisinterface, 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 (OPNAME ) for
each E1 link. When running the MML command SET BTSOMLTS, set the PN , CN , SRN , and SN parameters to the
values of the INPN , INCN , INSRN , and INSN parameters set in the MML command ADDBTSCONNECT, respectively.
Configuring Individual Admission and Individual Flow Control for ATM/IPNetworking
This policy is applicable only to the Iub interface. In this policy, operators use dedicated bandwidths overpaths 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 RscMngMode 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.
6.1.2 Shared Bandwidth
Overview
As shown in Figure 6-2, two operators share a RAN and transmission bandwidths over the Iub and Abisinterfaces.
Figure 6-2 Shared RAN and shared transmission bandwidths over the Iub and Abis interfaces
Configuring Centralized Admission and Centralized Flow Control for ATM/IPTransmission
In this policy, operators share paths and physical resources.
To achieve centralized resource management over the Iub and Abis interfaces, set parameters asfollows:
On the RNC side, set the RscMngMode parameter to SHARE when running the MML command ADDUNODEB.
On the BSC side, set the SptTRMShare parameter to YES when running the MML command SET
Configuring Centralized Admission and Centralized Flow Control for TDMTransmission
In Abis over TDM mode, operators share E1 links over the Abis interface. To achieve centralizedresource 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 AbisInterfaces
6.2.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.
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 IPNetworking
To enable operators to manage their respective dedicated transmission-resources over logical ports, setparameters as follows:
On the RNC side, set the RscMngMode parameter to EXCLUSIVE when running the MML commandADD UNODEB.
On the BSC side, set the SptTRMShare parameter to NO when running the MML command SETBTSSHARING.
On logical ports, perform the following steps to allocate bandwidths to operators and configurededicated 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 bandwidths to operators and specify TRM load threshold tables 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 for ATM/IPNetworking
See "Configuring Individual Admission and Individual Flow Control for ATM/IP Networking" in section6.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 Abisinterfaces.
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 asfollows:
On the RNC side, set the RscMngMode parameter to SHARE when running the MML command ADDUNODEB.
On the BSC side, set the SptTRMShare parameter to YES when running the MML command SETBTSSHARING.
Set the RSCMNGMODE ( ATM logical port)/RSCMNGMODE (IP logical port) parameter to SHARE when running the MML command ADD ATMLOGICPORT or ADD IPLOGICPORT.
CN BSC6900 SET BTSOMLTS(Optional) Meaning: Number of thecabinet where the port islocated.
GUI Value Range: 0~62
Actual Value Range: 0~62
Default Value: None
CNMNGMODE BSC6900 ADD ADJMAP(Mandatory)
MOD ADJMAP(Mandatory)
RMV ADJMAP(Mandatory)
Meaning: Resourcemanagement mode. Whenthe interface type is IUB,the value can be set toSHARE or EXCLUSIVE.When the interface type isIUR, IUCS, or IUPS, the
