Академический Документы
Профессиональный Документы
Культура Документы
Issue 01
Date 2017-03-08
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview......................................................................................................................................... 5
2.1 Introduction.................................................................................................................................................................... 5
2.2 Benefits........................................................................................................................................................................... 5
2.3 Application Networking................................................................................................................................................. 6
3 Technical Description...................................................................................................................7
3.1 Introduction.................................................................................................................................................................... 7
3.2 Transmission Priorities................................................................................................................................................... 7
3.3 Traffic Limiting and Shaping....................................................................................................................................... 10
3.4 Load Control.................................................................................................................................................................12
3.5 Flow Control.................................................................................................................................................................12
4 Application Scenarios.................................................................................................................17
4.1 Unlimited Access Bandwidth for Multimode Base Stations........................................................................................ 17
4.1.1 Introduction............................................................................................................................................................... 17
4.1.2 Transmission Resource Management Strategies....................................................................................................... 18
4.2 Limited Access Bandwidth for Multimode Base Stations............................................................................................21
4.2.1 Introduction............................................................................................................................................................... 21
4.2.2 Transmission Resource Management Strategies....................................................................................................... 22
4.3 Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios................................................................. 26
4.3.1 Introduction............................................................................................................................................................... 26
4.3.2 Transmission Resource Management Strategies....................................................................................................... 27
4.4 Satellite Transmission for Multimode Base Stations (Without Distinguishing Transmission Priorities).................... 30
4.4.1 Introduction............................................................................................................................................................... 30
4.4.2 Transmission Resource Management Strategies....................................................................................................... 31
5 Related Features...........................................................................................................................34
5.1 MRFD-121115 Bandwidth sharing of MBTS Multi-mode Co-Transmission(GBTS)................................................. 34
5.2 MRFD-121125 Bandwidth sharing of MBTS Multi-mode Co-Transmission(NodeB)................................................34
6 Network Impact........................................................................................................................... 37
7 Engineering Guidelines............................................................................................................. 38
7.1 When to Use................................................................................................................................................................. 38
7.2 Required Information................................................................................................................................................... 38
7.3 Planning........................................................................................................................................................................ 38
7.4 Deployment.................................................................................................................................................................. 39
7.4.1 Requirements............................................................................................................................................................. 39
7.4.2 Precautions.................................................................................................................................................................39
7.4.3 Hardware Adjustment................................................................................................................................................40
7.4.4 Data Preparation........................................................................................................................................................ 40
7.4.5 Initial Configuration.................................................................................................................................................. 48
7.4.5.1 Access Bandwidth Unlimited for GUL/GUT/GULT Triple-Mode Base Stations..................................................48
7.4.5.2 Unlimited Access Bandwidth for GU Dual-Mode Base Stations...........................................................................51
7.4.5.3 Unlimited Access Bandwidth for GL/GT Dual-Mode Base Stations.....................................................................53
7.4.5.4 Unlimited Access Bandwidth for UL/UT/ULT Multimode Base Stations.............................................................54
7.4.5.5 Limited Access Bandwidth for GUL/GUT/GULT Multimode Base Stations........................................................56
7.4.5.6 Limited Access Bandwidth for GU Dual-Mode Base Stations.............................................................................. 62
7.4.5.7 Limited Access Bandwidth for GL/GT/GLT Multimode Base Stations................................................................ 64
7.4.5.8 Limited Access Bandwidth for UL/UT/ULT Multimode Base Stations................................................................ 65
7.4.5.9 Access Bandwidth Limited for Each Operator in a UL/UT Dual-Mode Base Station in RAN Sharing Scenarios
............................................................................................................................................................................................ 68
7.4.5.10 GU Dual-Mode Base Stations Using Satellite Transmission............................................................................... 75
7.4.6 Activation Observation..............................................................................................................................................77
7.4.6.1 Unlimited Access Bandwidth for Multimode Base Stations.................................................................................. 77
7.4.6.2 Limited Access Bandwidth for Multimode Base Stations......................................................................................78
7.4.6.3 Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios........................................................... 80
7.5 Performance Monitoring...............................................................................................................................................81
7.6 Parameter Optimization................................................................................................................................................ 81
7.7 Possible Issues.............................................................................................................................................................. 82
8 Parameters..................................................................................................................................... 83
9 Counters...................................................................................................................................... 110
10 Glossary..................................................................................................................................... 111
11 Reference Documents............................................................................................................. 112
1.1 Scope
This document describes the Bandwidth Sharing of Multimode Base Station Co-Transmission
feature, including the bandwidth sharing mechanism, recommended transmission
configuration strategies, application scenarios, related features, network impact, and
engineering guidelines. This feature applies to GSM/UMTS, GSM/LTE, UMTS/LTE, and
GSM/UMTS/LTE multimode base stations in co-transmission scenarios.
This document describes the following optional features:
l MRFD-121115 Bandwidth sharing of MBTS Multi-mode Co-Transmission(GBTS)
l MRFD-121125 Bandwidth sharing of MBTS Multi-mode Co-Transmission(NodeB)
l MRFD-121135 Bandwidth sharing of MBTS Multi-mode Co-Transmission(eNodeB)
l MRFD-121145 Bandwidth sharing of MBTS Multi-mode Co-Transmission(LTE TDD)
l MRFD-121155 Bandwidth sharing of MBTS Multi-mode Co-Transmission(NB-IoT)
Unless otherwise specified, in this document, LTE, eNodeB, and eRAN always include FDD,
TDD, and NB-IoT. The "L", "T", and "M" in RAT acronyms refer to LTE FDD, LTE TDD,
and LTE NB-IoT, respectively.
For definitions of base stations described in this document, see section "Base Station
Products" in SRAN Networking and Evolution Overview Feature Parameter Description.
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier
version
SRAN12.1 01 (2017-03-08)
This issue does not include any changes.
2 Overview
2.1 Introduction
The Bandwidth Sharing of Multimode Base Station Co-Transmission feature centrally
manages GSM, UMTS, and LTE transmission resources. When transmission resources are
congested, this feature ensures the smooth processing of high-priority services and prevents
GSM, UMTS, and LTE services from impacting each other. This ensures high service quality
and good user experience. Bandwidth Sharing of Multimode Base Station Co-Transmission
includes the following transmission resource management strategies: mapping between traffic
classes and transmission priorities, traffic limiting and shaping, load control, and flow control.
If this feature is not enabled, the transmission resources of a multimode base station are
managed in the same way as those of a single-mode base station. For details about
transmission resource management strategies for GSM, UMTS, and LTE, see Transmission
Resource Management Feature Parameter Description for GBSS and RAN, and Transport
Resource Management Feature Parameter Description for eRAN, respectively.
2.2 Benefits
GSM, UMTS, and LTE services have different peak hours. Therefore, transmission resources
of one mode can be multiplexed by other modes if this mode is not experiencing a traffic
peak. The Bandwidth Sharing of Multimode Base Station Co-Transmission feature provides
the following benefits:
l For a multimode base station in co-transmission scenarios, transmission resources can be
dynamically shared by GSM, UMTS, and LTE.
l As GSM services continuously shrink, the released GSM bandwidth can be used by
UMTS and LTE services.
l When uplink or downlink transmission resources of a multimode base station are
congested, the quality of service (QoS) of high-priority GSM, UMTS, and LTE services
can be guaranteed.
Figure 2-1 Networking scheme for a co-MPT GUL multimode base station in co-
transmission scenarios
For details about the networking scheme for a multimode base station in co-transmission
scenarios, see Common Transmission Feature Parameter Description for SingleRAN.
NOTE
l In this document, a multimode base station can be a GU/GL/GT/UL/UT/LT dual-mode base station,
a GUL/GLT/ULT/GUT triple-mode base station, or a GULT quadruple-mode base station. The
GSM, UMTS, or LTE side of a multimode base station is referred to as the GBTS/eGBTS, NodeB,
or eNodeB. LTE can be LTE FDD, LTE TDD, or LTE NB-IoT.
l Multimode base stations are classified into co-MPT and separate-MPT multimode base stations. The
GSM side of a separate-MPT multimode base station can be either an eGBTS or a GBTS. The GSM
side of a co-MPT multimode base station must be an eGBTS. The GBTS is not recommended for
providing a co-transmission port to a separate-MPT multimode base station. This scenario is not
covered in this document.
3 Technical Description
3.1 Introduction
For a separate-MPT multimode base station in co-transmission scenarios, the co-transmission
port transmits and receives the local data and the passing data. In this case, the co-
transmission port centrally schedules and manages the data of multiple modes. For a co-MPT
multimode base station in co-transmission scenarios, the co-transmission port transmits and
receives only the local data, which includes the data for all modes of this base station. In this
case, the co-transmission port centrally schedules and manages the data for all modes.
To enable a co-transmission port to implement unified data scheduling and management,
differentiation and fairness among different service types and modes must be ensured.
Moreover, transmission resource congestion when all of the modes have overlapping traffic
bursts must also be addressed. To address these problems, Huawei introduces the Bandwidth
Sharing of Multimode Base Station Co-Transmission feature.
NOTE
ensure that differentiated services (DiffServ) are provided to different service types based on
transmission priorities. Transmission priorities include the DiffServ Code Point (DSCP),
virtual local area network (VLAN) priority, and queue priority.
DSCP
DSCP is a field in an IP packet header to indicate the QoS requirements. Each node
implements DiffServ based on the DSCP value.
A multimode base station or a base station controller sets the DSCP value for each IP packet
based on the QoS requirements of each service type. From the DSCP value, intermediate
transmission devices identify the traffic class and related QoS requirements of the service and
perform per-hop behavior (PHB) accordingly. PHB includes transmission resource allocation,
queue scheduling, and packet discarding. All nodes in the network comply with PHB policies
according to the DSCP in the IP packet.
The following table describes how to use MML commands to configure the mapping between
traffic classes and DSCP values for each type of base station.
NE Command Description
GBTS SET BTSVLAN Used to set the mapping between DSCP values
and data from the O&M plane, control plane (CP),
and user plane (UP) on the GBTS side.
eGBTS and SET DIFPRI Used to set the mapping between DSCP values
NodeB and data from the O&M plane and CP plane on
the eGBTS or NodeB side.
eNodeB SET DIFPRI Used to set the mapping between DSCP values
and data from the O&M plane and CP plane on
the eNodeB side.
Pay attention to the following when mapping traffic classes and DSCP values:
NOTE
The mapping between traffic classes and DSCP values for GSM, UMTS, and LTE services should be
consistent on the base station, the base station controller, and the CN.
If control-plane EPS optimized transmission is used, NB-IoT services are carried only on SCTP links.
The priority for the control-plane data is the priority for NB-IoT services.
VLAN Priority
The VLAN tag defines the VLAN priority of an IP packet. Based on the VLAN priority,
Layer 2 devices can implement DiffServ.
VLAN priorities of packets with different traffic classes are determined by DSCP values.
Table 3-1 provides the default mapping between DSCP values and VLAN priorities on the
multimode base station side.
Table 3-1 Default mapping between DSCP values and VLAN priorities
DSCP VLAN Priority
0-7 0
8-15 1
16-23 2
24-31 3
32-39 4
40-47 5
48-55 6
56-63 7
Queue Priority
Queue priority defines the scheduling priority of a queue. Each Ethernet port or Point-to-Point
Protocol (PPP) link supports eight queues: PQ1, PQ2, PQ3, and WRR (which includes WFQ4
through WFQ8). The queues are displayed in descending order of scheduling priority. A
multimode base station puts packets with different traffic classes into different queues to
implement DiffServ.
NOTE
Queue priorities are determined for different traffic types according to the mapping between
DSCP values and queue priorities. Table 3-2 and Table 3-3 list the default mapping between
DSCP values of GSM, UMTS, and LTE services and queue priorities for multimode base
stations. You are not advised to modify the default mapping.
Table 3-2 Default mapping between DSCP values and queue priorities for the GBTS
DSCP Queue Queue Priority
40-63 PQ1 0
Reserved PQ2 1
Reserved PQ3 2
32-39 WFQ4 3
24-31 WFQ5 3
16-23 WFQ6 3
8-15 WFQ7 3
0-7 WFQ8 3
Table 3-3 Default mapping between DSCP values and queue priorities for the eGBTS,
NodeB, eNodeB, and co-MPT multimode base station
DSCP Queue Queue Priority
48-63 PQ1 0
40-47 PQ2 1
32-39 PQ3 2
24-31 WFQ4 3
16-23 WFQ5 3
8-15 WFQ6 3
0-7 WFQ7 3
The traffic limiting and shaping functions apply only to non-real-time services.
NOTE
Base stations cannot dynamically adjust the data rates of real-time services. To prevent real-time service
congestion, at the early stage of network deployment, the minimum bandwidth of the intermediate
transmission devices must be greater than the total bandwidth planned for real-time services in a GU,
GL, UL, or GUL multimode base station.
The traffic limiting and shaping functions can be configured at both the base station level and
the logical port level.
If the eGBTS, NodeB, eNodeB, or co-MPT multimode base station provides a co-
transmission port, you can run the SET LR command and specify the LR.CIR parameter to
set the bandwidth after traffic limiting for a base station.
If the eGBTS, NodeB, eNodeB, or co-MPT multimode base station provides a co-
transmission port, you can run the ADD RSCGRP command and specify the
RSCGRP.TXBW parameter to set the bandwidth after traffic limiting for a logical port.
l Co-MPT multimode base station controller
You can run the ADD IPLOGICPORT command and specify the
IPLOGICPORT.CIR (BSC6900, BSC6910) parameter to set the bandwidth after traffic
limiting for logical port.
NOTE
You are not advised to modify the rate using the ADD ETHPORT command.
Transport resource groups are classified into default port transport resource groups and non-default port
transport resource groups. One physical port can be configured with one or more default port transport
resource group and multiple non-default port transport resource groups. The following transport resource
group configuration policy is recommended for a co-MPT multimode base station:
l All modes use the same default transport resource group to implement traffic limiting and shaping.
l Each mode uses different non-default transport resource groups to implement traffic limiting and
shaping.
Table 3-4 Support for flow control on GSM, UMTS, and LTE
Mode NE Support for Flow Remarks
Control
The flow control algorithm on a NodeB calculates the transmission delay, the number of
discarded packets, and bandwidth resources available and then performs traffic shaping. In
this way, packet discarding caused by Iub interface congestion is prevented. This algorithm
takes effect only on HSDPA and HSUPA services. The NodeB dynamic flow control
algorithm is classified into two types, as listed in Table 3-5.
For a co-MPT UL or GUL multimode base station in co-transmission scenarios, the NodeB
sends the results of the uplink bandwidth adaptive adjustment algorithm to the eNodeB by
default. The eNodeB then performs uplink flow control according to the results. If the
eNodeB is not expected to use the results of the algorithm, two transmission resource groups
can be configured to carry UMTS and LTE services separately. In this situation, the eNodeB
performs LTE uplink flow control. For details, see Transport Resource Management Feature
Parameter Description for eRAN.
When packet loss (for example, packet loss caused by a bit error) occurs in the transmission
network due to non-congestion reasons, it is recommended that the enhanced function of
HSDPA flow control and the enhanced function of HSUPA Iub flow control in case of Iub
congestion be enabled to prevent the bandwidth from being falsely decreased by the flow
control algorithm.
l For details about the enhanced function of HSDPA flow control, see HSDPA Feature
Parameter Description.
l For details about the enhanced function of HSUPA Iub flow control in case of Iub
congestion, see Transmission Resource Management Feature Parameter Description for
RAN.
As described in Table 3-6, in UL and GUL co-transmission scenarios, if UMTS HSDPA
services are under flow control, the released UMTS bandwidth may be occupied by LTE
services. Consequently, the bandwidth available for UMTS services may decrease
considerably. To protect the bandwidth for UMTS HSDPA services, turn on the fair flow
control switch DLFLOWCTRLPARA.FAIRSWITCH on the NodeB side.
Table 3-6 Fair flow control switch on the NodeB side in co-transmission scenarios
Co-Transmission Whether the Fair Flow Control Switch Takes Effect
Scenario
Separate-MPT UL No
multimode base station
using panel
interconnection
Separate-MPT GUL
multimode base station
using panel
interconnection
The fair flow control switch can be configured either on a physical port (preferred) of a co-
MPT UL dual-mode base station or on the corresponding loopback interface (also called a
logical port) of the physical port. When configured on the loopback interface, the fair flow
control switch for co-MPT multimode base stations applies only to the following scenarios:
l Scenario 1: One loopback interface corresponds to one physical port, and UMTS and
LTE services are carried on the same physical port, as shown in Figure 3-2.
l Scenario 2: One loopback interface corresponds to multiple physical ports, and UMTS
and LTE services are carried on different physical ports, as shown in Figure 3-3.
NOTE
Scenario 2 does not belong to the multimode base station co-transmission networking scenario. It is
recommended that you configure the DLFLOWCTRLPARA.FAIRSWITCH for the loopback interface
in scenario 2.
The fair flow control switch ensures that at least 30% of the actual receive bandwidth is retained for
UMTS HSDPA services. This does not mean that the bandwidth retained for UMTS USDPA services is
equal to 30% of the actual receive bandwidth.
For details about the flow control algorithm, see Transmission Resource Management Feature
Parameter Description for RAN.
NOTE
4 Application Scenarios
4.1.1 Introduction
Access bandwidth unlimited for multimode base stations refers to scenarios in which:
l The operator cannot or has not planned access bandwidth for each multimode base
station.
l The bandwidth of the converging device, which converges the data of multimode base
stations, is either limited or unlimited.
For example, in Figure 4-1, the access bandwidth for each multimode base station is 100
Mbit/s and the bandwidth for intermediate transmission devices is also 100 Mbit/s.
Table 4-1 Recommended transmission priorities for different traffic classes if access
bandwidth is unlimited for multimode base stations
CS Voice EF 46 5
IP Clock EF 46 5
EML AF21 18 2
CS Voice EF 46 5
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
CCH&SRB&AMR EF 46 5
Conversational&Streami AF41 34 4
ng
R99 AF21 18 2
interactive&background
HSxPA AF11 10 1
interactive&background
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
QCI1 EF 46 5
QCI2 AF41 34 4
QCI3 AF41 34 4
QCI4 AF41 34 4
QCI5 EF 46 5
QCI6 AF21 18 2
QCI7 AF21 18 2
QCI8 AF21 18 2
QCI9 BE 0 0
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
In most cases, intermediate transmission devices support queue scheduling. Layer 3 and Layer
2 intermediate transmission devices support eight queues. However, if intermediate
transmission devices in the bearer network support less than eight queues, transmission
priority combining strategies listed in Table 4-2 are recommended. You can combine packets
with different DSCP values into one queue and combine packets with different VLAN
priorities into one queue. For example, if the intermediate transmission devices support six
queues, packets whose DSCP values are 48 and 46 can be put into one queue. Accordingly,
packets whose VLAN priorities are 6 and 5 can be put into one queue. This queue has the
highest transmission priority.
Number of DSCP Value for Each Queue VLAN Priority for Each Queue
Queues
NOTE
If there are only two queues, obtain from Huawei technical support personnel the method of combining
DSCP values.
If control-plane EPS optimized transmission is used, NB-IoT services are carried on SCTP links. The
transmission priority mapping for NB-IoT services is the transmission priority mapping for SCTP
services.
Table 4-3 Recommended settings for the NodeB flow control algorithm and the HSDPA fair
flow control switch if the access bandwidth is unlimited for multimode base stations
Base Station Type Setting of the Setting of the Setting of the
ULFLOWCTRLP DLFLOWCTRLP DLFLOWCTRLP
ARA.TNLCONGC ARA.SWITCH ARA.FAIRSWITC
TRLSWITCH H
Co-MPT GL dual-
mode base station
Co-MPT GUL
triple-mode base
station
NOTE
Configuring Traffic Limiting and Shaping on the Base Station Controller Side
Configure traffic limiting and shaping on the base station controller side and set the
bandwidth limit to the access bandwidth planned by the operator for a multimode base station.
Table 4-4 Recommended transmission priorities for different traffic classes if access
bandwidth is limited for multimode base stations
CS Voice EF 46 5
IP Clock CS6 46 6
EML AF21 18 2
CS Voice EF 46 5
OM High EF 46 5
OM Low AF21 18 2
IP Clock CS6 46 6
CCH&SRB&AMR EF 46 5
Conversational&Strea AF41 34 4
ming
R99 AF21 18 2
interactive&backgroun
d
HSxPA AF11 10 1
interactive&backgroun
d
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
QCI1 EF 46 5
QCI2 AF41 34 4
QCI3 AF41 34 4
QCI4 AF41 34 4
QCI5 EF 46 5
QCI6 AF21 18 2
QCI7 AF21 18 2
QCI8 AF21 18 2
QCI9 BE 0 0
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
In most cases, intermediate transmission devices support queue scheduling. Layer 3 and Layer
2 intermediate transmission devices support eight queues. However, if intermediate
transmission devices in the bearer network support less than eight queues, transmission
priority combining strategies listed in Table 4-5 are recommended. You can combine packets
with different DSCP values into one queue and combine packets with different VLAN
priorities into one queue. For example, if the intermediate transmission devices support six
queues, packets whose DSCP values are 48 and 46 can be put into one queue. Accordingly,
packets whose VLAN priorities are 6 and 5 can be put into one queue. This queue has the
highest transmission priority.
NOTE
If there are only two queues, obtain from Huawei technical support personnel the method of combining
DSCP values.
If control-plane EPS optimized transmission is used, NB-IoT services are carried on SCTP links. The
transmission priority mapping for NB-IoT services is the transmission priority mapping for SCTP
services.
Table 4-6 Recommended settings for the NodeB flow control algorithm and the HSDPA fair
flow control switch if access bandwidth is limited for multimode base stations
Base Station Setting of the Setting of the Setting of the Setting of the
Type RSCGRPALG. ULFLOWCTR DLFLOWCT DLFLOWCT
TCSW LPARA.TNLC RLPARA.SWI RLPARA.FAI
ONGCTRLSW TCH RSWITCH
ITCH
Co-MPT GL
dual-mode base
station
Base Station Setting of the Setting of the Setting of the Setting of the
Type RSCGRPALG. ULFLOWCTR DLFLOWCT DLFLOWCT
TCSW LPARA.TNLC RLPARA.SWI RLPARA.FAI
ONGCTRLSW TCH RSWITCH
ITCH
NOTE
4.3.1 Introduction
Limited access bandwidth for each operator in radio access network (RAN) sharing scenarios
refer to scenarios in which:
l Multiple operators share one multimode base station.
l Access bandwidth of one operator is not shared by other operators.
l Access bandwidth of one operator is shared among services of each mode run by this
operator.
l Access bandwidth for each operator is limited.
Access bandwidth for each operator is limited when the bearer network is leased. In
RAN15.0, limited access bandwidth for multiple operators in RAN sharing scenarios
applies only to UL dual-mode base stations. For example, in Figure 4-3, the access
bandwidth for each operator is limited to 10 Mbit/s.
Figure 4-3 Limited access bandwidth for each operator in RAN sharing scenarios
Table 4-7 Recommended transmission priorities for different traffic classes if access
bandwidth is limited for each operator in RAN sharing scenarios
NE Traffic Class PHB DSCP VLAN
Priority
CCH&SRB&AMR EF 46 5
Conversational&Streaming AF41 34 4
R99 AF21 18 2
interactive&background
HSxPA AF11 10 1
interactive&background
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
QCI1 EF 46 5
QCI2 AF41 34 4
QCI3 AF41 34 4
QCI4 AF41 34 4
QCI5 EF 46 5
QCI6 AF21 18 2
QCI7 AF21 18 2
QCI8 AF21 18 2
QCI9 BE 0 0
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
In most cases, intermediate transmission devices support queue scheduling. Layer 3 and Layer
2 intermediate transmission devices support eight queues. However, if intermediate
transmission devices in the bearer network support less than eight queues, transmission
priority combining strategies listed in Table 4-8 are recommended. You can combine packets
with different DSCP values into one queue and combine packets with different VLAN
priorities into one queue. For example, if the intermediate transmission devices support six
queues, packets whose DSCP values are 48 and 46 can be put into one queue. Accordingly,
packets whose VLAN priorities are 6 and 5 can be put into one queue. This queue has the
highest transmission priority.
Number of DSCP Value for Each Queue VLAN Priority for Each Queue
Queues
NOTE
If there are only two queues, obtain from Huawei technical support personnel the method of combining
DSCP values.
If control-plane EPS optimized transmission is used, NB-IoT services are carried on SCTP links. The
transmission priority mapping for NB-IoT services is the transmission priority mapping for SCTP
services.
Table 4-9 Recommended settings for the NodeB flow control algorithm and the HSDPA fair
flow control switch if access bandwidth is limited for each operator in RAN sharing scenarios
Scenario Setting of the Setting of the Setting of the Setting of the
RSCGRPALG ULFLOWCTR DLFLOWCT DLFLOWCT
.TCSW LPARA.TNLC RLPARA.SWI RLPARA.FAI
ONGCTRLS TCH RSWITCH
WITCH
Co-MPT UL ENABLE(Enab
dual-mode base le) (default
station value)
NOTE
4.4.1 Introduction
Satellite transmission for multimode base stations (without distinguishing transmission
priorities) refers to scenarios in which differentiated services cannot be performed on satellite
transmission networks based on their transmission priorities. This scenario is applicable only
to GU dual-mode base stations.
Figure 4-4 uses an example of two GU dual-mode base stations for illustrating satellite
transmission. The access bandwidth for each GU dual-mode base station is limited to 4 Mbit/s
and the satellite transmission network where the GU dual-mode base stations access cannot
distinguish their transmission priorities. In this case, transmission packets are processed
according to the first-come first-served policy.
Table 4-10 Recommended transmission priorities for different traffic classes if satellite
transmission is used for GU dual-mode base stations
NE Traffic Class PHB DSCP VLAN
Priority
CS Voice EF 46 5
IP Clock CS6 46 6
EML AF21 18 2
CS Voice EF 46 5
OM High EF 46 5
OM Low AF21 18 2
IP Clock CS6 46 6
CCH&SRB&AMR EF 46 5
Conversational&Streamin AF41 34 4
g
R99 AF21 18 2
interactive&background
HSxPA AF11 10 1
interactive&background
OM High EF 46 5
OM Low AF21 18 2
IP Clock EF 46 5
NOTE
In this scenario, the satellite transmission does not distinguish transmission priorities. Therefore, the
transmission priorities for the preceding traffic classes take effect on the multimode base station side.
Table 4-11 Recommended settings for the NodeB flow control algorithm if satellite
transmission is used for GU dual-mode base stations
Base Station Setting of the Setting of the Setting of the Setting of the
Type RSCGRPALG ULFLOWCTR DLFLOWCT DLFLOWCTR
.TCSW LPARA.TNLC RLPARA.SW LPARA.FAIR
ONGCTRLSW ITCH SWITCH
ITCH
NOTE
If the configured UL committed information rate (CIR) is less than or equal to 2 Mbit/s, you need to set
RSCGRPALG.TCSW to DISABLE. Otherwise, the OM service rate may decrease dramatically.
5 Related Features
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
None
Impacted Features
None
6 Network Impact
System Capacity
No impact.
Network Performance
If the settings of inter-RAT parameters, such as inter-RAT bandwidth allocation and inter-RAT
QoS planning, are inappropriate, activating this feature will have the following impacts:
l Increased service congestion rates
l Reduced data rates of low-priority services, for example, best effort (BE) services
l Increased packet loss rates of low-priority services
7 Engineering Guidelines
7.3 Planning
This section describes planning activities you need to complete before you implement the
feature.
RF Planning
N/A
Network Planning
l Transmission bandwidth plan for radio services
Make a transmission bandwidth plan each for the GBTS/eGBTS, NodeB, and eNodeB of
a multimode base station based on the service plan and the corresponding bandwidth
requirements.
l QoS plan for radio services
For a GU, GL, UL, or GUL multimode base station in co-transmission scenarios, it is
recommended that signaling and circuit switched (CS) services be classified as real-time
services and packet switched (PS) services as non-real-time services. Set real-time
services to a higher priority than non-real-time services to ensure the continuity of
signaling and CS services when transmission resources become congested. Activate the
flow control algorithm for each mode to properly allocate transmission resources across
non-real-time services when transmission resources become congested.
l Traffic class and transmission priority mapping
Plan traffic classes, DSCP values, VLAN priorities, and the mapping between traffic
classes and DSCP values based on the QoS plan of services.
l QoS plan for the bearer network
Plan DSCP values, VLAN priorities, and the number of PQ queues for layer-3 and
layer-2 devices based on service priorities.
l Bandwidth plan for the bearer network
Plan bandwidth for the bearer network based on services' bandwidth requirements and
available bandwidth resources.
When planning transmission bandwidth on the RAN side, ensure that the bandwidth
between a base station and a base station controller is higher than the total bandwidth of
real-time services to avoid reducing the service quality of real-time services.
Hardware Planning
N/A
7.4 Deployment
This section describes how to deploy the Bandwidth Sharing of Multimode Base Station Co-
Transmission feature.
7.4.1 Requirements
Other Features
For details, see 5 Related Features.
License
This feature has been changed to basic, and is not under license control.
7.4.2 Precautions
None
Table 7-1 Data to prepare for configuring traffic limiting and shaping if access bandwidth is
limited for multimode base stations
If access bandwidth is limited for each operator in multi-operator scenarios, data for traffic
limiting and shaping must be prepared on the base station side that provides a co-transmission
port. Table 7-2 lists the data to prepare for configuring traffic limiting and shaping.
Table 7-2 Data to prepare for configuring traffic limiting and shaping if access bandwidth is
limited for each operator in multi-operator scenarios
If access bandwidth is unlimited for multimode base stations and limited for each operator in
multi-operator scenarios, data for traffic limiting and shaping must be prepared on the BSC or
RNC side. Table 7-3 lists the data to prepare for configuring traffic limiting and shaping.
Table 7-3 Data to prepare for traffic limiting and shaping on the BSC or RNC side
Transport QoS
l Transport QoS for GSM services
– Table 7-4 lists the data to prepare for configuring the mapping between DSCP
values and data from the O&M plane, CP, and UP of a GBTS.
– Table 7-5 lists the data to prepare for configuring the mapping between DSCP
values and data from the O&M plane and CP of an eGBTS.
– Table 7-7 lists the data to prepare for configuring the mapping between DSCP
values and data from the O&M plane and CP of a BSC. Table 7-8 lists the data to
prepare for configuring the mapping between DSCP values and data from the UP of
a BSC.
l Transport QoS for UMTS services
– Table 7-5 lists the data to prepare for configuring the mapping between DSCP
values and data from the O&M plane and CP of a NodeB.
– Table 7-9 lists the data to prepare for configuring the mapping between DSCP
values and data from the O&M plane, CP, and UP of an RNC.
l Transport QoS for LTE services
– Table 7-5 lists the data to prepare for configuring the mapping between DSCP
values and data from the O&M plane and CP of an eNodeB. Table 7-6 lists the data
to prepare for configuring the mapping between DSCP values and data from the UP
of an eNodeB.
Table 7-4 Data to prepare for configuring the mapping between DSCP values and data from
the O&M plane, CP, and UP of a GBTS
Table 7-5 Data to prepare for configuring the mapping between DSCP values and data from
the O&M plane and CP of the eGBTS, NodeB, and eNodeB side of a co-MPT multimode
base station
OM Low OMLOWPRI
Priority
Table 7-6 Data to prepare for configuring the mapping between DSCP values and data from
the UP of an eNodeB
Table 7-7 Data to prepare for configuring the mapping between DSCP values and data from
the O&M plane and CP of a BSC
MO Parameter Parameter ID Setting Notes
Name
Table 7-8 Data to prepare for configuring the mapping between DSCP values and data from
the UP of a BSC
MO Parameter Name Parameter ID Setting Notes
Table 7-9 Data to prepare for configuring the mapping between DSCP values and data from
the CP and UP of an RNC
MO Parameter Name Parameter ID Setting Notes
Flow Control
Table 7-10 Data to prepare for setting the flow control algorithm on the NodeB side
MO Parameter Parameter ID Setting Notes
Name
Other Data
Table 7-11 lists other data to prepare if access bandwidth is limited for multimode base
stations.
Table 7-11 Other data to prepare if access bandwidth is limited for multimode base stations
Data Item Sample Value Remarks
Table 7-12 Other data to prepare if access bandwidth is limited for each operator in RAN
sharing scenarios
Data Item Sample Value Remarks
Table 7-13 Other data to prepare if satellite transmission is used for GU dual-mode base
station
Data Item Sample Value Remarks
----End
//Setting the mapping between DSCP values and data from the CP on the Abis interface
SET BSCABISPRIMAP: IDTYPE=BYID, BTSID=1, TRANSTYPE=IP, OMLDSCP=48, RSLDSCP=48,
EMLDSCP=18, ESLDSCP=48;
//Adding the mapping from the Abis interface to the TRMMAP index
ADD ADJMAP: ANI=3, ITFT=ABIS, TMIGLD=111, FTI=1;
//Setting the mapping between DSCP values and data from the CP of an eGBTS
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;
----End
//Adding the mapping from the Iub interface to the TRMMAP index
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110,
TMIBRZ=110, FTI=1;
//Configuring the dynamic flow control algorithm for the NodeB (when the bearer network
supports two or more queues)
----End
NOTE
If control-plane EPS optimized transmission is used, NB-IoT services are carried on SCTP links. No
configuration for the user-plane MO UDTPARAGRP is required.
//Setting the mapping between DSCP values and data from the CP of an eNodeB
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;
//Setting the mapping between DSCP values and user-plane data of an eNodeB. If the control
plane CIoT EPS optimization function is implemented between the NB-IoT eNodeB and
EPC, no user-plane data configuration is required.
MOD UDTPARAGRP: UDTPARAGRPID=40, PRIRULE=DSCP, PRI=46, ACTFACTOR=100;
MOD UDTPARAGRP: UDTPARAGRPID=41, PRIRULE=DSCP, PRI=26, ACTFACTOR=100;
MOD UDTPARAGRP: UDTPARAGRPID=42, PRIRULE=DSCP, PRI=34, ACTFACTOR=100;
MOD UDTPARAGRP: UDTPARAGRPID=43, PRIRULE=DSCP, PRI=26, ACTFACTOR=100;
MOD UDTPARAGRP: UDTPARAGRPID=44, PRI=46;
MOD UDTPARAGRP: UDTPARAGRPID=45, PRI=18;
MOD UDTPARAGRP: UDTPARAGRPID=46, PRI=18;
MOD UDTPARAGRP: UDTPARAGRPID=47, PRI=18;
MOD UDTPARAGRP: UDTPARAGRPID=48, PRI=0;
Step 1 Set GSM, UMTS, and LTE parameters on the CME according to the operation sequence
described in Table 7-14, Table 7-15, and Table 7-16. For instructions on how to perform the
CME single configuration, see CME Single Configuration Operation Guide.
1 a TRMMAP GBSC
b BSCABISPRIMAP GBSC
c ADJMAP GBSC
2 a BTSVLAN/DIFPRI GBTS/eGBTS
1 a TRMMAP RNC
b ADJMAP RNC
2 a DIFPRI NodeB
b ULFLOWCTRLPARA NodeB
c DLFLOWCTRLPARA NodeB
1 a DIFPRI eNodeB
b UDTPARAGRP eNodeB
----End
----End
//Adding the mapping from the Iub interface to the TRMMAP index
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110,
TMIBRZ=110, FTI=1;
//Configuring the uplink bandwidth adaptive flow control switch and HSDPA flow control
switch on the NodeB side
//Adding an HSUPA flow control parameter
ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0,
BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;
Set parameters GSM and UMTS on the CME according to the operation sequence described
in Table 7-14 and Table 7-17. For instructions on how to perform the CME single
configuration, see CME Single Configuration Operation Guide.
SN MO NE
1 a TRMMAP RNC
b ADJMAP RNC
2 a DIFPRI NodeB
b ULFLOWCTRLPA NodeB
RA
c DLFLOWCTRLPA NodeB
RA
Set parameters GSM and LTE on the CME according to the operation sequence described in
Table 7-14 and Table 7-16. For instructions on how to perform the CME single configuration,
see CME Single Configuration Operation Guide.
Step 2 Run the SET DIFPRI command to set the mapping between DSCP values and data from the
CP of a NodeB.
Step 3 Configure the dynamic flow control algorithm for the NodeB.
1. Run the ADD ULFLOWCTRLPARA command to add an HSUPA flow control
parameter to set the uplink bandwidth adaptive flow control switch.
2. Run the ADD DLFLOWCTRLPARA command to add an HSDPA flow control
parameter to set the HSDPA flow control switch.
----End
//Setting the mapping between DSCP values and data from the CP and UP on the Iub interface
ADD
TRMMAP:TMI=110,ITFT=IUB,TRANST=IP,CCHPRIPATH=EF,SIPPRIPATH=EF,SRBPRIPATH=EF,VOICEP
RIPATH=EF,CSCONVPRIPATH=AF41,CSSTRMPRIPATH=AF41,PSCONVPRIPATH=AF41,PSSTRMPRIPATH=A
F41,PSINTHGHPRIPATH=AF21,PSINTLOWPRIPATH=AF21,PSBKGPRIPATH=AF21,HDSRBPRIPATH=EF,HD
SIPPRIPATH=EF,HDVOICEPRIPATH=EF,HDCONVPRIPATH=AF41,HDSTRMPRIPATH=AF41,HDINTHGHPRIP
ATH=AF11,HDINTMIDPRIPATH=AF11,HDINTLOWPRIPATH=AF11,HDBKGPRIPATH=AF11,HUSRBPRIPATH=
EF,HUSIPPRIPATH=EF,HUVOICEPRIPATH=EF,HUCONVPRIPATH=AF41,HUSTRMPRIPATH=AF41,HUINTHG
HPRIPATH=AF11,HUINTMIDPRIPATH=AF11,HUINTLOWPRIPATH=AF11,HUBKGPRIPATH=AF11;
//Adding the mapping from the Iub interface to the TRMMAP index
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110,
TMIBRZ=110, FTI=1;
//Configuring the dynamic flow control algorithm for the NodeB (when the bearer network
supports two or more queues)
Step 1 Set parameters on the CME according to the operation sequence described in Table 7-18 and
Table 7-16. For instructions on how to perform the CME single configuration, see CME
Single Configuration Operation Guide.
SN MO NE
1 a TRMMAP RNC
b ADJMAP RNC
2 a DIFPRI NodeB
b ULFLOWCTRLPARA NodeB
c DLFLOWCTRLPARA NodeB
----End
----End
//For a GBTS, binding an IP logical port and a GBTS on the Abis interface
SET BTSIP: IDTYPE=BYID, BTSID=1, BTSCOMTYPE=LOGICIP, BTSIP="16.16.90.201",
BSCIP="172.16.140.140", CFGFLAG=IPLGCPORT, SN=24, LPN=1;
//In the preceding script, the base station is identified by its base station
index.
//For an eGBTS, binding an IP path and an IP logical port on the Abis interface if the peer end
is a BSC6900
ADD IPPATH: ANI=3, PATHID=0, ITFT=ABIS, ISEGBTS=Yes, PATHT=QoS,
IPADDR="172.16.140.140", PEERIPADDR="16.16.90.201", TXBW=10000, RXBW=10000,
CARRYFLAG=IPLGCPORT, LPNSN=0, LPN=1, VLANFLAG=DISABLE, PATHCHK=DISABLED,
AbisLnkBKFLAG=OFF;
//For an eGBTS, binding an adjacent node and an IP logical port on the Abis interface if the
peer end is a BSC6910
ADD ADJLOGICPORTBIND: ANI=3, SRN=1, SN=24, LPN=1;
//Setting the mapping between DSCP values and data from the CP on the Abis interface
SET BSCABISPRIMAP: IDTYPE=BYID, BTSID=1, TRANSTYPE=IP, OMLDSCP=48, RSLDSCP=48,
EMLDSCP=18, ESLDSCP=48;
//Adding the mapping from the Abis interface to the TRMMAP index
ADD ADJMAP: ANI=3, ITFT=ABIS, TMIGLD=111, FTI=1;
//Setting the mapping between DSCP values and data from the CP of an eGBTS
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;
Step 3 Configure a TRM table on the RNC side by referring to section 4.2.2 Transmission Resource
Management Strategies.
1. Run the ADD TRMMAP command to set the mapping between DSCP values and data
from the UP and CP on the Iub interface.
2. Run the ADD ADJMAP command to add the mapping from the Iub interface to the
TRMMAP index.
Step 4 Run the SET DIFPRI command to set the mapping between DSCP values and data from the
CP of a NodeB.
Step 5 Configure the dynamic flow control algorithm for the NodeB.
1. Run the ADD ULFLOWCTRLPARA command to add an HSUPA flow control
parameter to set the uplink bandwidth adaptive flow control switch.
2. Run the ADD DLFLOWCTRLPARA command to add an HSDPA flow control
parameter to set the HSDPA flow control switch.
Step 6 If the NodeB side of a separate-MPT multimode base station provides a co-transmission port
and co-transmission is implemented through panel interconnection, the traffic control switch
for a transmission resource group must be disabled on the co-transmission port. Otherwise,
when transmission resources become congested, passing data will preempt bandwidth from
the local data. This deteriorates user experience.
1. Run the ADD RSCGRP command to configure a default transport resource group on the
co-transmission port.
2. Run the SET RSCGRPALG command to disable the traffic control switch of the default
transport resource group you have configured.
----End
//Binding an IP path and an IP logical port if the transmission resource pool feature is not
implemented on the Iub interface
ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=QoS,
IPADDR="172.16.100.140", PEERIPADDR="16.16.70.201", TXBW=20000, RXBW=20000,
CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Binding an adjacent node and an IP logical port if the transmission resource pool feature is
implemented on the Iub interface
//Adding the mapping from the Iub interface to the TRMMAP index
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110,
TMIBRZ=110, FTI=1;
//Configuring the dynamic flow control algorithm for the NodeB (when the bearer network
supports two or more queues)
//Adding an HSUPA flow control parameter
ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0,
BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;
//Turning off the traffic control switch of the default transmission resource group configured
on the co-transmission port if the NodeB side of a separate-MPT multimode base station
provides a co-transmission port and co-transmission is implemented through panel
interconnection
//Configuring a default transmission resource group on the co-transmission port
ADD RSCGRP: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT, RU=KBPS;
//Disabling the traffic control switch on the default transmission resource group you have
configured
SET RSCGRPALG: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT,
TCSW=DISABLE;
----End
NOTE
If control-plane EPS optimized transmission is used, NB-IoT services are carried on SCTP links. No
configuration for the user-plane MO UDTPARAGRP is required. NB-IoT does not support the traffic
control switch for a transmission resource group.
If user-plane EPS optimized transmission is used for NB-IoT, NB-IoT does not support the traffic
control switch for a transmission resource group.
//Turning off the traffic control switch of the default transmission resource group configured
on the co-transmission port if the eNodeB side of a separate-MPT multimode base station
provides a co-transmission port and co-transmission is implemented through panel
interconnection. NB-IoT does not support the traffic control switch for a transmission
resource group.
//Configuring a default transmission resource group on the co-transmission port
//Disabling the traffic control switch on the default transmission resource group you have
configured
SET RSCGRPALG: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT,
TCSW=DISABLE;
Step 1 Set parameters GSM, UMTS, and LTE on the CME according to the operation sequence
described in Table 7-19, Table 7-20, and Table 7-21. For instructions on how to perform the
CME single configuration, see CME Single Configuration Operation Guide.
1 a IPLOGICPORT GBSC
b BTSIP/IPPATH/ADJLOGICPORTBIND GBSC
c TRMMAP GBSC
d BSCABISPRIMAP GBSC
e ADJMAP GBSC
4 a BTSVLAN/DIFPRI GBTS/eGBTS
1 a LR NodeB
2 a IPLOGICPORT RNC
b IPPATH/ADJLOGICPORTBIND RNC
c TRMMAP RNC
d ADJMAP RNC
3 a DIFPRI NodeB
b ULFLOWCTRLPARA NodeB
c DLFLOWCTRLPARA NodeB
d RSCGRP NodeB
e RSCGRPALG NodeB
1 a LR eNodeB
b DIFPRI eNodeB
c UDTPARAGRP eNodeB
d RSCGRP eNodeB
e RSCGRPALG eNodeB
----End
Step 3 Configure a TRM table on the RNC side by referring to section 4.2.2 Transmission Resource
Management Strategies.
1. Run the ADD TRMMAP command to set the mapping between DSCP values and data
from the UP and CP on the Iub interface.
2. Run the ADD ADJMAP command to add the mapping from the Iub interface to the
TRMMAP index.
Step 4 Run the SET DIFPRI command to set the mapping between DSCP values and data from the
CP of a NodeB.
Step 5 Configure the dynamic flow control algorithm for the NodeB.
1. Run the ADD ULFLOWCTRLPARA command to add an HSUPA flow control
parameter to set the uplink bandwidth adaptive flow control switch.
2. Run the ADD DLFLOWCTRLPARA command to add an HSDPA flow control
parameter to set the HSDPA flow control switch.
----End
//Binding an IP path and an IP logical port if the transmission resource pool feature is not
implemented on the Iub interface
ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=QoS,
IPADDR="172.16.100.140", PEERIPADDR="16.16.70.201", TXBW=20000, RXBW=20000,
CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Binding an adjacent node and an IP logical port if the transmission resource pool feature is
implemented on the Iub interface
ADD ADJLOGICPORTBIND: ANI=10, SRN=1, SN=26, LPN=1;
//Adding the mapping from the Iub interface to the TRMMAP index
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110,
TMIBRZ=110, FTI=1;
//Configuring the uplink bandwidth adaptive flow control switch and HSDPA flow control
switch on the NodeB side
1 a LR NodeB
2 a IPLOGICPORT RNC
b IPPATH/ADJLOGICPORTBIND RNC
c TRMMAP RNC
d ADJMAP RNC
3 a DIFPRI NodeB
b ULFLOWCTRLPARA NodeB
c DLFLOWCTRLPARA NodeB
Set parameters GSM and LTE on the CME according to the operation sequence described in
Table 7-19 and Table 7-21. For instructions on how to perform the CME single configuration,
see CME Single Configuration Operation Guide.
Step 3 Configure a TRM table on the RNC side by referring to 4.2.2 Transmission Resource
Management Strategies.
1. Run the ADD TRMMAP command to set the mapping between DSCP values and data
on the UP and CP of the Iub interface.
2. Run the ADD ADJMAP command to add the mapping from the Iub interface to the
TRMMAP index.
Step 4 Run the SET DIFPRI command to set the mapping between DSCP values and data on the CP
of a NodeB.
Step 5 Configure the dynamic flow control algorithm for the NodeB.
1. Run the ADD ULFLOWCTRLPARA command to add an HSUPA bandwidth adaptive
flow control switch.
2. Run the ADD DLFLOWCTRLPARA command to add an HSDPA flow control switch.
Step 6 If the NodeB side of a separate-MPT multimode base station provides a co-transmission port
and co-transmission is implemented through panel interconnection, the traffic control switch
for a transmission resource group must be disabled on the co-transmission port. Otherwise,
when transmission resources become congested, passerby data will preempt bandwidth from
the local data. This deteriorates user experience.
1. Run the ADD RSCGRP command to configure a default transmission resource group on
the co-transmission port.
2. Run the SET RSCGRPALG command to disable the traffic control switch of the default
transmission resource group you have configured.
----End
//Binding an IP path and an IP logical port if the transmission resource pool feature is not
implemented on the Iub interface
ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=QoS,
IPADDR="172.16.100.140", PEERIPADDR="16.16.70.201", TXBW=20000, RXBW=20000,
CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Binding an adjacent node and an IP logical port if the transmission resource pool feature is
implemented on the Iub interface
ADD ADJLOGICPORTBIND: ANI=10, SRN=1, SN=26, LPN=1;
//Adding the mapping from the Iub interface to the TRMMAP index
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110,
TMIBRZ=110, FTI=1;
//Configuring the dynamic flow control algorithm for the NodeB (when the bearer network
supports two or more queues)
//Adding an HSUPA flow control parameter
Turn off the traffic control switch of the default transmission resource group configured on
the co-transmission port if the NodeB side of a separate-MPT multimode base station
provides a co-transmission port and co-transmission is implemented through panel
interconnection.
//Turning off the traffic control switch on the default transmission resource group you have
configured
SET RSCGRPALG: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=DEFAULTPORT,
TCSW=DISABLE;
Step 1 Set UMTS and LTE parameters on the CME according to the operation sequence described in
Table 7-23 and Table 7-21. For instructions on how to perform the CME single configuration,
see CME Single Configuration Operation Guide.
1 a LR NodeB
SN MO NE
2 a IPLOGICPORT RNC
b IPPATH/ADJLOGICPORTBIND RNC
c TRMMAP RNC
d ADJMAP RNC
3 a DIFPRI NodeB
b ULFLOWCTRLPARA NodeB
c DLFLOWCTRLPARA NodeB
d RSCGRP NodeB
e RSCGRPALG NodeB
----End
7.4.5.9 Access Bandwidth Limited for Each Operator in a UL/UT Dual-Mode Base
Station in RAN Sharing Scenarios
Step 2 Bind a user-plane link for transmitting local data and the configured transport resource group
on the base station side.
l Link mode:
a. Run the ADD IPPATH command to add an IP path and bind this IP path and the
configured transmission resource group.
b. Run the ADD NODEBPATH command to bind a NodeB and the added IP path.
l End-point mode:
a. Run the ADD EPGROUP command to add an end point group on the NodeB side.
b. Run the ADD USERPLANEHOST command to add a user-plane host on the NodeB
side.
c. Run the ADD USERPLANEPEER command to add a user-plane peer on the NodeB
side.
d. Run the ADD UPHOST2EPGRP command to bind the added user-plane host and the
added end point group on the NodeB side.
e. Run the ADD UPPEER2EPGRP command to bind the added user-plane peer and the
added end point group on the NodeB side.
f. Run the ADD EP2RSCGRP command to bind the added end point group and the
configured transmission resource group.
1. Run the ADD IP2RSCGRP command to bind a user-plane link for transmitting passing
data and a transmission resource group on the NodeB side.
Step 3 Configure logical ports on the RNC side.
1. Run the ADD IPLOGICPORT command to add an IP logical port on the Iub interface.
2. Run the ADD IPPATH command to bind a user-plane link and an IP logical port on the
Iub interface on the base station controller side.
Step 4 Configure a TRM table on the RNC side by referring to section 4.2.2 Transmission Resource
Management Strategies.
1. Run the ADD TRMMAP command to set the mapping between DSCP values and data
from the UP and CP on the Iub interface.
2. Run the ADD ADJMAP command to add the mapping from the Iub interface to the
TRMMAP index.
Step 5 Run the SET DIFPRI command to set the mapping between DSCP values and data from the
CP of a NodeB.
Step 6 Configure the dynamic flow control algorithm for the NodeB.
1. Run the ADD ULFLOWCTRLPARA command to add an HSUPA flow control
parameter to set the uplink bandwidth adaptive flow control switch.
2. Run the ADD DLFLOWCTRLPARA command to add an HSDPA flow control
parameter to set the HSDPA flow control switch.
Step 7 Turn off the traffic control switch of the default transmission resource group configured on
the co-transmission port.
If the NodeB side of a separate-MPT multimode base station provides a co-transmission port
and co-transmission is implemented through panel interconnection, the traffic control switch
for a transmission resource group must be disabled on the co-transmission port. Otherwise,
when transmission resources become congested, passing data will preempt bandwidth from
the local data. This deteriorates user experience.
Run the SET RSCGRPALG command to turn off the traffic control switch of the default
transmission resource group you have configured.
----End
//Link mode
//End-point mode
//Binding an end point group and the configured transport resource group
ADD EPGROUP: EPGROUPID=0;
ADD EPGROUP: EPGROUPID=1;
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="16.16.70.201";
ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="16.16.60.201";
ADD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, PEERIPV4="172.16.90.140";
ADD USERPLANEPEER: UPPEERID=1, IPVERSION=IPv4, PEERIPV4="172.16.80.140";
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;
ADD UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1;
ADD UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0;
ADD UPPEER2EPGRP: EPGROUPID=1, UPPEERID=1;
ADD EP2RSCGRP: ENDPOINTID=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1;
ADD EP2RSCGRP: ENDPOINTID=1, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2;
//Binding the passing data and the configured transmission resource group
ADD IP2RSCGRP: MAPIDX=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1,
DSTIP="172.15.90.140", DSTMASK="255.255.255.255";
ADD IP2RSCGRP: MAPIDX=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2,
DSTIP="172.15.80.140", DSTMASK="255.255.255.255";
//Binding an IP path and the logical port you have added on the Iub interface
ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=QoS,
IPADDR="172.16.90.140", PEERIPADDR="16.16.70.201", TXBW=10000, RXBW=10000,
CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;
ADD IPPATH: ANI=10, PATHID=2, ITFT=IUB, TRANST=IP, PATHT=QoS,
IPADDR="172.16.80.140", PEERIPADDR="16.16.60.201", TXBW=10000, RXBW=10000,
CARRYFLAG=NULL, VLANFlAG=DISABLE, PATHCHK=DISABLED;
//Adding the mapping from the Iub interface to the TRMMAP index
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110,
TMIBRZ=110, FTI=1;
//Configuring the dynamic flow control algorithm for the NodeB (when the bearer network
supports two or more queues)
//Adding an HSUPA flow control parameter
ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0,
BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;
//Adding an HSDPA flow control parameter in the case of a separate-MPT multimode base
station
ADD DLFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0,
SWITCH=BW_SHAPING_ONOFF_TOGGLE, FAIRSWITCH=ON;
//Adding an HSDPA flow control parameter in the case of a co-MPT multimode base station
ADD DLFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0,
SWITCH=BW_SHAPING_ONOFF_TOGGLE, FAIRSWITCH=ON;
//Turning off the traffic control switch of the default transmission resource group configured
on the co-transmission port in a separate-MPT multimode base station where co-transmission
is implemented through panel interconnection
//Configuring a default transmission resource group on the co-transmission port
SET RSCGRPALG: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1, TCSW=DISABLE;
SET RSCGRPALG: SN=6, BEAR=IP, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2, TCSW=DISABLE;
Step 2 Configure a TRM table on the eNodeB side. If the control plane CIoT EPS optimization
function is implemented between the NB-IoT eNodeB and EPC, no user-plane data
configuration is required.
1. Run the SET DIFPRI command to set the mapping between DSCP values and control-
plane data of an eNodeB.
2. Run the MOD UDTPARAGRP command to set the mapping between DSCP values and
user-plane data of an eNodeB.
Step 3 Turn off the traffic control switch of the default transmission resource group configured on
the co-transmission port.
If the eNodeB side of a separate-MPT multimode base station provides a co-transmission port
and co-transmission is implemented through panel interconnection, the traffic control switch
for a transmission resource group must be disabled on the co-transmission port. Otherwise,
when transmission resources become congested, passerby data will preempt bandwidth from
the local data. This deteriorates user experience.
Run the SET RSCGRPALG command to turn off the traffic control switch of the default
transmission resource group you have configured. NB-IoT does not support the traffic control
switch for a transmission resource group.
----End
//Configuring traffic limiting and shaping if the eNodeB side of a separate-MPT multimode
base station provides a co-transmission port
//Link mode
//Binding an IP path to the configured transmission resource group. If the control plane CIoT
EPS optimization function is implemented between the NB-IoT eNodeB and EPC, no user-
plane data configuration is required.
ADD IPPATH: PATHID=1, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=1,
LOCALIP="16.15.70.201", PEERIP="172.15.90.140", PATHTYPE=ANY;
ADD ENODEBPATH: IpPathId=1, AppType=S1, S1InterfaceId=0;
ADD IPPATH: PATHID=2, SN=6, SBT=BASE_BOARD, PT=ETH, JNRSCGRP=ENABLE, RSCGRPID=2,
LOCALIP="16.15.60.201", PEERIP="172.15.80.140", PATHTYPE=ANY;
ADD ENODEBPATH: IpPathId=2, AppType=S1, S1InterfaceId=0;
//End-point mode
//Binding an end point group and the configured transmission resource group. If the control
plane CIoT EPS optimization function is implemented between the NB-IoT eNodeB and
EPC, no user-plane data configuration is required.
ADD EPGROUP: EPGROUPID=0;
ADD EPGROUP: EPGROUPID=1;
ADD USERPLANEHOST: UPHOSTID=0, IPVERSION=IPv4, LOCIPV4="16.15.70.201";
ADD USERPLANEHOST: UPHOSTID=1, IPVERSION=IPv4, LOCIPV4="16.15.60.201";
ADD USERPLANEPEER: UPPEERID=0, IPVERSION=IPv4, PEERIPV4="172.15.90.140";
ADD USERPLANEPEER: UPPEERID=1, IPVERSION=IPv4, PEERIPV4="172.15.80.140";
ADD UPHOST2EPGRP: EPGROUPID=0, UPHOSTID=0;
ADD UPHOST2EPGRP: EPGROUPID=1, UPHOSTID=1;
ADD UPPEER2EPGRP: EPGROUPID=0, UPPEERID=0;
ADD UPPEER2EPGRP: EPGROUPID=1, UPPEERID=1;
ADD EP2RSCGRP: ENDPOINTID=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1;
ADD EP2RSCGRP: ENDPOINTID=1, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2;
//Binding the passing data and the configured transmission resource group
ADD IP2RSCGRP: MAPIDX=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=1,
DSTIP="172.16.90.140", DSTMASK="255.255.255.255";
ADD IP2RSCGRP: MAPIDX=0, SN=6, SBT=BASE_BOARD, PT=ETH, RSCGRPID=2,
DSTIP="172.16.80.140", DSTMASK="255.255.255.255";
//Setting the mapping between DSCP values and data from the CP of an eNodeB
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMHIGHPRI=46, OMLOWPRI=18, IPCLKPRI=46;
//Setting the mapping between DSCP values and data from the UP of an eNodeB
MOD UDTPARAGRP: UDTPARAGRPID=40, PRIRULE=DSCP, PRI=46, ACTFACTOR=100;
MOD UDTPARAGRP: UDTPARAGRPID=41, PRIRULE=DSCP, PRI=26, ACTFACTOR=100;
MOD UDTPARAGRP: UDTPARAGRPID=42, PRIRULE=DSCP, PRI=34, ACTFACTOR=100;
MOD UDTPARAGRP: UDTPARAGRPID=43, PRIRULE=DSCP, PRI=26, ACTFACTOR=100;
MOD UDTPARAGRP: UDTPARAGRPID=44, PRI=46;
MOD UDTPARAGRP: UDTPARAGRPID=45, PRI=18;
MOD UDTPARAGRP: UDTPARAGRPID=46, PRI=18;
MOD UDTPARAGRP: UDTPARAGRPID=47, PRI=18;
MOD UDTPARAGRP: UDTPARAGRPID=48, PRI=0;
//Turning off the traffic control switch of the default transmission resource group configured
on the co-transmission port if the eNodeB side of a separate-MPT multimode base station
provides a co-transmission port. NB-IoT does not support the traffic control switch for a
transmission resource group.
Step 1 Set UMTS and LTE parameters on the CME according to the operation sequence described in
Table 7-24 and Table 7-25. For instructions on how to perform the CME single configuration,
see CME Single Configuration Operation Guide.
1 a RSCGRP NodeB
b IPPATH NodeB
c NODEBPATH NodeB
d IP2RSCGRP NodeB
2 a IPLOGICPORT RNC
b IPPATH/ADJLOGICPORTBIND RNC
c TRMMAP RNC
d ADJMAP RNC
3 a DIFPRI NodeB
b ULFLOWCTRLPARA NodeB
c DLFLOWCTRLPARA NodeB
d RSCGRPALG NodeB
1 a RSCGRP eNodeB
b IPPATH eNodeB
c ENODEBPATH eNodeB
d IP2RSCGRP eNodeB
2 a DIFPRI eNodeB
b UDTPARAGRP eNodeB
c RSCGRPALG eNodeB
----End
----End
//Configuring traffic limiting and shaping if the NodeB side of a separate-MPT multimode
base station provides a co-transmission port
SET LR: CN=0, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, LRSW=ENABLE, CIR=4000,
CBS=8000, EBS=0;
//Binding an IP path to an IP logical port if the transmission resource pool feature is not
implemented on the Iub interface
ADD IPPATH: ANI=10, PATHID=1, ITFT=IUB, TRANST=IP, PATHT=QoS,
IPADDR="172.16.100.140", PEERIPADDR="16.16.70.201", TXBW=3000, RXBW=3000,
CARRYFLAG=IPLGCPORT, LPNSN=0, LPN=1, PATHCHK=DISABLED;
//Binding an adjacent node to an IP logical port if the transmission resource pool feature is
implemented on the Iub interface
ADD ADJLOGICPORTBIND: ANI=10, SRN=1, SN=26, LPN=1;
//Adding the mapping from the Iub interface to the TRMMAP index
ADD ADJMAP: ANI=10, ITFT=IUB, TRANST=IP, CNMNGMODE=SHARE, TMIGLD=110, TMISLV=110,
TMIBRZ=110, FTI=1;
//Configuring the uplink bandwidth adaptive flow control switch and HSDPA flow control
switch on the NodeB side
//Adding an HSUPA flow control parameter
ADD ULFLOWCTRLPARA: CN=0, SRN=0, SN=7, SBT=BASE_BOARD, BEAR=IP, PT=ETH, PN=0,
BWPRTSWITCH=ON, TNLCONGCTRLSWITCH=ON;
Step 1 Set GSM and UMTS parameters on the CME according to the operation sequence described
in Table 7-19 and Table 7-26. For instructions on how to perform the CME single
configuration, see CME Single Configuration Operation Guide.
1 a LR NodeB
2 a IPLOGICPORT RNC
c SCTPLNK RNC
d TRMMAP RNC
e ADJMAP RNC
3 a DIFPRI NodeB
b ULFLOWCTRLPARA NodeB
c DLFLOWCTRLPARA NodeB
----End
Perform the following steps to determine whether this feature has been activated:
For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace.
For MAC tracing: Choose Trace > Common Services > MAC Trace.
l If the eNodeB provides a co-transmission port, start IP or MAC tracing on the eNodeB
LMT.
For IP tracing: Choose Trace > Common Services > IP Layer Protocol Trace.
For MAC tracing: Choose Trace > Common Services > MAC Trace.
Step 2 For IP tracing: In the displayed IP Layer Protocol Trace dialog box, specify Local IP
Address and Peer IP Address of the packets to be traced.
For MAC tracing: In the displayed MAC Trace dialog box, specify Local MAC Address and
Peer MAC Address of the packets to be traced.
Step 3 Use the TrafficReview tool to check the TOS (type of service) field in the Layer 3 IP packet
header or the VLAN Priority field in the Layer 2 IP packet header. The first six bits in the
TOS field indicate the DSCP value of a packet. If the calculated DSCP values or VLAN
priorities are the same as DSCP values or VLAN priorities planned, this feature has been
activated.
----End
Step 1 Run the LST RSCGRP command on the base station that provides the co-transmission port
to check whether a transport resource group has been configured for the co-transmission port.
If not, go to method 2.
Step 2 Initiate a UMTS or LTE PS service and set the maximum data rate to a value greater than the
CIR to simulate transmission resource congestion.
Step 3 Query the value of the VS.RscGroup.TxFlowOverloadTime counter for the co-transmission
port. If the value is greater than 0, this feature has been activated.
----End
If you need to check whether the configured service priority has taken effect, perform the
following steps to check whether the feature has been activated:
l The eGBTS side of a multimode base station provides a co-transmission port.
Step 1 Initiate a UMTS or LTE PS service and set the maximum data rate higher than the CIR value
to simulate transmission resource congestion.
Step 2 Start transport link flux monitoring on the eGBTS LMT. Choose Monitor > Realtime
Performance Monitoring > Transport Link Flux Monitoring.
Step 3 Initiate a GSM or UMTS CS service if the traffic flux approaches the bandwidth available for
the bearer network.
Step 4 Terminate the CS service if the call is successfully set up and the voice is clear and constant.
Step 5 Initiate a GSM PS service, connect a personal computer (PC) to the multimode base station,
and use the DU Meter on the PC to check whether the GSM PS service is successfully set up
and the data rate is stable.
----End
l The NodeB side of a multimode base station provides a co-transmission port.
Step 1 Initiate a UMTS PS service and set the maximum data rate higher than the CIR value to
simulate transmission resource congestion.
Step 2 Start transport link flux monitoring on the NodeB LMT. Choose Monitor > Realtime
Performance Monitoring > Transport Link Flux Monitoring.
Step 3 Initiate a GSM or UMTS CS service if the traffic flux approaches the bandwidth available for
the bearer network.
Step 4 Terminate the CS service if the call is successfully set up and the voice is clear and constant.
Step 5 Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meter
on the PC to check whether the GSM PS service is successfully set up and the data rate is
stable.
l If yes, this feature has been activated.
l If no, this feature has not been activated.
NOTE
Step 5 is performed only in a separate-MPT GU dual-mode base station or a separate-MPT GUL triple-
mode base station.
----End
Step 1 Initiate an LTE PS service and set the maximum data rate higher than the CIR value to
simulate transmission resource congestion.
Step 2 Start transport link flux monitoring on the eNodeB LMT. Choose Monitor > Realtime
Performance Monitoring > Transport Link Flux Monitoring.
Step 3 Initiate a GSM or UMTS CS service if the traffic flux approaches the bandwidth available for
the bearer network.
Step 4 Terminate the CS service if the call is successfully set up and the voice is clear and constant.
Initiate a GSM PS service, connect a PC to the multimode base station, and use the DU Meter
on the PC to check whether the GSM PS service is successfully set up and the data rate is
stable.
l If yes, this feature has been activated.
l If no, this feature has not been activated.
NOTE
Step 4 is performed only in a separate-MPT GL dual-mode base station or a separate-MPT GUL triple-
mode base station.
----End
7.4.6.3 Limited Access Bandwidth for Each Operator in RAN Sharing Scenarios
If you do not need to check whether the configured service priority has taken effect, perform
the following steps to check whether the feature has been activated:
Step 1 Run the LST RSCGRP command on the base station that provides the co-transmission port
to check whether a transport resource group has been configured for the co-transmission port.
If not, go to method 2.
Step 2 Initiate a UMTS or LTE PS service for an operator and set the maximum data rate to a value
greater than the TXBW value to simulate transmission resource congestion.
Step 3 Query the value of the VS.RscGroup.TxFlowOverloadTime counter for the co-transmission
port. If the value is greater than 0, this feature has been activated.
----End
If you need to check whether the configured service priority has taken effect, perform the
following steps to check whether the feature has been activated:
Step 1 Initiate a UMTS or LTE PS service for operator A and set the maximum data rate higher than
the TXBW value to simulate transmission resource congestion.
Step 2 Start transport link flux monitoring on the LMT.
l If the NodeB side of a separate-MPT multimode base station provides a co-transmission
port, start transport link flux monitoring on the NodeB LMT. Choose Monitor >
Realtime Performance Monitoring > Transport Link Flux Monitoring.
l If the eNodeB side of a separate-MPT multimode base station provides a co-transmission
port, start transport link flux monitoring on the eNodeB LMT. Choose Monitor >
Realtime Performance Monitoring > Transport Link Flux Monitoring.
Step 3 Initiate a UMTS CS service for operator A if the traffic flux approaches the bandwidth
available for the bearer network. Terminate the CS service if the call is successfully set up and
the voice is clear and constant.
Step 4 Perform the first three steps to verify services of other operators.
----End
8 Parameters
CIR BTS390 SET LR WRFD- HSDPA Meaning: Indicates the UL committed information
0, LST LR 0106101 Flow rate after rate limitation is configured at a port. The
BTS390 0 Control precision of the UL committed information rate
0 supported by the UMPTa, UMPTb, UMPTe, UMDU
WCDM or GTMUc is 64 kbit/s, the precision supported by the
A, other board is 32 kbit/s. If the configured UL
BTS390 committed information rate is not a multiple of the
0 LTE, precision, the UL committed information rate is
BTS590 rounded up. For the GTMUb, the value of CIR ranges
0, from 64 to 100000. If this parameter is set to a value
BTS590 greater than the maximum allowed value or less than
0 the minimum allowed value, the maximum or the
WCDM minimum allowed value takes effect.
A, GUI Value Range: 32~40000000
BTS590
0 LTE Unit: kbit/s
Actual Value Range: 32~40000000
Default Value: None
TXBW BTS390 ADD WRFD- Transmi Meaning: Indicates the maximum uplink bandwidth of
0, RSCGR 0213040 ssion a transmission resource group at the MAC layer when
BTS390 P 6 Recours the transmission resource group is carried over IP.
0 MOD e This parameter value is used as the uplink transport
WCDM RSCGR Sharing admission bandwidth and TX traffic shaping
A, P on bandwidth. The minimum rate supported by the
BTS390 Iub/Iur UMPTa, UMPTb, UMPTe, UMDU, GTMUb or
0 LTE, DSP Interface GTMUc is 64 kbit/s. The LMPT can be configured
BTS590 RSCGR with a maximum of 360 Mbit/s TX bandwidth. The
0, P WMPT, GTMUb or GTMUc can be configured with a
BTS590 LST maximum of 300 Mbit/s TX bandwidth. The UMPTa,
0 RSCGR UMPTb, UMDU or UTRPc can be configured with a
WCDM P maximum of 1 Gbit/s TX bandwidth. The UMPTe or
A, UCCU can be configured with a maximum of 10
BTS590 Gbit/s TX bandwidth. The UBBPe, UBBPei,
0 LTE UBBPep, UBBPem, UBBPex2 or LCOP can be
configured with a maximum of 40 Gbit/s TX
bandwidth. If the parameter is set to a value greater
than the maximum TX bandwidth supported by a
board, the maximum TX bandwidth supported by the
board takes effect. For a WMPT and a UTRP
(excluding UTRPa), this parameter does not specify
the TX traffic shaping bandwidth of the transmission
resource group that is carried on the PPP link.
GUI Value Range: 32~40000000
Unit: None
Actual Value Range: 32~40000000
Default Value: None
CIR BSC690 ADD WRFD- Overboo Meaning: Bandwidth of the logical port
0 IPLOGI 050408 king on GUI Value Range: 1~1562
CPORT WRFD- IP
Transmi Unit: 64kbit/s
MOD 140208
IPLOGI ssion Actual Value Range: 64~64000(FG2a/GOUa/
WRFD- UOIa(IP)), 256~99968(FG2c/FG2e/GOUc/POUc(IP)/
CPORT 021311 Iub
Transmi PEUc(IP)/GOUe)
WRFD- ssion Default Value: None
140207 Resourc
e Pool in
RNC
MOCN
Introduc
tion
Package
Iu/Iur
Transmi
ssion
Resourc
e Pool in
RNC
CIR BSC691 ADD WRFD- Overboo Meaning: Bandwidth of the logical port.
0 IPLOGI 050408 king on GUI Value Range: 4~1562
CPORT IP
Transmi Unit: 64kbit/s
MOD
IPLOGI ssion Actual Value Range: 256~99968
CPORT Default Value: None
TNLCO BTS390 ADD None None Meaning: Indicates whether to perform congestion
NGCTR 0, ULFLO control. When this switch is turned on, the BS lowers
LSWIT BTS390 WCTRL the TX rate if the BS detects that links experience
CH 0 PARA transmission delay or packet loss.
WCDM SET GUI Value Range: OFF(Off), ON(On)
A, ULFLO
BTS590 Unit: None
WCTRL
0, PARA Actual Value Range: OFF, ON
BTS590 Default Value: ON(On)
0 DSP
WCDM ULFLO
A WCTRL
PARA
LST
ULFLO
WCTRL
PARA
SWITC BTS390 ADD WRFD- HSDPA Meaning: Indicates the switch for the DL flow control
H 0, DLFLO 0106101 Flow algorithm. If this parameter is set to
BTS390 WCTRL 0 Control STATIC_BW_SHAPING, the available HSDPA
0 PARA bandwidth equals the total bandwidth minus the R99
WCDM SET bandwidth. If this parameter is set to
A, DLFLO DYNAMIC_BW_SHAPING, flow allocation for
BTS590 WCTRL HSDPA users is performed according to the delay and
0, PARA packet loss of the transmission interface board in
BTS590 STATIC_BW_SHAPING mode. This function
0 DSP requires the network controller using the 3GPP R6
WCDM DLFLO protocol. Therefore, you are advised to use this
A WCTRL function with the RNC that complies with the 3GPP
PARA R6 protocol. If this parameter is set to
LST NO_BW_SHAPING, the BS does not allocate
DLFLO bandwidth according to the configuration and delay of
WCTRL the transmission interface board. The BS reports the
PARA air interface conditions to the controller, and then the
controller allocates bandwidth. When this parameter is
set to NO_BW_SHAPING, the backpressure function
must be enabled on the controller side. If this
parameter is set to
BW_SHAPING_ONOFF_TOGGLE, the BS
automatically selects either
DYNAMIC_BW_SHAPING or NO_BW_SHAPING
during a flow congestion detection on a port. That is,
DYNAMIC_BW_SHAPING is selected if congestion
is detected; NO_BW_SHAPING is selected if
congestion is not detected for a certain period of time.
GUI Value Range:
STATIC_BW_SHAPING(STATIC_BW_SHAPING),
DYNAMIC_BW_SHAPING(DYNAMIC_BW_SHA
PING), NO_BW_SHAPING(NO_BW_SHAPING),
BW_SHAPING_ONOFF_TOGGLE(BW_SHAPING
_ONOFF_TOGGLE)
Unit: None
Actual Value Range: STATIC_BW_SHAPING,
DYNAMIC_BW_SHAPING, NO_BW_SHAPING,
BW_SHAPING_ONOFF_TOGGLE
Default Value:
BW_SHAPING_ONOFF_TOGGLE(BW_SHAPING
_ONOFF_TOGGLE)
FAIRS BTS390 ADD WRFD- HSDPA Meaning: Indicates the switch controlling downlink
WITCH 0, DLFLO 0106101 Flow fairness flow. If multiple modes share transmission
BTS390 WCTRL 0 Control bandwidth and congestion occurs, the UMTS data rate
0 PARA may decrease due to downlink flow control and the
WCDM SET LTE data rate may increase due to bandwidth
A, DLFLO preemption when the Flow Control Switch parameter
BTS590 WCTRL is set to DYNAMIC_BW_SHAPING or is set to
0, PARA BW_SHAPING_ONOFF_TOGGLE but actually
BTS590 takes effect using the DYNAMIC_BW_SHAPING
0 DSP value. When this switch is turned on, the system
WCDM DLFLO guarantees the minimum downlink transmission
A WCTRL bandwidth of the UMTS mode. This switch applies
PARA only to Ethernet ports, Ethernet trunks, and loop
LST interfaces with Port Type set to ETH or ETHTRK.
DLFLO GUI Value Range: OFF(Off), ON(On)
WCTRL
PARA Unit: None
Actual Value Range: OFF, ON
Default Value: OFF(Off)
FAIRR BTS390 ADD WRFD- HSDPA Meaning: Indicates the minimum protection ratio of
ATIO 0, DLFLO 0106101 Flow downlink fairness flow control. When the fairness
BTS390 WCTRL 0 Control flow control switch is turned on and unfairness flow
0 PARA control is performed, the system guarantees the
WCDM SET minimum UMTS transmission bandwidth based on
A, DLFLO the value of this parameter.
BTS590 WCTRL GUI Value Range: 0~100
0, PARA
BTS590 Unit: %
0 DSP Actual Value Range: 0~100
WCDM DLFLO
WCTRL Default Value: 30
A
PARA
LST
DLFLO
WCTRL
PARA
RSCGR BTS390 ADD WRFD- Transmi Meaning: Indicates the ID of a transmission resource
PID 0, RSCGR 0213040 ssion group. When you use an MML command to add a PPP
BTS390 P 6 Recours link, an MP group, an Ethernet port, an Ethernet trunk,
0 DSP e a tunnel, or a PPPoE link, the system automatically
WCDM RSCGR Sharing creates a transmission resource group with
A, P on Transmission Resource Group ID set to
BTS390 Iub/Iur DEFAULTPORT(Default Port). When you remove
0 LTE, MOD Interface any of the preceding objects, the system automatically
BTS590 RSCGR removes the transmission resource group. When you
0, P add a PPP link, an MP group, an Ethernet port, an
BTS590 RMV Ethernet trunk, or an uplink tunnel on the CME, if the
0 RSCGR default transmission resource group does not exist, the
WCDM P system automatically creates a transmission resource
A, LST group with Transmission Resource Group ID set to
BTS590 RSCGR AUTOPORT(Autoport Port). When you remove any
0 LTE P of the preceding objects, the system automatically
removes the transmission resource group.
GUI Value Range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12,
13, 14, 15, AUTOPORT(Auto Port),
DEFAULTPORT(Default Port)
Unit: None
Actual Value Range: 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11,
12, 13, 14, 15, AUTOPORT, DEFAULTPORT
Default Value: None
TUNNE BTS390 ADD MRFD- IP- Meaning: Indicates the type of the tunnel.
LTYPE 0, TUNNE 121124 Based GUI Value Range: UL(UL), DL(DL)
BTS390 L Multi-
0 mode Unit: None
MOD
WCDM TUNNE Co- Actual Value Range: UL, DL
A, L Transmi Default Value: UL(UL)
BTS390 ssion on
0 LTE, LST BS
BTS590 TUNNE side(No
0, L deB)
BTS590
0
WCDM
A,
BTS590
0 LTE
CBS BTS390 SET LR WRFD- IP Meaning: Indicates the Committed Burst Size (CBS)
0, LST LR 050402 Transmi after rate limitation is configured at a port. The
BTS390 ssion minimum rate supported by the UMPTa, UMPTb,
0 Introduc UMPTe, UMDU or GTMUc is 64 kbit/s. For the
WCDM tion on GTMUb, the value of CBS ranges from 63 kbit to 256
A, Iub kbit. If this parameter is set to a value greater than the
BTS390 Interface maximum allowed value or less than the minimum
0 LTE, allowed value, the maximum or the minimum allowed
BTS590 value takes effect.
0, GUI Value Range: 32~40000000
BTS590
0 Unit: kbit
WCDM Actual Value Range: 32~40000000
A, Default Value: None
BTS590
0 LTE
EBS BTS390 SET LR WRFD- IP Meaning: Indicates the Excess Burst Size (EBS) after
0, LST LR 050402 Transmi rate limitation is configured at a port.
BTS390 ssion GUI Value Range: 0~40000000
0 Introduc
WCDM tion on Unit: kbit
A, Iub Actual Value Range: 0~40000000
BTS390 Interface Default Value: None
0 LTE,
BTS590
0,
BTS590
0
WCDM
A,
BTS590
0 LTE
TXCBS BTS390 ADD WRFD- Transmi Meaning: Indicates the TX committed burst size of a
0, RSCGR 0213040 ssion transmission resource group. The LMPT can be
BTS390 P 6 Recours configured with a maximum of 400 Mbit/s TX
0 MOD e committed burst size. The WMPT can be configured
WCDM RSCGR Sharing with a maximum of 600 Mbit/s TX committed burst
A, P on size. The WMPT, GTMUb or GTMUc can be
BTS390 Iub/Iur configured with a maximum of 600 Mbit/s TX
0 LTE, LST Interface committed burst size. The UMPTa, UMPTb, UMDU
BTS590 RSCGR or UTRPc can be configured with a maximum of 1
0, P Gbit/s TX committed burst size. The UMPTe or
BTS590 UCCU can be configured with a maximum of 10
0 Gbit/s TX committed burst size. The UBBPe,
WCDM UBBPei, UBBPep, UBBPem, UBBPex2 or LCOP can
A, be configured with a maximum of 40 Gbit/s TX
BTS590 committed burst size. The value of TX committed
0 LTE burst size is set to the maximum value of TX
committed burst size supported by the board when it
bigger than the maximum one.
GUI Value Range: 64~40000000
Unit: kbit
Actual Value Range: 64~40000000
Default Value: 64
TXEBS BTS390 ADD WRFD- Transmi Meaning: Indicates the TX excessive burst size of a
0, RSCGR 0213040 ssion transmission resource group. The LMPT can be
BTS390 P 6 Recours configured with a maximum of 450 Mbit/s TX
0 MOD e excessive burst size. The WMPT, GTMUb or GTMUc
WCDM RSCGR Sharing can be configured with a maximum of 600 Mbit/s TX
A, P on excessive burst size. The UMPTa, UMPTb, UMDU or
BTS390 Iub/Iur UTRPc can be configured with a maximum of 1
0 LTE, LST Interface Gbit/s TX excessive burst size. The UMTPe or UCCU
BTS590 RSCGR can be configured with a maximum of 10 Gbit/s TX
0, P excessive burst size. The UBBPe, UBBPei, UBBPep,
BTS590 UBBPem, UBBPex2 or LCOP can be configured with
0 a maximum of 40 Gbit/s TX excessive burst size. The
WCDM value of TX excessive burst size is set to the
A, maximum value of TX excessive burst size supported
BTS590 by the board when it bigger than the maximum one.
0 LTE GUI Value Range: 64~40000000
Unit: kbit
Actual Value Range: 64~40000000
Default Value: 1000000
LPN BSC690 ADD WRFD- Iub Meaning: Logical port number. It is uniquely
0 IPLOGI 140208 Transmi numbered within the active/standby boards.
CPORT WRFD- ssion GUI Value Range: 0~1535
MOD 140207 Resourc
e Pool in Unit: None
IPLOGI
CPORT RNC Actual Value Range: 0~119(FG2a/GOUa/UOIa(IP));
Iu/Iur 0~489, 512~767(FG2c/FG2e); 0~499,
RMV 512~767(GOUc/GOUe); 0~988,
IPLOGI Transmi
ssion 1024~1535(POUc(IP)); 0~127, 1024~1087(PEUc(IP))
CPORT
Resourc Default Value: None
e Pool in
RNC
PRIRUL BTS390 SET WRFD- IP Meaning: Indicates the rule for prioritizing traffic. If
E 0, DIFPRI 050402 Transmi this parameter is set to IPPRECEDENCE, the protocol
BTS390 LST ssion stack of the earlier version is adopted and the base
0 DIFPRI Introduc station converts TOSs to DSCPs and then prioritizes
WCDM tion on traffic.
A, Iub GUI Value Range: IPPRECEDENCE(IP Precedence),
BTS390 Interface DSCP(DSCP)
0 LTE,
BTS590 Unit: None
0, Actual Value Range: IPPRECEDENCE, DSCP
BTS590 Default Value: DSCP(DSCP)
0
WCDM
A,
BTS590
0 LTE
SIGPRI BTS390 SET WRFD- IP Meaning: Indicates the priority of signaling. The
0, DIFPRI 050402 Transmi priority has a positive correlation with the value of
BTS390 LST ssion this parameter.
0 DIFPRI Introduc GUI Value Range: 0~63
WCDM tion on
A, Iub Unit: None
BTS390 Interface Actual Value Range: 0~63
0 LTE, Default Value: 48
BTS590
0,
BTS590
0
WCDM
A,
BTS590
0 LTE
OMHIG BTS390 SET WRFD- IP Meaning: Indicates the priority of the high-level OM
HPRI 0, DIFPRI 050402 Transmi data. The priority has a positive correlation with the
BTS390 LST ssion value of this parameter.
0 DIFPRI Introduc GUI Value Range: 0~63
WCDM tion on
A, Iub Unit: None
BTS390 Interface Actual Value Range: 0~63
0 LTE, Default Value: 46
BTS590
0,
BTS590
0
WCDM
A,
BTS590
0 LTE
OMLO BTS390 SET WRFD- IP Meaning: Indicates the priority of the low-level OM
WPRI 0, DIFPRI 050402 Transmi data, such as the data to be uploaded or downloaded.
BTS390 LST ssion The priority has a positive correlation with the value
0 DIFPRI Introduc of this parameter. The low-level OM data includes the
WCDM tion on packets related to File Transfer Protocol (FTP).
A, Iub GUI Value Range: 0~63
BTS390 Interface
0 LTE, Unit: None
BTS590 Actual Value Range: 0~63
0, Default Value: 18
BTS590
0
WCDM
A,
BTS590
0 LTE
IPCLKP BTS390 SET None None Meaning: Indicates the priority of the IP clock. If the
RI 0, DIFPRI IP clock that follows the PTP is used, this parameter is
BTS390 LST set to the DSCP of the PTP packets. If the IP clock
0 DIFPRI that follows the Huawei proprietary protocol is used,
WCDM this parameter is set to the DSCP of these packets that
A, follow the Huawei proprietary protocol.
BTS390 GUI Value Range: 0~63
0 LTE,
BTS590 Unit: None
0, Actual Value Range: 0~63
BTS590 Default Value: 46
0
WCDM
A,
BTS590
0 LTE
CCHPR BSC690 ADD WRFD- ATM Meaning: Primary path that carries the common
IPATH 0 TRMM 050406 QoS channel services.
AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE,
AP Node B LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
(Overbo LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
oking on LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Hub CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Node B LQCS5, LQCS6, LQCS7
Transmi
ssion) Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
SIPPRIP BSC690 ADD WRFD- ATM Meaning: This parameter is used to set IMS SRB
ATH 0 TRMM 050406 QoS primary path.
AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE,
AP Node B LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
(Overbo LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
oking on LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Hub CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Node B LQCS5, LQCS6, LQCS7
Transmi
ssion) Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
SRBPRI BSC690 ADD WRFD- ATM Meaning: Signaling service bearer primary path.
PATH 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
VOICE BSC690 ADD WRFD- ATM Meaning: AMR voice service bearer primary path.
PRIPAT 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
H AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
CSCON BSC690 ADD WRFD- ATM Meaning: R99 CS conversational service primary
VPRIPA 0 TRMM 050406 QoS path. When the interface type is Iu-CS, this parameter
TH AP Introduc does not differentiate the service bearer type.
MOD tion on GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
TRMM Hub BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
AP Node B AF32, AF33, AF41, AF42, AF43, EF, LQBE,
(Overbo LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
oking on LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
Hub LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Node B CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Transmi LQCS5, LQCS6, LQCS7
ssion)
Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
CSSTR BSC690 ADD WRFD- ATM Meaning: R99 CS streaming service bearer primary
MPRIP 0 TRMM 050406 QoS path. When the interface type is Iu-CS, this parameter
ATH AP Introduc does not differentiate the service bearer type.
MOD tion on GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
TRMM Hub BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
AP Node B AF32, AF33, AF41, AF42, AF43, EF, LQBE,
(Overbo LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
oking on LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
Hub LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Node B CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Transmi LQCS5, LQCS6, LQCS7
ssion)
Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
PSCON BSC690 ADD WRFD- ATM Meaning: R99 PS conversational service primary path.
VPRIPA 0 TRMM 050406 QoS When the interface type is Iu-PS, this parameter does
TH AP Introduc not differentiate the service bearer type.
MOD tion on GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
TRMM Hub BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
AP Node B AF32, AF33, AF41, AF42, AF43, EF, LQBE,
(Overbo LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
oking on LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
Hub LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Node B CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Transmi LQCS5, LQCS6, LQCS7
ssion)
Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
PSSTR BSC690 ADD WRFD- ATM Meaning: R99 PS streaming service bearer primary
MPRIP 0 TRMM 050406 QoS path. When the interface type is Iu-PS, this parameter
ATH AP Introduc does not differentiate the service bearer type.
MOD tion on GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
TRMM Hub BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
AP Node B AF32, AF33, AF41, AF42, AF43, EF, LQBE,
(Overbo LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
oking on LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
Hub LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Node B CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Transmi LQCS5, LQCS6, LQCS7
ssion)
Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
PSINTH BSC690 ADD WRFD- ATM Meaning: R99 PS high PRI interactive primary path.
GHPRIP 0 TRMM 050406 QoS When the interface type is Iu-PS, this parameter does
ATH AP Introduc not differentiate the service bearer type.
MOD tion on GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
TRMM Hub BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
AP Node B AF32, AF33, AF41, AF42, AF43, EF, LQBE,
(Overbo LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
oking on LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
Hub LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Node B CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Transmi LQCS5, LQCS6, LQCS7
ssion)
Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
PSINT BSC690 ADD WRFD- ATM Meaning: R99 PS middle PRI interactive primary
MIDPRI 0 TRMM 050406 QoS path. When the interface type is Iu-PS, this parameter
PATH AP Introduc does not differentiate the service bearer type.
MOD tion on GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
TRMM Hub BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
AP Node B AF32, AF33, AF41, AF42, AF43, EF, LQBE,
(Overbo LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
oking on LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
Hub LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Node B CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Transmi LQCS5, LQCS6, LQCS7
ssion)
Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
PSINTL BSC690 ADD WRFD- ATM Meaning: R99 PS low PRI interactive primary path.
OWPRI 0 TRMM 050406 QoS When the interface type is Iu-PS, this parameter does
PATH AP Introduc not differentiate the service bearer type.
MOD tion on GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
TRMM Hub BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
AP Node B AF32, AF33, AF41, AF42, AF43, EF, LQBE,
(Overbo LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
oking on LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
Hub LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Node B CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Transmi LQCS5, LQCS6, LQCS7
ssion)
Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
PSBKG BSC690 ADD WRFD- ATM Meaning: R99 PS background service bearer primary
PRIPAT 0 TRMM 050406 QoS path. When the interface type is Iu-PS, this parameter
H AP Introduc does not differentiate the service bearer type.
MOD tion on GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
TRMM Hub BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
AP Node B AF32, AF33, AF41, AF42, AF43, EF, LQBE,
(Overbo LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
oking on LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
Hub LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Node B CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Transmi LQCS5, LQCS6, LQCS7
ssion)
Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HDSRB BSC690 ADD WRFD- ATM Meaning: HSDPA signaling bearer primary path.
PRIPAT 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
H AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HDSIPP BSC690 ADD WRFD- ATM Meaning: HSDPA IMS signaling bearer primary path.
RIPATH 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HDVOI BSC690 ADD WRFD- ATM Meaning: HSDPA voice service bearer primary path.
CEPRIP 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
ATH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HDCON BSC690 ADD WRFD- ATM Meaning: HSDPA conversational service bearer
VPRIPA 0 TRMM 050406 QoS primary path.
TH AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE,
AP Node B LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
(Overbo LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
oking on LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Hub CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Node B LQCS5, LQCS6, LQCS7
Transmi
ssion) Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HDSTR BSC690 ADD WRFD- ATM Meaning: HSDPA streaming service bearer primary
MPRIP 0 TRMM 050406 QoS path.
ATH AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE,
AP Node B LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
(Overbo LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
oking on LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Hub CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Node B LQCS5, LQCS6, LQCS7
Transmi
ssion) Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HDINT BSC690 ADD WRFD- ATM Meaning: HSDPA high PRI interactive primary path.
HGHPR 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
IPATH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HDINT BSC690 ADD WRFD- ATM Meaning: HSDPA middle PRI interactive primary
MIDPRI 0 TRMM 050406 QoS path.
PATH AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE,
AP Node B LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
(Overbo LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
oking on LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Hub CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Node B LQCS5, LQCS6, LQCS7
Transmi
ssion) Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HDINT BSC690 ADD WRFD- ATM Meaning: HSDPA low PRI interactive primary path.
LOWPR 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
IPATH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HDBKG BSC690 ADD WRFD- ATM Meaning: HSDPA background service bearer primary
PRIPAT 0 TRMM 050406 QoS path.
H AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE,
AP Node B LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
(Overbo LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
oking on LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Hub CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Node B LQCS5, LQCS6, LQCS7
Transmi
ssion) Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HUSRB BSC690 ADD WRFD- ATM Meaning: HSUPA signaling bearer primary path.
PRIPAT 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
H AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HUSIPP BSC690 ADD WRFD- ATM Meaning: HSUPA IMS signaling bearer primary path.
RIPATH 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HUVOI BSC690 ADD WRFD- ATM Meaning: HSUPA voice service bearer primary path.
CEPRIP 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
ATH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HUCON BSC690 ADD WRFD- ATM Meaning: HSUPA conversational service primary
VPRIPA 0 TRMM 050406 QoS path.
TH AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE,
AP Node B LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
(Overbo LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
oking on LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Hub CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Node B LQCS5, LQCS6, LQCS7
Transmi
ssion) Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HUSTR BSC690 ADD WRFD- ATM Meaning: HSUPA streaming service bearer primary
MPRIP 0 TRMM 050406 QoS path.
ATH AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE,
AP Node B LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
(Overbo LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
oking on LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Hub CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Node B LQCS5, LQCS6, LQCS7
Transmi
ssion) Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HUINT BSC690 ADD WRFD- ATM Meaning: HSUPA high PRI interactive primary path.
HGHPR 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
IPATH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HUINT BSC690 ADD WRFD- ATM Meaning: HSUPA middle PRI interactive primary
MIDPRI 0 TRMM 050406 QoS path.
PATH AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE,
AP Node B LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
(Overbo LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
oking on LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Hub CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Node B LQCS5, LQCS6, LQCS7
Transmi
ssion) Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HUINT BSC690 ADD WRFD- ATM Meaning: HSUPA low PRI interactive primary path.
LOWPR 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
IPATH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE,
TRMM Hub LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
AP Node B LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
(Overbo LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
oking on CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Hub LQCS5, LQCS6, LQCS7
Node B
Transmi Unit: None
ssion) Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
HUBKG BSC690 ADD WRFD- ATM Meaning: HSUPA background service bearer primary
PRIPAT 0 TRMM 050406 QoS path.
H AP Introduc GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
MOD tion on BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
TRMM Hub AF32, AF33, AF41, AF42, AF43, EF, LQBE,
AP Node B LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
(Overbo LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
oking on LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
Hub CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
Node B LQCS5, LQCS6, LQCS7
Transmi
ssion) Unit: None
Actual Value Range: CBR, RT_VBR, NRT_VBR,
UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, CS1, CS2, CS3, CS4,
CS5, CS6, CS7, LQCS1, LQCS2, LQCS3, LQCS4,
LQCS5, LQCS6, LQCS7
Default Value: None
9 Counters
10 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
11 Reference Documents