UX2 Interface Management (RAN18.1 - 02)

WCDMA RAN
uX2 Interface Management Feature

Parameter Description
Issue 02
Date 2016-03-28
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 02 (2016-03-28) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
WCDMA RAN
uX2 Interface Management Feature Parameter Description Contents
Contents
1 About This Document.................................................................................................................. 1

1.1 Scope.............................................................................................................................................................................. 1
1.2 Intended Audience.......................................................................................................................................................... 1
1.3 Change History............................................................................................................................................................... 1
1.4 Differences Between Base Station Types....................................................................................................................... 2
2 Overview......................................................................................................................................... 3
2.1 Introduction.................................................................................................................................................................... 3
2.2 Benefits........................................................................................................................................................................... 3
2.3 Architecture.................................................................................................................................................................... 4
2.4 Specifications..................................................................................................................................................................5
3 uX2 Interface Management in Common Scenarios.................................................................6

3.1 uX2 Interface Self-Setup................................................................................................................................................ 6
3.1.1 uX2 Self-Setup with SCTPPEER and USERPLANEPEER Manually Configured................................................ 6
3.1.2 uX2 Self-Setup with SCTPPEER and USERPLANEPEER Automatically Configured.........................................7
3.2 uX2 Interface Auto-Deletion........................................................................................................................................ 10
3.3 uX2 Dynamic Blacklist.................................................................................................................................................11
4 uX2 Interface Self-Setup in IPsec-enabled Scenarios...........................................................12

4.1 Overview...................................................................................................................................................................... 12
4.2 uX2 Self-Setup in IPsec-enabled Scenarios with SCTPPEER and USERPLANEPEER Manually Configured.........13
4.2.1 uX2 Self-Setup with All IPsec MOs Manually Configured...................................................................................... 14
4.2.2 uX2 Self-Setup with Some IPsec MOs Automatically Generated............................................................................ 14
4.2.2.1 SeGW Deployed Between NodeBs........................................................................................................................ 14
4.2.2.2 No SeGW Between NodeBs...................................................................................................................................19
4.3 uX2 Self-Setup in IPsec-enabled Scenarios with SCTPPEER and USERPLANEPEER Automatically Configured
............................................................................................................................................................................................ 21
4.3.1 uX2 Self-Setup with All IPsec MOs Manually Configured...................................................................................... 21
4.3.2 uX2 Self-Setup with Some IPsec MOs Automatically Generated............................................................................ 21
4.3.2.1 SeGW Deployed Between NodeBs........................................................................................................................ 21
4.3.2.2 No SeGW Between NodeBs...................................................................................................................................24
4.4 Automatic and Manual Configuration of ACL Rules for uX2 Packet Filtering...........................................................26
5 Important Notes for uX2 Self-Setup........................................................................................ 27

6 Related Features...........................................................................................................................29
Issue 02 (2016-03-28) Huawei Proprietary and Confidential ii

WCDMA RAN
uX2 Interface Management Feature Parameter Description Contents
7 Network Impact........................................................................................................................... 30
8 Engineering Guidelines............................................................................................................. 31
8.1 When to Use uX2 Interface Management.................................................................................................................... 31
8.2 Required Information................................................................................................................................................... 31
8.3 Planning........................................................................................................................................................................ 31
8.3.1 RF Planning............................................................................................................................................................... 31
8.3.2 Network Planning...................................................................................................................................................... 31
8.3.3 Hardware Planning.................................................................................................................................................... 31
8.4 Deployment.................................................................................................................................................................. 31
8.4.1 Process....................................................................................................................................................................... 31
8.4.2 Requirements............................................................................................................................................................. 32
8.4.3 Data Preparation........................................................................................................................................................ 33
8.4.4 Initial Configuration.................................................................................................................................................. 46
8.4.4.1 Using the CME....................................................................................................................................................... 46
8.4.4.2 Using MML Commands......................................................................................................................................... 53
8.4.4.3 MML Command Examples.................................................................................................................................... 53
8.4.5 Activation Observation..............................................................................................................................................54
8.4.6 Deactivation...............................................................................................................................................................55
8.4.7 Reconfiguration......................................................................................................................................................... 55
8.5 Performance Monitoring...............................................................................................................................................55
8.6 Parameter Optimization................................................................................................................................................ 56
8.7 Troubleshooting............................................................................................................................................................ 56
9 Parameters..................................................................................................................................... 58
10 Counters.................................................................................................................................... 107
11 Glossary..................................................................................................................................... 109
12 Reference Documents............................................................................................................. 110
Issue 02 (2016-03-28) Huawei Proprietary and Confidential iii

WCDMA RAN
uX2 Interface Management Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes uX2 Interface Management, including its technical principles,
related features, network impact, and engineering guidelines.
Any managed objects (MOs), parameters, alarms, or counters described herein correspond to
the software release delivered with this document. Any future updates will be described in the
product documentation delivered with future software releases.
This document applies to the following types of base stations.
Base Station Model

Type
Macro BTS3900, BTS3900A, BTS3900C, BTS3900L, BTS3900AL, and

DBS3900
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes:
l Feature change
Changes in features and parameters of a specified version as well as the affected entities
l Editorial change
Issue 02 (2016-03-28) Huawei Proprietary and Confidential 1

WCDMA RAN
uX2 Interface Management Feature Parameter Description 1 About This Document
Changes in wording or addition of information and any related parameters affected by

editorial changes. Editorial change does not specify the affected entities.
RAN18.1 02 (2016-03-28)
This issue includes the following changes.
Change Change Description Parameter Change

Type
Feature None None

change
Editorial Optimized the monitoring over the uX2 interface. None

change For details, see 8.5 Performance Monitoring.
RAN18.1 01 (2016-02-29)
This issue includes the following changes.
Change Change Description Parameter Change

Type
Feature None None

change
Editorial Optimized the description about restrictions of the None

change uX2 dynamic blacklist function. For details, see 3.3
uX2 Dynamic Blacklist.
Optimized the monitoring over the uX2 interface. None

For details, see 8.5 Performance Monitoring.
Draft A (2015-12-30) of RAN18.1

This document is created for RAN18.1.
1.4 Differences Between Base Station Types

Only macro base stations support the uX2 interface.

WCDMA RAN
uX2 Interface Management Feature Parameter Description 2 Overview
2 Overview
2.1 Introduction
The uX2 interface is a Huawei-defined logical interface between NodeBs that transmits
service coordination data. uX2 interfaces consist of uX2-C and uX2-U interfaces. The NodeB
can be configured in link and end point modes, whereas the uX2 interface can be configured
only in end point mode.
NOTE
For details about inter-NodeB service coordination, see Multi-Carrier HSDPA Feature Parameter
Description and Inter-NodeB Uplink CoMP Feature Parameter Description.
For details about the link and end point configuration modes, see IP Transmission Feature Parameter
Description.
The uX2 Interface Management feature allows for automatic uX2 interface setup when
triggered, for example, when the end-point configurations change or service coordination is
initiated between NodeBs.
uX2 Interface Management provides the following functions:
l Automatic uX2 interface setup

The NodeB automatically sets up uX2 interfaces based on the configured end point MOs.
l Automatic uX2 interface deletion
The NodeB automatically deletes uX2-C links that were automatically set up and have
been interrupted for a long period.
l Dynamic blacklist
The NodeB automatically deletes uX2-C links that were automatically set up but
physically unreachable, and add NodeBs at both ends of the links to the blacklist,
preventing undesired alarms.
2.2 Benefits
uX2 Interface Management simplifies configuration operations, reduces capital expenditure
(CAPEX) for operators, and improves NodeB resource usage.

WCDMA RAN
2.3 Architecture
Figure 2-1 shows the uX2 interface in a network.
Figure 2-1 uX2 interface in a network
The uX2 interface supports only the IP RAN networking mode, as shown in Figure 2-2. In an
IP RAN network, uX2 links can be set up over Ethernet ports on transmission boards, through
which NodeBs or MBTSs connect to the transport network.
Figure 2-2 Coordination over IP RAN

WCDMA RAN
NOTE
In this network topology, the uX2 and Iub interfaces may share an Ethernet egress. Due to the high
bandwidth requirements of coordination services, transmission resources may become insufficient with
the introduction of the uX2 interface. To minimize the impact of uX2 services on Iub services,
transmission QoS policies such as flow control, transport resource overload control, and queue
congestion backpressure are introduced. For details, see Transmission Resource Management Feature
Parameter Description.
The uX2-C and uX2-U interfaces use different protocol stacks, as shown in Figure 2-3.
l The uX2-C interface uses the Signaling Control Transmission Protocol (SCTP).
l The uX2-U interface uses the User Datagram Protocol (UDP).
Figure 2-3 uX2 protocol stack
This document describes automatic setup of the uX2 interface in common and IPsec-enabled
scenarios. For common scenarios, basic configurations are provided. For IPsec-enabled
scenarios, IPsec-protected NodeB packets and packet filtering are described. For details, see 3
uX2 Interface Management in Common Scenarios and 4 uX2 Interface Self-Setup in
IPsec-enabled Scenarios.
For details about the limitations of uX2 interface management in certain scenarios, see 5
Important Notes for uX2 Self-Setup.
2.4 Specifications
When the UMPT serves as the main control board in a macro NodeB, a maximum of 96 uX2-
C interfaces can be configured.

WCDMA RAN
uX2 Interface Management Feature Parameter Description 3 uX2 Interface Management in Common Scenarios
3 uX2 Interface Management in Common

Scenarios
3.1 uX2 Interface Self-Setup

uX2 interface self-setup consists of uX2-C self-setup and uX2-U self-setup.
uX2 self-setup can be implemented in the following ways:
l uX2 self-setup with the SCTPPEER and USERPLANEPEER MOs manually
configured
If a NodeB has multiple uX2 interfaces, you need to manually add multiple SCTPPEER
and USERPLANEPEER MOs to obtain the control-plane and user-plane IP addresses
of the peer.
l uX2 self-setup with the SCTPPEER and USERPLANEPEER MOs automatically
configured
A NodeB initiates an inter-NodeB service coordination to trigger a uX2 setup. The
control-plane and user-plane IP addresses of the peer are automatically obtained.
It is recommended that information about the peer end be automatically configured when
service coordination is initiated between NodeBs under the same RNC and U2000. This
reduces manual intervention and costs for network planning, optimization, and O&M.
3.1.1 uX2 Self-Setup with SCTPPEER and USERPLANEPEER

Manually Configured
Figure 3-1 shows the relationships between MOs during uX2 self-setup with the SCTPPEER
and USERPLANEPEER MOs manually configured.

WCDMA RAN
Figure 3-1 Relationships between MOs during uX2 self-setup with the SCTPPEER and
USERPLANEPEER MOs manually configured
The uX2 self-setup procedures are as follows:

1. The NodeB obtains a data configuration file, which contains the following MOs:
SCTPHOST, USERPLANEHOST, SCTPPEER, USERPLANEPEER, UX2,
EPGROUP, SCTPTEMPLAT, USERPLANEHOST, and USERPLANEPEER.
2. The NodeB generates an SCTPLNK MO based on the parameters configured in the
UX2, EPGROUP, SCTPHOST, and SCTPPEER MOs.
In the SCTPLNK MO, the first IP address of the local NodeB (specified by the
SCTPHOST.SIGIP1V4 parameter) is used as the IP address of the local NodeB.
The first IP address of the peer NodeB (specified by the SCTPPEER.SIGIP1V4
parameter) is used as the IP address of the peer NodeB. Parameters for setting up an
SCTP link must be configured in the SCTPTEMPLATE MO referenced by the
SCTPHOST MO. If a second IP address is configured in the SCTPHOST or
SCTPPEER MO, the NodeB automatically sets up a multihoming SCTP link.
The value of SCTPLNK.DESCRI must be the same as the value of
SCTPPEER.USERLABEL.
3. The NodeB then sets up a uX2-U transmission link based on parameters configured in
the UX2, EPGROUP, USERPLANEHOST, and USERPLANEPEER MOs.
4. After the SCTPLNK MO is configured, the NodeB automatically generates the
CPBEARER and UX2INTERFACE MOs based on the UX2 and EPGROUP MOs.
3.1.2 uX2 Self-Setup with SCTPPEER and USERPLANEPEER

Automatically Configured
Figure 3-2 shows the relationships between MOs during uX2 self-setup with the SCTPPEER
and USERPLANEPEER MOs automatically configured.

WCDMA RAN
Figure 3-2 Relationships between MOs during uX2 self-setup with the SCTPPEER and
USERPLANEPEER MOs automatically configured
The NodeB automatically sets up the SCTP link, uX2-U transmission link, and uX2 interface
based on the data configuration file and the automatically generated SCTPPEER and
USERPLANEPEER MOs. The data configuration file contains the following MOs:
SCTPHOST, USERPLANEHOST, EPGROUP, and UX2.
Service coordination initiated by an upper-layer causes the local NodeB to obtain information
about the peer NodeB. As a result, the SCTPPEER and USERPLANEPEER MOs are
automatically generated, and then the uX2 self-setup is implemented.
Currently, the NodeB only supports uX2 self-setup over the operations support system (OSS).
In uX2 over OSS mode, the local NodeB obtains information about the peer NodeB through
the U2000. This mode applies to the scenario where the local and peer NodeBs are managed
by the same RNC and U2000.
In this mode, the RNC, NodeB, and U2000 must meet the following conditions:
l RNC
The RNC configures inter-NodeB coordination services to trigger a NodeB to set up the
uX2 interface.
l NodeB
uX2-related MOs are configured, which include SCTPHOST,
USERPLANEHOST, UX2, EPGROUP, and SCTPTEMPLATE.
A NodeB initiates an inter-NodeB service coordination to trigger a uX2 setup.
NOTE
During automatic configuration of the uX2 interface, the parameter PN in the MO SCTPHOST
must have the same value for the two NodeBs interconnected through the uX2 interface.
l U2000
The CMServer function is enabled on the U2000. Otherwise, the U2000 cannot
respond to the uX2 self-setup request sent by the NodeB.

WCDMA RAN
Corresponding NodeBs have been configured on the U2000. The NodeBID and
NodeBName of the NodeB on the U2000 must be consistent with those on the
RNC.
Figure 3-3 shows the main procedures for uX2 self-setup over OSS when both the local and
peer NodeBs are provided by Huawei.
Figure 3-3 Procedures for uX2 self-setup over OSS
1. The RNC sends a uX2 Setup Indication message to the source NodeB. The message
contains the uX2-related parameters of the source NodeB and target NodeB, such as the
local NodeB ID, local RNC ID, peer NodeB ID, and peer RNC ID.
2. The source NodeB sends a Configuration Transfer message to the U2000. This message
contains uX2 interface information, such as the uX2 interface configuration of the source
NodeB, target NodeB ID, and target RNC ID.
3. After receiving the message, the U2000 transfers the message to the target NodeB
identified by the target NodeB ID. If the U2000 cannot locate the target NodeB, the uX2
self-setup fails.
4. The target NodeB sends the Configuration Transfer message to the U2000, which
contains the target NodeB's control plane IP address. Meanwhile, the target NodeB
automatically generates related MOs to set up transmission links for the control plane.
a. The target NodeB automatically generates the SCTPPEER MO based on the
control-plane IP address of the target NodeB contained in the message. The target
NodeB then adds the SCTPPEER MO to the EPGROUP MO.
b. The target NodeB automatically generates the SCTPLNK, CPBEARER, and
UX2INTERFACE MOs according to the configured MOs SCTPHOST, UX2,
EPGROUP, and SCTPTEMPLATE as well as the automatically generated MO
SCTPPEER.
5. The U2000 sends the Configuration Transfer message to the source NodeB. If the U2000
cannot locate the source NodeB, the uX2 self-setup fails.
6. Upon receiving this message, the source NodeB automatically generates related MOs to
set up transmission links for the control plane.
a. The source NodeB automatically generates the SCTPPEER MO based on the
control-plane IP address of the target NodeB contained in the message. The source
NodeB then adds the SCTPPEER MO to the EPGROUP MO.

WCDMA RAN
b. The source NodeB automatically generates the SCTPLNK, CPBEARER, and

UX2INTERFACE MOs according to the configured MOs SCTPHOST, UX2,
EPGROUP, and SCTPTEMPLATE as well as the automatically generated MO
SCTPPEER.
7. After the uX2-C self-setup is complete, the source NodeB sends the uX2-U setup request
to the target NodeB over the uX2-C interface. During this procedure, the user-plane end
point information is exchanged to generate the USERPLANEPEER MO to set up the
uX2-U interface. If the transmission types at two ends are inconsistent, the uX2-U self-
setup fails.
During the automatic generation of the SCTPPEER and USERPLANEPEER MOs, the
source and target NodeBs automatically assign the value of the SCTPPEER.USERLABEL
or USERPLANEPEER.USERLABEL parameter according to the following rules:
The NodeB automatically assigns the value of the SCTPPEER.USERLABEL or
USERPLANEPEER.USERLABEL parameter in the format of uX2:RNCId_xxx NBId_xxx-
xxx-xxxxxxx based on the target NodeB's RNC ID and NodeB ID. uX2:RNC_xxx indicates
the logical RNC ID of the target NodeB. NBId_xxx-xxx-xxxxxxx indicates the NodeB ID
information of the target NodeB. The NodeB automatically assigns the value of
SCTPPEER.USERLABEL to SCTPLNK.DESCRI.
3.2 uX2 Interface Auto-Deletion

New uX2 interfaces cannot be configured if the total number of configured uX2 interfaces of
an NodeB exceeds the upper limit.
During network deployment, redundant uX2 interfaces may exist due to network adjustment.
Therefore, redundant uX2 interfaces must be deleted. The uX2 auto-deletion function
automatically identifies and deletes redundant uX2 interfaces, reducing manual maintenance
costs.
This function takes effect after UX2AutoDeleteForFaultSw(BSC6900,BSC6910) is set to
ON.
If a uX2 interface is constantly faulty within a period specified by
UX2AutoDeleteForFaultTimer(BSC6900,BSC6910), local configurations for this interface,
together with the uX2-C and uX2-U links, are axiomatically deleted.
NOTE
UX2AutoDeleteForFaultTimer(BSC6900,BSC6910) is specified based on network conditions. It is

recommended that the timer length be set to a small value for scenarios requiring rapid automatic
adjustment or convergence of uX2 interfaces, such as NodeBs under migration, capacity expansion, or
network reconstruction. A smaller value of this parameter results in a higher probability of automatic
uX2 deletion and therefore a higher probability that uX2 interfaces are incorrectly deleted and then
automatically set up. A larger value of this parameter results in a lower probability of automatic uX2
deletion and therefore lower efficiency of deleting faulty uX2 interfaces. As a result, new uX2 interfaces
cannot be configured if the total number of uX2 interfaces configured for a NodeB has reached its
maximum.
Automatic uX2 deletion applies only to uX2 links that are automatically set up. For example, when
Inter-NodeB Uplink CoMP (Joint Reception) is enabled. It does not apply to uX2 links that are manually
set up.

WCDMA RAN
3.3 uX2 Dynamic Blacklist

During network adjustment, many invalid alarms are reported if uX2 self-setup fails due to
unreachable routes or physical link isolation. The uX2 dynamic blacklist function helps to
identify and delete invalid alarms and uX2 configurations, reducing manual maintenance
costs.
This function takes effect after UX2DynBlackListSw(BSC6900,BSC6910) is set to ON.
Specifically, if uX2 interface self-setup fails within five consecutive minutes, the RNC
obtains configurations for this interface and deletes associated uX2-C and uX2-U links. In
addition, the RNC adds NodeBs at both ends to the dynamic blacklist and the penalty expires
only after UX2DynBlackListAgingTimer(BSC6900,BSC6910) expires.
NOTE
l UX2DynBlackListAgingTimer(BSC6900,BSC6910) is specified based on network conditions. It is

recommended that the timer length be set to a small value for scenarios requiring rapid automatic
adjustment or convergence of uX2 interfaces, such as NodeBs under migration, capacity expansion,
or network reconstruction. A smaller value of this parameter results in more redundant signaling
data required for uX2 self-setup. A larger value of this parameter results in a longer wait period for
automatic uX2 setup.
l For blacklisted uX2 links, automatic uX2 setup works only after
UX2DynBlackListAgingTimer(BSC6900,BSC6910) expires, but manual uX2 setup is not affected.
l For the uX2 link between NodeBs automatically selected by the RNC:
The uX2 dynamic blacklist function takes effect when the NodeB parameter UX2SONSETUPSW is
set to ON.
When the NodeB parameter UX2SONSETUPSW is set to OFF, and the
SCTPPEER.USERLABEL or USERPLANEPEER.USERLABEL parameter manually configured
for the uX2 link does not comply with uX2:RNCId_xxx NBId_xxx-xxx-xxxxxxx, the uX2 dynamic
blacklist function does not take effect.
l For the uX2 link between NodeBs manually selected by the RNC (for example, inter-NodeB DB-
HSDPA), the uX2 dynamic blacklist function does not take effect.

WCDMA RAN
uX2 Interface Management Feature Parameter Description 4 uX2 Interface Self-Setup in IPsec-enabled Scenarios
4 uX2 Interface Self-Setup in IPsec-enabled

Scenarios
4.1 Overview
When IPsec is enabled, IPsec is performed on packets sent by a NodeB and packet filtering is
performed on packets received by a NodeB. Table 4-1 describes security policies for the uX2
interface.
Table 4-1 Security policies for the uX2 interface

Scenario Security Policy
IP RAN l IPsec can be implemented on a network where a security gateway

networking (SeGW) is deployed between NodeBs or a network where NodeBs are
directly interconnected through uX2 interfaces.
l Both the uX2-C and uX2-U interfaces support IPsec protection and
packet filtering.
l Both the uX2-C and uX2-U interfaces support self-setup in IPsec
scenarios.

WCDMA RAN
NOTE
IPsec specifications are as follows:

l A NodeB supports a maximum of 100 Internet Key Exchange (IKE) peers. During uX2 self-setup in
IPsec-enabled scenarios, the sum of manually and automatically configured IKE peers must not
exceed 100.
l A NodeB supports a maximum of 64 IPsec security association (SA) pairs. At least one pair of IPsec
SAs is required for one IPsec tunnel. During uX2 self-setup with IPsec enabled, the number of
supported uX2 interfaces is restricted by the IPsec tunnel specifications.
l Access control list (ACL) rules apply to packet filtering as well as IPsec-enabled scenarios. These
rules applied to packet filtering can filter packets received by a NodeB. ACL rules applied to IPsec-
enabled scenarios provide corresponding IPsec policies to packets sent by a NodeB.
l A NodeB supports a maximum of 868 ACL rules (specified by the ACLRULE MO). This
specification is shared by packet filtering and IPsec scenarios. During uX2 self-setup, the number of
supported uX2 interfaces is restricted by the ACL rule specifications.
4.2 uX2 Self-Setup in IPsec-enabled Scenarios with

SCTPPEER and USERPLANEPEER Manually Configured
This section describes the differences in uX2 self-setup between the common scenarios
presented in 3.1 uX2 Interface Self-Setup and the IPsec-enabled scenarios with the
SCTPPEER and USERPLANEPEER MOs manually configured. Users can implement
uX2-C and uX2-U self-setup in IPsec-enabled scenarios with SCTPPEER and
USERPLANEPEER manually configured, by referring to this section and 3.1 uX2 Interface
Self-Setup.
In IPsec-enabled scenarios, if the SCTPPEER and USERPLANEPEER MOs are manually
configured, NodeBs support the following methods of uX2 self-setup:
l uX2 self-setup with all IPsec MOs manually configured (recommended)
l uX2 self-setup with some IPsec MOs automatically generated (with an SeGW deployed
between NodeBs)
An SeGW is located between two NodeBs, and IPsec tunnels are set up between the
SeGW and NodeBs in the following ways:
Each uX2-C interface exclusively uses an IPsec tunnel.
If one SCTP host is connected to multiple SCTP peers, the NodeB sets up one IPsec
tunnel for each SCTP peer.
Each uX2-U interface exclusively uses an IPsec tunnel.
If one user-plane host is connected to multiple user-plane peers, the NodeB sets up
one IPsec tunnel for each user-plane peer.
uX2-C interfaces share an IPsec tunnel.
If one SCTP host is connected to multiple SCTP peers, the NodeB sets up one IPsec
tunnel for all the SCTP peers.
uX2-U interfaces share an IPsec tunnel.
If one user-plane host is connected to multiple user-plane peers, the NodeB sets up
one IPsec tunnel for all the user-plane peers.
l uX2 self-setup with some IPsec MOs manually configured (with no SeGW between
NodeBs)
Two NodeBs are directly interconnected through the uX2 interface, and an IPsec tunnel
is set up between them to protect the uX2 interface.

WCDMA RAN
A NodeB can use only one of the preceding three methods for uX2 interface self-setup.
To prevent excessive IPsec tunnels in the network, you are advised to use one IPsec tunnel to
protect all uX2 interfaces extended from one NodeB.
4.2.1 uX2 Self-Setup with All IPsec MOs Manually Configured

When this method is used, all IPsec MOs for the uX2 interface are manually configured,
including IKEPROPOSAL, IKEPEER, ACL, ACLRULE, IPSECPROPOSAL,
IPSECPOLICY, and IPSECBIND. In this situation, the IPsec switches of all MOs must be
turned off.
For details about how to configure these MOs, see IPsec Feature Parameter Description.
4.2.2 uX2 Self-Setup with Some IPsec MOs Automatically

Generated
presented in 3.1 uX2 Interface Self-Setup and the IPsec-enabled scenarios with some IPsec
MOs automatically generated.
4.2.2.1 SeGW Deployed Between NodeBs

When an SeGW is deployed between NodeBs, the configuration modes of IPsec-related MOs
are as follows:
l The following MOs need to be manually configured: ACL, ACLRULE, IKEPEER,
IKEPROPOSAL, IPSECPROPOSAL, SECURITYHOST,
SECURITYTEMPLATE, and SECURITYPEER.
l The following MOs can be automatically configured: ACL, ACLRULE,
IPSECPOLICY, IPSECBIND.
The procedures for uX2 self-setup vary depending on whether the uX2 interface exclusively
uses an IPsec tunnel.
l Each uX2-U interface exclusively uses an IPsec tunnel
Figure 4-1 shows the procedures for uX2 self-setup with some IPsec MOs manually
configured when each uX2 interface exclusively uses an IPsec tunnel.

WCDMA RAN
Figure 4-1 uX2 self-setup with some IPsec MOs manually configured (each uX2 interface
exclusively uses an IPsec tunnel)
The uX2-C self-setup procedures are as follows:

IKEPEER, IKEPROPOSAL, IPSECPROPOSAL, SECURITYPEER,
SECURITYHOST, SECURITYTEMPLATE, SCTPHOST, SCTPPEER, and
SCTPTEMPLATE. (SCTPHOST, SCTPPEER, and SCTPTEMPLATE are used for
setting up the uX2-C interface). Parameters in the MOs in the data configuration file
must meet the requirements in the following table.
MO Parameter ID Value
SECURITYTEMPLATE SEGWSWITCH ENABLE(Enable)
SECURITYHOST SEGWSWITCH ENABLE(Enable)
SEGWCONFIGMODE SEGW_CONFIG_ON_PE
ER(SeGW Config on
Peer)
SECURITYTEMPLATEI Same as the

D SECURITYTEMPLATEI
D parameter
SCTPHOST SIGIP1SECSWITCH ENABLE(Enable)
SIGIP2SECSWITCH
SIGIP1SECHOSTID Same as the

SECURITYHOSTID
SIGIP2SECHOSTID parameter
SECURITYPEER IPSECPROPNAME Same as the PROPNAME

parameter
PEERNAME Same as the PEERNAME

parameter

WCDMA RAN
SCTPPEER SIGIP1SECSWITCH ENABLE(Enable)
SIGIP2SECSWITCH
SIGIP1SECPEERID Same as the

SECURITYPEERID
SIGIP2SECPEERID parameter

3. Based on the configuration of the preceding IPsec-related parameters, the NodeB
automatically generates the ACL, ACLRULE, IPSECPOLICY, and IPSECBIND
MOs for setting up an IPsec tunnel for the uX2-C interface.
The uX2-U interface self-setup procedures are as follows:
IKEPEER, IKEPROPOSAL, IPSECPROPOSAL, SECURITYPEER,
SECURITYHOST, SECURITYTEMPLATE, USERPLANEHOST, and
USERPLANEPEER. (USERPLANEHOST and USERPLANEPEER are used for
setting up the uX2-U interface). Parameters in the MOs in the data configuration file
SEGWCONFIGMODE SEGW_CONFIG_ON_PE
ER(SeGW Config on
Peer)
SECURITYTEMPLATE Same as the

ID SECURITYTEMPLATEI
D parameter
USERPLANEHOST IPSECSWITCH ENABLE(Enable)
SECHOSTID Same as the

SECURITYHOSTID
parameter

parameter

parameter
USERPLANEPEER IPSECSWITCH ENABLE(Enable)
SECPEERID Same as the

SECURITYPEERID
parameter

WCDMA RAN
2. The NodeB generates a uX2-U transmission link according to the parameters configured
in the UX2, EPGROUP, USERPLANEHOST, and USERPLANEPEER MOs.
MOs for setting up an IPsec tunnel for the uX2-U interface.
l uX2 Interfaces Sharing an IPsec Tunnel
configured when uX2 interfaces share an IPsec tunnel.
Figure 4-2 uX2 self-setup with some IPsec MOs manually configured (uX2 interfaces
share an IPsec tunnel)
The uX2-C interface self-setup procedures are as follows:
IKEPEER, IKEPROPOSAL, IPSECPROPOSAL, SECURITYHOST,
SECURITYTEMPLATE, SCTPHOST, SCTPPEER, and SCTPTEMPLATE.
(SCTPHOST, SCTPPEER, and SCTPTEMPLATE are used for setting up the uX2-C
interface). Parameters in the MOs in the data configuration file must meet the
requirements in the following table.
SEGWCONFIGMODE SEGW_CONFIG_ON_H
OST(SeGW Config on
Host)

D SECURITYTEMPLATEI
D parameter

WCDMA RAN
IPSECPROPNAME Same as the PROPNAME

parameter

parameter
SIGIP2SECSWITCH

SECURITYHOSTID
SCTPPEER SIGIP1SECSWITCH DISABLE(disable)
SIGIP2SECSWITCH

MOs for setting up an IPsec tunnel for the uX2-C interface.
SECURITYTEMPLATE, USERPLANEHOST, and USERPLANEPEER.
(USERPLANEHOST and USERPLANEPEER are used for setting up the uX2-U
interface). Parameters in the MOs in the data configuration file must meet the
requirements in the following table.
OST(SeGW Config on
Host)

D parameter

parameter

parameter

WCDMA RAN

SECURITYHOSTID
parameter

parameter

parameter
USERPLANEPEER IPSECSWITCH DISABLE(disable)
in the UX2, EPGROUP, USERPLANEHOST, and USERPLANEPEER MOs.
automatically generates the ACLRULE, ACL, IPSECPOLICY, and IPSECBIND
MOs for setting up an IPsec tunnel for the uX2-U interface.
4.2.2.2 No SeGW Between NodeBs

When no SeGW is deployed between NodeBs, the configuration modes of IPsec-related MOs
are as follows:
l The following MOs must be manually configured: IKEPROPOSAL,
IPSECPROPOSAL, SECURITYHOST, and SECURITYTEMPLATE.
l The following MOs can be automatically generated: ACL, ACLRULE,
IPSECPOLICY, IPSECBIND, and SECURITYPEER.
configured when there is no SeGW between NodeBs.
Figure 4-3 uX2 self-setup with some IPsec MOs manually configured (with no SeGW
between NodeBs)

WCDMA RAN

IKEPROPOSAL, IPSECPROPOSAL, SECURITYHOST, and
SECURITYTEMPLATE. Parameters in the MOs in the data configuration file must
meet the requirements in the following table.
SECURITYTEMPLATE SEGWSWITCH DISABLE(Disable)

parameter
PROPID Same as the PROPID

parameter
SECURITYHOST SEGWSWITCH DISABLE(Disable)

D parameter
SECURITYPEER SEGWSWITCH DISABLE(Disable)
SIGIP2SECSWITCH

SECURITYHOSTID

SECURITYHOSTID
parameter
SCTPPEER SIGIP1SECSWITCH ENABLE(Enable)
SIGIP2SECSWITCH
SIGIP1SECPEERID Same as the

SECURITYPEERID
SIGIP2SECPEERID parameter
USERPLANEPEER IPSECSWITCH ENABLE(Enable)
SECPEERID Same as the

SECURITYPEERID
parameter
2. The NodeB sets up an SCTP link and a uX2-U transmission link based on the parameters
configured in the UX2, SCTPHOST, USERPLANEHOST, EPGROUP, SCTPPEER,
and USERPLANEPEER MOs.
automatically generates the following MOs: SECURITYPEER ACL, ACLRULE,

WCDMA RAN
IPSECPOLICY, IKEPEER, and IPSECBIND MOs for setting up an IPsec tunnel for
the uX2 interface.
4.3 uX2 Self-Setup in IPsec-enabled Scenarios with

SCTPPEER and USERPLANEPEER Automatically
Configured
presented in 3.1 uX2 Interface Self-Setup and the IPsec-enabled scenarios with the
SCTPPEER and USERPLANEPEER MOs automatically generated. Users can implement
uX2-C and uX2-U self-setup in IPsec-enabled scenarios with SCTPPEER and
USERPLANEPEER automatically generated, by referring to this section and 3.1 uX2
Interface Self-Setup.
In IPsec-enabled scenarios, if the SCTPPEER and USERPLANEPEER MOs are
automatically generated, NodeBs support the following methods of uX2 self-setup:
l uX2 self-setup with all IPsec MOs manually configured (recommended)
l uX2 self-setup with some IPsec MOs automatically generated (with an SeGW deployed
between NodeBs)
An IPsec tunnel is set up directly between two NodeBs to protect the uX2 interface.
l uX2 self-setup with some IPsec MOs automatically generated (with no SeGW between
NodeBs)
An IPsec tunnel is set up directly between two NodeBs to protect the uX2 interface.
A NodeB can use only one of the preceding methods for self-setup of different uX2
interfaces.
To prevent excessive IPsec tunnels in the network, you are advised to use one IPsec tunnel to
protect all uX2 interfaces extended from one NodeB.
4.3.1 uX2 Self-Setup with All IPsec MOs Manually Configured

When this method is used, all IPsec MOs for the uX2 interface are manually configured,
including IKEPROPOSAL, IKEPEER, ACL, ACLRULE, IPSECPROPOSAL,
IPSECPOLICY, and IPSECBIND. In this situation, the IPsec switches of all MOs must be
turned off.
For details about how to configure these MOs, see IPsec Feature Parameter Description.
4.3.2 uX2 Self-Setup with Some IPsec MOs Automatically

Generated
presented in 3.1 uX2 Interface Self-Setup and the IPsec-enabled scenarios with some IPsec
MOs automatically generated.
4.3.2.1 SeGW Deployed Between NodeBs

When an SeGW is deployed between NodeBs and the SCTPEER and USERPLANEPEER
MOs are automatically generated, the NodeB obtains the peer's IP address through the U2000

WCDMA RAN
or MME. However, the NodeB cannot obtain the IP address of the peer SeGW. Therefore, the
IKEPEER MO cannot be automatically generated. In this situation, the NodeB supports the
self-setup only when the uX2-C or uX2-U interfaces share an IPsec tunnel. That is, all the
SCTPPEER (or USERPLANEPEER) corresponding to the SCTPHOST (or
USERPLANEHOST) share an IPsec tunnel.
In this situation, the configuration modes of IPsec-related MOs are as follows:
l The following MOs can be manually configured: IKEPEER, IKEPROPOSAL,

IPSECPROPOSAL, SECURITYHOST, SECURITYTEMPLATE, and
SECURITYPEER.
l The following MOs can be automatically generated: ACLRULE, ACL,
IPSECPOLICY, and IPSECBIND.
Figure 4-4 shows the relationships between IPsec-related MOs.
Figure 4-4 Relationships between IPsec-related MOs
The uX2-C self-setup procedures are as follows:
SECURITYTEMPLATE, SCTPHOST, and SCTPTEMPLATE. (SCTPHOST and
SCTPTEMPLATE are used for setting up the uX2-C interface). Parameters in the MOs
in the data configuration file must meet the requirements in the following table.

WCDMA RAN
OST(SeGW Config on
Host)

D SECURITYTEMPLATEI
D parameter

parameter

parameter
SIGIP2SECSWITCH

SECURITYHOSTID
2. The NodeB generates a uX2-C transmission link according to the parameters configured
in the UX2, EPGROUP, SCTPHOST MOs and the automatically configured
SCTPPEER MO.
3. Based on the configuration of the preceding IPsec-related parameters and the
automatically configured SCTPPEER MO, the NodeB automatically generates the
ACL, ACLRULE, IPSECPOLICY, and IPSECBIND MOs for setting up an IPsec
tunnel for the uX2 interface.
SECURITYTEMPLATE, and USERPLANEHOST. (USERPLANEHOST is used
for setting up the uX2-U interface). Parameters in the MOs in the data configuration file
OST(SeGW Config on
Host)

D parameter

parameter

WCDMA RAN

parameter

SECURITYHOSTID
parameter
in the UX2, EPGROUP, USERPLANEHOST MOs and the automatically configured
USERPLANEPEER MO.
3. Based on the configuration of the preceding IPsec-related parameters and the
automatically configured USEPLANEPEER MO, the NodeB automatically generates
the ACL, ACLRULE, IPSECPOLICY, and IPSECBIND MOs for setting up an IPsec
tunnel for the uX2-U interface.
4.3.2.2 No SeGW Between NodeBs

When NodeBs are directly interconnected and the uX2 control-plane peer and user-plane peer
(MO SCTPEER and USERPLANEPEER) are configured, the NodeB supports IPsec tunnel
self-setup for the uX2-C and uX2-U interfaces. The uX2-C and uX2-U interfaces must be
both configured with direct IPsec and the same SECURITYHOST.
In this situation, the configuration modes of IPsec-related MOs are as follows:
l The following MOs must be manually configured: IPSECPROPOSAL,
IKEPROPOSAL, SCTPHOST, USERPLANEHOST, EPGROUP, and
SECURITYHOST.
l The following MOs can be automatically generated: SECURITYPEER, ACLRULE,
ACL, IPSECPOLICY, IKEPEER, and IPSECBIND.
Figure 4-5 shows the relationships between IPsec-related MOs.

WCDMA RAN
Figure 4-5 Relationships between IPsec-related MOs
The procedure and involved MOs are as follows:

IKEPROPOSAL, IPSECPROPOSAL, SECURITYHOST, and
SECURITYTEMPLATE. Parameters in the MOs in the data configuration file must
meet the requirements in the following table.
SECURITYTEMPLATE SEGWSWITCH DISABLE(Disable)

parameter
PROPID Same as the PROPID

parameter
SECURITYHOST SEGWSWITCH DISABLE(Disable)

D parameter
SCTPHOST SIGIP1SECSWITCH DISABLE(Disable)
SIGIP2SECSWITCH

WCDMA RAN

SECURITYHOSTID
parameter
2. The NodeB generates uX2-C and uX2-U links based on the uX2, SCTPHOST,
USERPLANEHOST, EPGROUP, and the automatically generated SCTPPEER and
USERPLANEPEER MOs.
3. The NodeB automatically generates the following MOs: SECURITYPEER, ACL,
ACLRULE, IPSECPOLICY, IKEPEER, and IPSECBIND, based on the IPsec-
related parameters and the security and service IP addresses of the neighboring NodeB
contained in the signaling. The NodeB then sets up an IPsec tunnel to the uX2-U
interface.
NOTE
If no SeGW is between NodeBs and an IPsec tunnel is set up for a uX2 interface, two ACLRULE MOs
are generated for the control plane and user plane during the automatic setup of the IPsec tunnel. An
IPsec tunnel is set up for only one uX2 interface. If the NodeB has set up 64 IPsec tunnels, which reach
the maximum number of IPsec SAs, no more uX2 interfaces can be added on the NodeB. Therefore, the
number of uX2 interfaces that can be added on an NodeB cannot reach the maximum number 128 in the
preceding scenario.
4.4 Automatic and Manual Configuration of ACL Rules

for uX2 Packet Filtering
presented in 3.1 uX2 Interface Self-Setup and the packet filtering scenarios. Users can
implement uX2 self-setup in packet filtering scenarios by referring to this section and 3.1 uX2
Interface Self-Setup.
The ACLRULE MO can be manually or automatically configured. The
EPGROUP.PACKETFILTERSWITCH parameter specifies the configuration mode of the
ACLRULE MO.
l If the EPGROUP.PACKETFILTERSWITCH parameter referenced by the UX2 MO is
set to ENABLE(Enable), the NodeB automatically generates ACL rules for uX2-C and
uX2-U based on the IP addresses obtained during the uX2 self-setup procedure. In
addition, the NodeB adds the related ACL rules to the corresponding ACL MOs for
packet filtering. If you change the ACL IDs mapping the ACLRULE MOs, the
corresponding ACLRULE MOs are not automatically added to the new ACL MO. In
this situation, the uX2-C and uX2-U links will be disconnected and you must manually
configure the ACLRULE MOs again.
l If EPGROUP.PACKETFILTERSWITCH is set to DISABLE(Disable) in the
EPGROUP MO referenced by the UX2 MO, an ACLRULE MO must be manually
configured for the NodeB. ACLRULE.ACLID in this ACLRULE MO must be set to
the same value as PACKETFILTER.ACLID for packet filtering; otherwise, data
transmission fails.

WCDMA RAN
uX2 Interface Management Feature Parameter Description 5 Important Notes for uX2 Self-Setup
5 Important Notes for uX2 Self-Setup
Application Limitations
If configuring the NodeB is prohibited, uX2-C and uX2-U self-setup will fail because the
related MOs cannot be created.
Configuring the NodeB is prohibited when one of the following conditions is met:
l The NodeB enters the security logout state.

l Configuration recovery fails during the NodeB startup.
l The MML command ACT CFGFILE or ACT BATCHFILE is executed to activate the
configuration files.
l The MML command ACT CB or CFM CB is executed to activate or confirm the
configuration baselines.
l The MML command BKP CFGFILE or the U2000 command EXP CFGSYNFILE is
executed to back up or export configuration files.
l The MML command STR CFGCHKSYNC is executed to check configuration
synchronization.
l Logs are exported into .XML files by one click or configurations are exported at 1:00
a.m.
l Configuration data is upgraded using a USB flash drive.
Assume that the number of UX2 MOs or transmission-related MOs configured on the local
NodeB reaches the maximum number. If a uX2 interface is manually deleted from a peer
NodeB, a uX2 interface cannot be automatically set up between the local and peer NodeBs. In
this case, only manual setup is supported.
uX2 self-setup applies to NodeBs managed by the same RNC and U2000.
Only one uX2 link can be configured between two NodeBs. If more than one uX2 link is
configured, an incorrect uX2 link may be selected for coordination services, causing
coordination services to fail.
uX2 self-setup does not apply to IPv6 networks.
The uX2 interface cannot share an IP address with the eX2 or X2 interface.
When the uX2 interface and the Iub interface share the same IP address, they must use
different EPGROUP MOs.

WCDMA RAN
uX2 Interface Management Feature Parameter Description 5 Important Notes for uX2 Self-Setup
The uX2-U interface automatically establishes a unidirectional IP PM session between two

NodeBs. Therefore, bidirectional IP PM sessions are not required. Otherwise, uX2 links will
become unavailable.
Upgrade Limitations
None
Configuration Limitations
Control plane EPGROUP: If the local IP addresses and port numbers are the same in two
control plane EPGROUP MOs, one SCTPPEER MO cannot simultaneously be added to the
two control plane EPGROUP MOs.
User plane EPGROUP: If the local IP addresses are the same in two user plane EPGROUP
MOs, one USERPLANEPEER MO cannot simultaneously be added to the two user plane
EPGROUP MOs.
If the value of the CTRLMODE parameter under an automatically generated MO is changed

to MANUAL_MODE, this MO can only be manually modified or deleted. These MOs
include SCTPLNK, SCTPPEER, USERPLANEPEER, ACLRULE, ACL, CPBEARER,
SECURITYPEER, IKEPEER, IPSECPOLICY, and IPSECBIND.
NOTE
When the preceding MOs are manually configured, the CTRLMODE parameter value can be either
MANUAL_MODE or AUTO_MODE. When the preceding MOs are automatically configured, the
parameter value is automatically set to AUTO_MODE.
If one of the preceding MOs has been automatically added before manual addition:
l Parameters added to this MO using the CME will replace the automatically added
parameters.
l Parameters added to this MO using the MML will not replace the automatically added
parameters. Instead, a configuration conflict warning will be displayed.
NOTE
For the SCTPPEER, SECURITYPEER, and USERPLANEPEER MOs, the CTRLMODE parameter
is set to AUTO_MODE by default. For other MOs, this parameter is set to MANUAL_MODE by
default.
Based on the information about the local and peer end points included in the EPGROUP MO,
the NodeB automatically generates the SCTPLNK and CPBEARER MOs. For these two
MOs, the CTRLMODE parameter is set to AUTO_MODE. Do not modify or delete these
automatically generated MOs. Otherwise, the corresponding uX2 interface cannot work
properly. If a uX2 interface fails to work properly due to the preceding reason, manually
delete the UX2 MO and add it again.
Packet Filtering Limitations

In end point configuration mode, the EPGROUP.PACKETFILTERSWITCH parameter is
used to control whether to enable the ACL rule auto-configuration function for packet
filtering. Before setting this parameter to ENABLE(Enable), ensure that a
PACKETFILTER MO has been configured.
Deleting the PACKETFILTER MO will not delete the referenced ACLRULE MO.

WCDMA RAN
uX2 Interface Management Feature Parameter Description 6 Related Features
6 Related Features
Required Features
None
Mutually Exclusive Features

None
Affected Features
None

WCDMA RAN
uX2 Interface Management Feature Parameter Description 7 Network Impact
7 Network Impact
System Capacity
No impact.
Network Performance
No impact.

WCDMA RAN
uX2 Interface Management Feature Parameter Description 8 Engineering Guidelines
8 Engineering Guidelines
8.1 When to Use uX2 Interface Management

uX2 Interface Management is recommended when the Inter-NodeB DB-HSDPA feature or the
Inter-NodeB Uplink CoMP feature needs to be deployed.
8.2 Required Information

None
8.3 Planning
8.3.1 RF Planning
None
8.3.2 Network Planning

For details about how to select a networking mode, see 2.3 Architecture.
8.3.3 Hardware Planning

The number of allowed uX2-C interfaces depends on the main control board. For example,
the UMPT or UMDU supports up to 96 uX2-C interfaces.
8.4 Deployment
8.4.1 Process
After the common data is deployed, users can deploy the uX2 interface self-setup function.
Figure 8-1 shows the deployment procedures of uX2 self-setup. The optional procedures in
Figure 8-1 are automatic uX2 peer configuration procedures.

WCDMA RAN
Figure 8-1 uX2 Interface Self-Setup
8.4.2 Requirements
Features or Functions
If the peer NodeB's information is automatically generated, ensure that the RNC and NodeB
support service coordination and related configurations. For example, uX2 interface self-setup
requires the Inter-NodeB DB-HSDPA feature. For related configurations on the RNC and
NodeB, see Multi-Carrier HSDPA Feature Parameter Description and Inter-NodeB Uplink
CoMP Feature Parameter Description.
Hardware
This feature requires the following boards:
l Main control board: UMPT, UDMU, or UMPT+UTRPc
l Baseband processing unit: WBBPd, WBBPf, or UBBPd/UBBPe/UBBPei
License Capacity Expansion

None
Others
l NEs
If the local NodeB obtains the peer NodeB's information through the U2000, the local
and peer NodeBs must be managed by the same U2000 and RNC. The U2000 version
must be iManager U2000 V200R16C10SPC100 or later.
l Transmission networking
Table 8-1 shows the requirements of the uX2 interface for transmission networking.

WCDMA RAN
Table 8-1 Requirements of the uX2 interface for transmission networking
One-way delay (s) Packet Loss Rate Bandwidth (bit/s)

(100%)
4000 1.0 10-3 -
The bandwidth required over the uX2 interface is determined by the bandwidth required
for service coordination. If multiple service coordination features are enabled at the same
time, the required bandwidth must be calculated based on the activation rate and required
bandwidth of these features.
Take the Inter-NodeB DB-HSDPA feature as an example. Each time a pair of
coordinating cells is added, a 3 Mbit/s bandwidth will be consumed in both the uplink
and downlink if the average data rate is used for calculating the required bandwidth. If
the peak rate is used for calculating the required bandwidth, a 19 Mbit/s bandwidth will
be consumed in both the uplink and downlink.
The preceding bandwidth calculation methods apply to general scenarios. Operators can
calculate the required bandwidth based on site conditions. In addition, the bandwidth
overheads of the transmission protocol must be considered and a 12% bandwidth margin
must be reserved. For example, if the required bandwidth is 3 Mbit/s, the actually
configured bandwidth should be 3 x (1 + 12%) = 3.36 Mbit/s.
NOTE
l You can run the MML command DSP UX2UPINFO to query the delay information of the
uX2-U interface.
l Transmission bandwidth insufficiency will incur packet loss on the uX2 link, affecting the rate
of uX2-based coordinated services. In UMTS/LTE co-transmission scenarios, the bandwidth
requirements for both UMTS and LTE need to be satisfied. For details about LTE bandwidth
requirements, see related feature parameter descriptions for LTE networks.
8.4.3 Data Preparation

This section describes the data to prepare before enabling the uX2 Interface Management
feature. Required data is data that you must collect for all scenarios. Scenario-specific data is
data necessary for a specific feature deployment scenario.
There are three types of data sources. The respective meanings are as follows:
l Network plan (negotiation not required): parameter values planned and set by the
operator
l Network plan (negotiation required): parameter values planned by the operator and
negotiated with the EPC or peer transmission equipment
l User-defined: parameter values set by users
Required Data
This section describes how to prepare data for uX2 self-setup in common scenarios.
Configure the NodeB algorithm parameter MO NODEBALGPARA and specify the uX2
self-setup switch.

WCDMA RAN
Parameter Parameter ID Setting Notes Data Source

Name
uX2 SON Setup UX2SONSETUPSW It is recommended that the Network plan

Switch value of the (negotiation
UX2SONSETUPSW not required)
parameter be unique on the
entire network.
The following table describes the key parameters that must be set in an SCTPTEMPLATE
MO to configure the negotiation parameters of uX2-C transmission links.

Name
SCTP SCTPTEMPLATEI - Network plan

Parameters D (negotiation
Template ID not required)
RTO Min Value RTOMIN - Network plan

(negotiation
not required)
RTO Max Value RTOMAX - Network plan

(negotiation
not required)
RTO Initial RTOINIT - Network plan

Value (negotiation
not required)
RTO Alpha RTOALPHA - Network plan

Value (negotiation
not required)
RTO Beta Value RTOBETA - Network plan

(negotiation
not required)
Heart-beat HBINTER - Network plan

Interval (negotiation
not required)
Max Association MAXASSOCRETR - Network plan

Retransmission (negotiation
not required)
Max Path MAXPATHRETR - Network plan

Retransmission (negotiation
not required)

WCDMA RAN

Name
Switch Back SWITCHBACKFLA - Network plan

Flag G (negotiation
not required)
Heart-beat Times SWITCHBACHHB - Network plan

When Switch NUM (negotiation
Back not required)
SACK Timeout TSACK - Network plan

(negotiation
not required)
Checksum CHKSUMTYPE - Network plan

Arithmetic Type (negotiation
not required)
Maximum MAXSTREAM - Network plan

Stream No. (negotiation
not required)
The following table describes the parameters that must be set in an SCTPHOST MO to
configure local NodeB information of the uX2-C interface.

Name
SCTP Host ID SCTPHOSTID - Network plan

(negotiation
not required)
IP Version IPVERSION - Network plan

(negotiation
not required)
First Local IP SIGIP1V4 - Network plan

Address (negotiation
not required)
IPSec Auto SIGIP1SECSWITC In IPsec-enabled uX2-C self- Network plan

Configure H setup scenarios, if each uX2-C (negotiation
Switch for First interface exclusively uses an not required)
Local IP IPsec tunnel, set this parameter
to ENABLE(Enable).
Security Host ID SIGIP1SECHOSTI Optional, configured only in Network plan

for First Local IP D IPsec-enabled scenarios. (negotiation
not required)

WCDMA RAN

Name
Second Local IP SIGIP2V4 - Network plan

not required)

Configure H setup scenarios, if each uX2-C (negotiation
Switch for interface exclusively uses an not required)
Second Local IP IPsec tunnel, set this parameter
to ENABLE(Enable).
Security Host ID SIGIP2SECHOSTI Optional, configured only in Network plan

for Second Local D IPsec-enabled scenarios. (negotiation
IP not required)
Local SCTP Port PN - Network plan

No. (negotiation
not required)
The following table describes the parameters that must be set in an SCTPPEER MO to
configure peer NodeB information of the uX2-C interface.

Name
SCTP Peer ID SCTPPEERID - Network plan

(negotiation
not required)

(negotiation
not required)
First Peer IP SIGIP1V4 - Network plan

not required)

Configure H setup scenarios, if SCTP peers (negotiation
Switch for First do not share an IPsec tunnel, not required)
Peer IP set this parameter to
ENABLE(Enable).
Security Peer ID SIGIP1SECPEERI Optional, configured only in Network plan

for First Peer IP D IPsec-enabled scenarios. (negotiation
not required)
Second Peer IP SIGIP2V4 - Network plan

not required)

WCDMA RAN

Name

Configure H setup scenarios, if SCTP peers (negotiation
Switch for do not share an IPsec tunnel, not required)
Second Peer IP set this parameter to
ENABLE(Enable).
Security Peer ID SIGIP2SECPEERI Optional, configured only in Network plan

for Second Peer D IPsec-enabled scenarios. (negotiation
IP not required)
Peer SCTP Port PN - Network plan

No. (negotiation
not required)
Control Mode CTRLMODE l If the SCTPPEER MO is Network plan

manually configured, set (negotiation
this parameter to not required)
MANUAL_MODE(Manu
al Mode).
l If the SCTPPEER MO is
automatically configured,
set this parameter to
AUTO_MODE(Auto
Mode).
The following table describes the parameters that must be set in a USERPLANEHOST MO
to configure local NodeB information of the uX2-U interface.

Name
User Plane Host UPHOSTID - Network plan

ID (negotiation
not required)
IP Version IPVERSION If the user plane peer uses Network plan

IPv4, set this parameter to (negotiation
IPv4(IPv4). not required)
Local IP Address LOCIPV4 - Network plan

(negotiation
not required)
IPSec Auto IPSECSWITCH In IPsec-enabled uX2-U self- Network plan

Configure setup scenarios, if all (negotiation
Switch USERPLANEPEER MOs not required)
share an IPsec tunnel, set this
parameter to
ENABLE(Enable).

WCDMA RAN

Name
Security Host ID SECHOSTID - Network plan

(negotiation
not required)
(Optional) The following table describes the parameters that must be set in a
USERPLANEPEER MO to configure peer NodeB information of the uX2-U interface. This
MO needs to be configured only when the uX2-U peer is manually configured.
Parameter Parameter ID Setting Notes Data

Name Source
User Plane Peer UPPEERID - Network plan

ID (negotiation
not required)
IP Version IPVERSION If IPv4 is used for the peer end, Network plan
set this parameter to IPV4. (negotiation
not required)
Peer IP Address PEERIPV4 - Network plan

(negotiation
not required)
IPSec Auto IPSECSWITCH If the USERPLANEPEER Network plan

Configure MO is to be manually (negotiation
Switch configured and each uX2-U not required)
interface exclusively uses an
IPSec tunnel, set this parameter
to ENABLE(Enable).
Security Peer ID SECPEERID Optional, configured only in Network plan

IPsec-enabled scenarios. (negotiation
not required)
Control Mode CTRLMODE l If the USERPLANEPEER Network plan

MO is manually configured, (negotiation
set this parameter to not required)
MANUAL_MODE(Manu
al Mode).
l If the USERPLANEPEER
MO is automatically
configured, set this
parameter to
AUTO_MODE(Auto
Mode).
The following table describes the parameters that must be set in an EPGROUP MO to
configure an endpoint group.

WCDMA RAN

Name
End Point Group EPGROUPID - Network plan

ID (negotiation
not required)
SCTP Host List SCTPHOSTLIST This parameter specifies the Network plan
list of SCTP hosts in the end (negotiation
point group. not required)
SCTP Peer List SCTPPEERLIST This parameter specifies the Network plan
list of SCTP peers in the end (negotiation
point group. not required)
User Plane Host USERPLANEHOS This parameter specifies the Network plan
List TLIST list of user plane hosts in the (negotiation
end point group. not required)
User Plane Peer USERPLANEPEE This parameter specifies the Network plan
List RLIST list of user plane peers in the (negotiation
end point group. not required)
Packet Filter PACKETFILTERS l To enable automatic Network plan

Switch WITCH configuration of ACL rules, (negotiation
ENABLE(Enable).
l To disable automatic
configuration of ACL rules,
set this parameter to
DISABLE(Disable).
Type TYPEFLAG For centralized cloud BB (ideal Network plan

backhaul), set this parameter to (negotiation
CENTRALIZED_uX2. For not required)
other scenarios, set this
parameter to COMMON.
The following table describes the parameters that must be set in the UX2 MO to configure the
relationships with the EPGROUP MO.

Name Source
uX2 ID UX2ID - Network plan

(negotiation
not required)
Control Plane CPEPGROUPID - Network plan

End-Point Group (negotiation
ID not required)

WCDMA RAN

Name Source
User Plane End- UPEPGROUPID - Network plan

Point Group ID (negotiation
not required)
uX2 Object USERLABEL - Network plan

Description (negotiation
not required)
Static Check STATICCHKSW Set this parameter to ON(On). Network plan

Switch (negotiation
not required)
The following table describes the key parameters that must be set in an RSCGRP MO to
configure the transmission resource group.

Name
Cabinet No. CN - Network plan

(negotiation
not required)
Subrack No. SRN - Network plan

(negotiation
not required)
Slot No. SN - Network plan

(negotiation
not required)
Transmission BEAR Set this parameter to IP(IP). Network plan

Resource Group (negotiation
Bear Type not required)
Bearing Port No. PN - Network plan

(negotiation
not required)
Subboard Type SBT Set this parameter to Network plan

BASE_BOARD(Base Board). (negotiation
not required)
Bearing Port PT Set this parameter according to Network plan

Type the actual network topology. (negotiation
not required)
Transmission RSCGRPID - Network plan

ID not required)

WCDMA RAN

Name
Rate Unit RU Set this parameter to KBPS Network plan

(kbit/s). (negotiation
not required)
Tx Bandwidth TXBW - Network plan

(negotiation
not required)
Rx Bandwidth RXBW - Network plan

(negotiation
not required)
TX Committed TXCBS - Network plan

Burst Size (negotiation
not required)
TX Excessive TXEBS - Network plan

Burst Size (negotiation
not required)
Scheduling WEIGHT - Network plan

Weight (negotiation
not required)
TX Committed TXCIR - Network plan

Information Rate (negotiation
not required)
RX Committed RXCIR - Network plan

not required)
TX Peak TXPIR - Network plan

not required)
RX Peak RXPIR - Network plan

not required)
TX Peak Burst TXPBS - Network plan

Size (negotiation
not required)
The following table describes the key parameters that must be set in an EP2RSCGRP MO to
configure the mapping between end points and transmission resource groups.

WCDMA RAN

Name Source
End Point ID ENDPOINTID - Network plan

(negotiation
not required)
Cabinet No. CN - Network plan

(negotiation
not required)
Subrack No. SRN - Network plan

(negotiation
not required)
Slot No. SN - Network plan

(negotiation
not required)
Subboard Type SBT - Network plan

Set this parameter to (negotiation
BASE_BOARD(Base Board). not required)
Bearing Port PT Set this parameter according to Network plan

Type the actual network topology. (negotiation
not required)
Bearing Port No. PN - Network plan

(negotiation
not required)
Transmission BEAR Set this parameter to IP(IP). Network plan

Bear Type not required)
Transmission RSCGRPID - Network plan

ID not required)
The following table describes the parameters that must be set in a UX2CTRLPARA MO to
configure timers for automatic uX2 deletion and dynamic blacklist.

Name
Link-Fault- UX2AutoDeleteFor Set this parameter to ON(On). Network plan

triggered uX2 FaultSw(BSC6900, (negotiation
Auto Delete BSC6910) not required)
Switch

WCDMA RAN

Name
Link-Fault- UX2AutoDeleteFor Set this parameter to 10080. Network plan

triggered uX2 FaultTimer(BSC690 (negotiation
Auto Delete 0,BSC6910) not required)
Timer
uX2 Dynamic UX2DynBlackListS Set this parameter to ON(On). Network plan

Blacklist Switch w(BSC6900,BSC69 (negotiation
10) not required)
uX2 Dynamic UX2DynBlackListA Set this parameter to 420. Network plan

Blacklist Aging gingTimer(BSC690 (negotiation
Timer 0,BSC6910) not required)
Scenario-specific Data
This section describes how to prepare scenario-specific data for a uX2 interface in IPsec-
enabled scenarios.
IPsec can only be manually configured and the ACLRULE MO of the IPsec cannot be
configured with ports.
The following table describes the parameters that must be set in a SECURITYTEMPLATE
MO to configure a security parameter template. This MO applies only to IPsec-enabled
scenarios.

Name
Security SECURITYTEMPL - Network plan

Parameters ATEID (negotiation
SeGW Switch SEGWSWITCH l If the NodeB performs Network plan

IPsec negotiation with the (negotiation
SeGW, set this parameter to not required)
ENABLE(Enable).
l If the NodeB directly
performs IPsec negotiation
with the peer, set this
parameter to
DISABLE(Disable).
IKE Proposal ID PROPID - Network plan

(negotiation
not required)
IPsec Proposal IPSECPROPNAME - Network plan

Name (negotiation
not required)

WCDMA RAN

Name
IKE Version IKEVERSION - Network plan

(negotiation
not required)
The following table describes the parameters that must be set in a SECURITYHOST MO to
configure the parameters related to a security host. This MO applies only to IPsec-enabled
scenarios.

Name
Security Host ID SECURITYHOSTI - Network plan

D (negotiation
not required)

ENABLE(Enable).
parameter to
DISABLE(Disable).
SeGW Config SEGWCONFIGMO l If all uX2 interfaces share Network plan

Mode DE an IPSec tunnel, set this (negotiation
parameter to not required)
SEGW_CONFIG_ON_H
OST.
l If each uX2 interface
exclusively uses an IPSec
tunnel, set this parameter to
SEGW_CONFIG_ON_PE
ER.

(negotiation
not required)
Local IKE IP LOCIKEIPV4 - Network plan

not required)
IKE Peer Name PEERNAME - Network plan

(negotiation
not required)

WCDMA RAN

Name
IPsec Proposal IPSECPROPNAM - Network plan

Name E (negotiation
not required)
Security SECURITYTEMPL - Network plan

Parameters ATEID (negotiation
The following table describes the parameters that must be set in a SECURITYPEER MO to
configure the parameters related to a security peer. This MO applies only to IPsec-enabled
scenarios.

Name
Security Peer ID SECURITYPEERI - Network plan

D (negotiation
not required)

ENABLE(Enable).
parameter to
DISABLE(Disable).

(negotiation
not required)
Peer IKE IP PEERIKEIPV4 - Network plan

not required)
IKE Peer Name PEERNAME - Network plan

(negotiation
not required)
IPsec Proposal IPSECPROPNAM - Network plan

Name E (negotiation
not required)

WCDMA RAN

Name
Control Mode CTRLMODE l If the SECURITYPEER Network plan

MO is manually configured, (negotiation
MANUAL_MODE(Manu
al Mode).
l If the SECURITYPEER
MO is automatically
configured, set this
parameter to
AUTO_MODE(Auto
Mode).
8.4.4 Initial Configuration
8.4.4.1 Using the CME

NOTE
When configuring the uX2 Interface Management feature on the CME, perform a single configuration
first, and then perform a batch modification if required. Configure the parameters of a single object
before a batch modification. Perform a batch modification before logging out of the parameter setting
interface.
Step 1 Configure a single object (such as a cell) on the CME.
Set parameters on the CME according to the operation sequence described in Table 8-2. For
instructions on how to perform the CME single configuration, see CME Single Configuration
Operation Guide.
Step 2 (Optional) Modify objects in batches on the CME. (CME batch modification center)
To modify objects in batches, click on the CME to start the batch modification wizard.
For instructions on how to perform a batch modification through the CME batch modification
center, press F1 while running the wizard to obtain online help.
----End
Table 8-2 Configuring parameters on the CME
SN MO NE Parameter Parameter Configura

Name ID ble in CME
Batch
Modificati
on Center
1 NODEBAL NodeB uX2 SON UX2SONSE Yes

GPARA Setup TUPSW
Switch

WCDMA RAN

Name ID ble in CME
Batch
Modificati
on Center
2 SCTPTEM NodeB SCTP SCTPTEMP Yes

PLATE Parameters LATEID
Template ID RTOMIN
RTO Min RTOMAX
Value
RTOINIT
RTO Max
Value RTOALPH
A
RTO Initial
Value RTOBETA
RTO Alpha HBINTER

Value MAXASSO
RTO Beta CRETR
Value MAXPATH
Heart-beat RETR
Interval SWITCHBA
Max CKFLAG
Association SWITCHBA
Retransmissi CHHBNUM
on TSACK
Max Path CHKSUMT
Retransmissi YPE
on
MAXSTRE
Switch Back AM
Flag
Heart-beat
Times When
Switch Back
SACK
Timeout
Checksum
Arithmetic
Type
Maximum
Stream No.

WCDMA RAN

Name ID ble in CME
Batch
Modificati
on Center
3 SCTPHOS NodeB SCTP Host SCTPHOST Yes

T ID ID
IP Version IPVERSIO
First Local N
IP Address SIGIP1V4
IPSec Auto SIGIP1SEC
Configure SWITCH
Switch for SIGIP1SEC
First Local HOSTID
IP
SIGIP2V4
Security
Host ID for SIGIP2SEC
First Local SWITCH
IP SIGIP2SEC
Second HOSTID
Local IP PN
Address
IPSec Auto
Configure
Switch for
Second
Local IP
Security
Host ID for
Second
Local IP
Local SCTP
Port No.

WCDMA RAN

Name ID ble in CME
Batch
Modificati
on Center
4 SCTPPEER NodeB SCTP Peer SCTPPEER Yes

ID ID
IP Version IPVERSIO
First Peer IP N
Address SIGIP1V4
IPSec Auto SIGIP1SEC
Configure SWITCH
Switch for SIGIP1SEC
First Peer IP PEERID
Security SIGIP2V4
Peer ID for
First Peer IP SIGIP2SEC
SWITCH
Second Peer
IP Address SIGIP2SEC
PEERID
IPSec Auto
Configure PN
Switch for CTRLMOD
Second Peer E
IP
Security
Peer ID for
Second Peer
IP
Peer SCTP
Port No.
Control
Mode
5 USERPLA NodeB User Plane UPHOSTID Yes

NEHOST Host ID IPVERSIO
IP Version N
Local IP LOCIPV4
Address IPSECSWI
IPSec Auto TCH
Configure SECHOSTI
Switch D
Security
Host ID

WCDMA RAN

Name ID ble in CME
Batch
Modificati
on Center
6 USERPLA NodeB User Plane UPPEERID Yes

NEPEER Peer ID IPVERSIO
IP Version N
Peer IP PEERIPV4
Address IPSECSWI
IPSec Auto TCH
Configure SECPEERI
Switch D
Security CTRLMOD
Peer ID E
Control
Mode
7 EPGROUP NodeB End Point EPGROUPI Yes

Group ID D
SCTP Host SCTPHOST
List LIST
SCTP Peer SCTPPEER
List LIST
User Plane USERPLAN
Host List EHOSTLIS
User Plane T
Peer List USERPLAN
Packet Filter EPEERLIS
Switch T
Type PACKETFI
LTERSWIT
CH
TYPEFLAG
8 UX2 NodeB uX2 ID UX2ID Yes

Control CPEPGRO
Plane End- UPID
Point Group UPEPGRO
ID UPID
User Plane USERLABE
End-Point L
Group ID
STATICCH
uX2 Object KSW
Description
Static Check
Switch

WCDMA RAN

Name ID ble in CME
Batch
Modificati
on Center
9 RSCGRP NodeB Cabinet No. CN Yes

Subrack No. SRN
Slot No. SN
Transmissio BEAR
n Resource PN
Group Bear SBT
Type
PT
Bearing Port
No. RSCGRPID
RU
Subboard
Type TXBW
Bearing Port RXBW
Type TXCBS
Transmissio TXEBS
n Resource WEIGHT
Group ID
TXCIR
Rate Unit
RXCIR
Tx
TXPIR
Bandwidth
RXPIR
Rx
Bandwidth TXPBS
TX
Committed
Burst Size
TX
Excessive
Burst Size
Scheduling
Weight
TX
Committed
Information
Rate
RX
Committed
Information
Rate
TX Peak
Information
Rate

WCDMA RAN

Name ID ble in CME
Batch
Modificati
on Center
RX Peak
Information
Rate
TX Peak
Burst Size
10 EP2RSCG NodeB End Point ENDPOINT Yes

RP ID ID
Cabinet No. CN
Subrack No. SRN
Slot No. SN
Subboard SBT
Type PT
Bearing Port PN
Type
BEAR
Bearing Port
No. RSCGRPID
Transmissio
n Resource
Group Bear
Type
Transmissio
n Resource
Group ID
11 UX2CTRL RNC Link-Fault- UX2AutoDe Yes

PARA triggered leteForFaul
uX2 Auto tSw(BSC690
Delete 0,BSC6910)
Switch UX2AutoDe
Link-Fault- leteForFaul
triggered tTimer(BSC
uX2 Auto 6900,BSC69
Delete Timer 10)
uX2 UX2DynBla
Dynamic ckListSw(B
Blacklist SC6900,BS
Switch C6910)
uX2 UX2DynBla
Dynamic ckListAging
Blacklist Timer(BSC6
Aging Timer 900,BSC691
0)

WCDMA RAN
8.4.4.2 Using MML Commands

Run the following commands on the NodeB:
Step 1 Run the MML command SET NODEBALGPARA with uX2 Auto-Setup Switch set to ON.
Step 2 Run the ADD SCTPTEMPLATE command to add an SCTP template.
Step 3 Run the ADD SCTPHOST command to add an SCTP host for uX2 self-setup.
Step 4 (Optional) Run the ADD SCTPPEER command to add an SCTP peer for uX2 self-setup.
Step 5 Run the ADD USERPLANEHOST command to add a user-plane host for uX2 self-setup.
Step 6 (Optional) Run the ADD USERPLANEPEER command to add a user-plane peer for uX2
self-setup.
Step 7 Run the ADD EPGROUP command to add an end point group for uX2 self-setup.
Step 8 Run the ADD SCTPHOST2EPGRP command to add the SCTP host to the end point group
for uX2 self-setup.
Step 9 (Optional) Run the ADD SCTPPEER2EPGRP command to add the control-plane peer to the
end point group for uX2 self-setup.
Step 10 Run the ADD UPHOST2EPGRP command to add the user-plane host to the end point group
for uX2 self-setup.
Step 11 (Optional) Run the ADD UPPEER2EPGRP command to add the user-plane peer to the end
point group for uX2 self-setup.
Step 12 (Optional) Run the ADD RSCGRP command to add a transport resource group for user plane
resource management.
Step 13 (Optional) Run the ADD EP2RSCGRP command to set the mapping from the end point
group to the transport resource group.
Step 14 Run the ADD UX2 command to add a uX2 object. In this command, set the end point group
ID and transmission type and enable uX2 user-plane connectivity checks.
----End
Run the following commands on the RNC:
Step 1 Run the SET UX2CTRLPARA command and set the following parameters: Link-Fault-
triggered uX2 Auto Delete Switch, Link-Fault-triggered uX2 Auto Delete Timer, uX2
Dynamic Blacklist Switch, and uX2 Dynamic Blacklist Aging Timer.
----End
8.4.4.3 MML Command Examples

On the NodeB
l Turning on the switch of uX2 self-setup
SET NODEBALGPARA:UX2SONSETUPSW=ON;
l Adding an SCTP template

WCDMA RAN
ADD SCTPTEMPLATE:SCTPTEMPLATEID=0,SWITCHBACKFLAG=ENABLE;
l Adding a control-plane host for uX2 auto-setup

ADD
SCTPHOST:SCTPHOSTID=888,IPVERSION=IPv4,SIGIP1V4="10.11.111.52",SIGIP1SECSWITCH
=DISABLE,SIGIP2SECSWITCH=DISABLE,PN=2000,SCTPTEMPLATEID=0;
l (Optional) Adding a control-plane peer for uX2 auto-setup

ADD
SCTPPEER:SCTPPEERID=1888,IPVERSION=IPv4,SIGIP1V4="10.10.10.10",SIGIP1SECSWITCH
=DISABLE,SIGIP2SECSWITCH=DISABLE,PN=3000;
l Adding a user-plane host for uX2 self-setup

ADD
USERPLANEHOST:UPHOSTID=2888,IPVERSION=IPv4,LOCIPV4="10.11.211.52",IPSECSWITCH=
DISABLE;
l (Optional) Adding a user-plane peer for uX2 self-setup

ADD
USERPLANEPEER:UPPEERID=3888,IPVERSION=IPv4,PEERIPV4="10.100.100.100",IPSECSWIT
CH=DISABLE;
l Adding an end point group for uX2 self-setup

ADD EPGROUP:EPGROUPID=1000;
l Adding the control-plane host for uX2 self-setup to the end point group
ADD SCTPHOST2EPGRP:EPGROUPID=1000,SCTPHOSTID=888;
l (Optional) Adding the control-plane peer to the end point group for uX2 self-setup
ADD SCTPPEER2EPGRP:EPGROUPID=1000,SCTPPEERID=1888;
l Adding the user-plane host for uX2 self-setup to the end point group
ADD UPHOST2EPGRP:EPGROUPID=1000,UPHOSTID=2888;
l (Optional) Adding the user-plane peer for uX2 self-setup to the end point group
ADD UPPEER2EPGRP:EPGROUPID=1000,UPPEERID=3888;
l (Optional) Adding a transport resource group

ADD RSCGRP:SN=6,BEAR=IP,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0,RU=KBPS;
l (Optional) Adding the mapping between the uX2 end point group and the transport
resource group
ADD EP2RSCGRP:ENDPOINTID=1000,SN=6,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0;
l Add a uX2 object and enable uX2 user-plane connectivity checks.

ADD UX2:UX2ID=0,CPEPGROUPID=1000,UPEPGROUPID=1000,STATICCHKSW=ON;
On the RNC
l Configure auto-deletion and dynamic blacklist for the uX2 interface.

SET
UX2CTRLPARA:UX2AutoDeleteForFaultSw=ON,UX2AutoDeleteForFaultTimer=10080,UX2Dyn
BlackListSw=ON,UX2DynBlackListAgingTimer=420,MaxCoordinatingCellNum=15;
8.4.5 Activation Observation
Querying Through the Web LMT

Signaling tracing can be enabled before the uX2 interface is set up to check whether UX2
self-setup has been activated.
Step 1 Log in to the NodeB WebLMT. Click Trace.
Step 2 In the left navigation tree, choose UMTS Services > uX2 Interface Trace.
Step 3 Create a uX2 tracing task.
Step 4 Check the tracing result, as shown in Figure 8-2.

WCDMA RAN
If information about the source and target NodeBs (such as the NodeB IDs and IP addresses)
is exchanged over the uX2 interface, uX2 self-setup in uX2 over OSS mode has been
activated.
Figure 8-2 Example of traced uX2 messages related to uX2 self-setup
----End
Observing Through MML Command

Run the NodeB MML command DSP UX2INTERFACE to query the value of the
UX2INTERFACESTATE parameter. If the value is Normal(Normal), the uX2 link is
successfully set up.
8.4.6 Deactivation
The feature does not need to be deactivated.
8.4.7 Reconfiguration
NodeBs are reconfigured in batches. For details, see the reconfiguration guide for NodeBs.
8.5 Performance Monitoring

The real-time traffic information over the uX2 interface can be obtained through the IP PM
real-time performance monitoring on the NodeB WebLMT.
The detailed operations are as follows:
1. Add an IP PM session. The IP address of the IP PM session is the same as the local and
peer IP addresses of the uX2 link.
ADD IPPMSESSION: IPPMSN=0, IPPMTYPE=FOUR_TUPLE, BINDPATH=NO,
LOCALIP="10.11.211.52", PEERIP="10.100.100.100", DIR=UP;
2. On the NodeB LMT, click Monitor. The Monitor page is displayed.

3. In the Monitor Navigation Tree pane, choose Monitor > Common Monitoring >
Transport Auto Setup User Plane Monitoring.
In the displayed Link Performance Monitoring dialog box, set IPPM flag to User
Plane Link, enter a virtual route instance, source IP address, and destination IP address,
and click Yes.
4. Double-click the corresponding task to view the uX2 real-time traffic measurement
result.

WCDMA RAN
Viewing the traffic and packet loss performance of the uX2 interface
On the NodeB, run the MML command ADD IPPMSESSION to add an IP PM
session. View the values of VS.IPPM.Local.TxPkts and VS.IPPM.Peer.RxPkts of
the IP PM session to check the traffic and packet loss performance of the uX2
interface.
ADD
IPPMSESSION:IPPMSN=0,IPPMTYPE=FOUR_TUPLE,BINDPATH=NO,LOCALIP="10.11.211.5
2",PEERIP="10.100.100.100",DIR=UP;
Viewing the total traffic over the uX2 interface and NodeB
If the uX2 interface and the Iub interface use the same IP address, run the MML
commands ADD RSCGRP and ADD EP2RSCGRP on the NodeB to add a
transmission resource group for the uX2 interface. View the values of
VS.RscGroup.TxBytes and VS.IP.TxBytes to check the traffic over the uX2
interface and the total traffic over the NodeB configured with the uX2 interface.
ADD RSCGRP:SN=6,BEAR=IP,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0,RU=KBPS;
ADD EP2RSCGRP:ENDPOINTID=1000,SN=6,SBT=BASE_BOARD,PT=ETH,RSCGRPID=0;
If the uX2 interface and the Iub interface use different IP addresses, view the value
of VS.IP.TxBytes to check the traffic over the uX2 interface.
8.6 Parameter Optimization

N/A
8.7 Troubleshooting
If the uX2 interface is faulty, check whether the alarm listed in Table 8-3 is generated. If this
alarm is generated, clear the alarm by referring to the related alarm reference.
Table 8-3 Alarm related to the uX2 interface
Alarm ID Alarm Name Alarm Severity
25888 SCTP Link Fault Major

WCDMA RAN
Alarm ID Alarm Name Alarm Severity
25952 User Plane Path Fault Major

WCDMA RAN
uX2 Interface Management Feature Parameter Description 9 Parameters
9 Parameters
Table 9-1 Parameters

Parame NE MML Feature Feature Description
ter ID Comma ID Name
nd
SIGIP1 BTS390 ADD LOFD-0 Self- Meaning: Indicates the first local SCTP IPv4 address,
V4 0, SCTPH 02004 / configur which is used by the base station to establish a
BTS390 OST TDLOF ation signaling channel. That is, this address is the first local
0 MOD D-00200 IPv4 address for automatically establishing an SCTP
WCDM SCTPH 4 link.
A, OST GUI Value Range: Valid IP address
BTS390
0 LTE LST Unit: None
SCTPH Actual Value Range: Valid IP address
OST
Default Value: None
SIGIP1 BTS390 ADD LOFD-0 Self- Meaning: Indicates the first peer SCTP IPv4 address,
V4 0, SCTPPE 02004 / configur which is used by the base station to establish a
BTS390 ER TDLOF ation signaling channel. That is, this address is the first peer
0 MOD D-00200 IPv4 address for automatically establishing an SCTP
WCDM SCTPPE 4 link.
A, ER GUI Value Range: Valid IP address
BTS390
SCTPPE Actual Value Range: Valid IP address
ER
Default Value: None
USERL BTS390 ADD LOFD-0 Self- Meaning: Indicates the description of the SCTP peer.
ABEL 0, SCTPPE 02004 / configur GUI Value Range: 0~256 characters
BTS390 ER TDLOF ation
0 D-00200 Unit: None
MOD
WCDM SCTPPE 4 Actual Value Range: 0~256 characters
A, ER Default Value: NULL(empty string)
BTS390
0 LTE LST
SCTPPE
ER

WCDMA RAN

nd
USERL BTS390 ADD WRFD- IP Meaning: Indicates the information about a user-plane
ABEL 0, USERP 050402 Transmi peer.
BTS390 LANEP ssion GUI Value Range: 0~256 characters
0 EER GBFD-1 Introduc
WCDM 18601 tion on Unit: None
MOD
A, USERP LOFD-0 Iub Actual Value Range: 0~256 characters
BTS390 LANEP 02004 / Interface Default Value: NULL(empty string)
0 LTE EER TDLOF Abis
LST D-00200 over IP
USERP 4
LANEP Self-
EER configur
ation
DESCRI BTS390 ADD WRFD- IP Meaning: Indicates the peer description information of
0, SCTPL 050402 Transmi the SCTP link.
BTS390 NK ssion GUI Value Range: 0~47 characters
0 GBFD-1 Introduc
MOD 18601 Unit: None
WCDM SCTPL tion on
A, NK GBFD-1 Iub Actual Value Range: 0~47 characters
BTS390 18611 Interface Default Value: NULL(empty string)
0 LTE LST
SCTPL LBFD-0 Abis
NK 0202103 over IP
/ Abis IP
TDLBF over
D-00202 E1/T1
103
SCTP
Multi-
homing
UX2Aut BSC690 SET None None Meaning: Whether to automatically delete a faulty
oDelete 0 UX2CT uX2 interface. When this switch is set to ON, a faulty
ForFault RLPAR uX2 interface will be automatically deleted to release
Sw A uX2 interface resources if the uX2 interface remains
faulty for a period of time specified by
UX2AutoDeleteForFaultTimer. When this switch is
set to OFF, faulty uX2 interfaces cannot be
automatically deleted.
GUI Value Range: OFF, ON
Unit: None
Actual Value Range: OFF, ON
Default Value: OFF

WCDMA RAN

nd
UX2Aut BSC691 SET None None Meaning: Whether to automatically delete a faulty
oDelete 0 UX2CT uX2 interface. When this switch is set to ON, a faulty
ForFault RLPAR uX2 interface will be automatically deleted to release
Sw A uX2 interface resources if the uX2 interface remains
faulty for a period of time specified by
UX2AutoDeleteForFaultTimer. When this switch is
set to OFF, faulty uX2 interfaces cannot be
automatically deleted.
Unit: None
Default Value: OFF
UX2Aut BSC690 SET None None Meaning: Timer for a faulty uX2 interface to be
oDelete 0 UX2CT automatically deleted. If a uX2 interface remains
ForFault RLPAR faulty for a period of time specified by this timer, the
Timer A interface will be deleted. If this parameter is set to a
small value, the condition for uX2 interface deletion
can be easily met, leading to repetitive uX2 deletion
and self-setup. If this parameter is set to a large value,
the condition for uX2 interface deletion is difficult to
meet. Consequently, faulty uX2 interfaces cannot be
deleted in a timely manner to release uX2 interface
resources, hampering new uX2 interface setup.
GUI Value Range: 1~50400
Unit: min
Actual Value Range: 1~50400
Default Value: 10080
UX2Aut BSC691 SET None None Meaning: Timer for a faulty uX2 interface to be
oDelete 0 UX2CT automatically deleted. If a uX2 interface remains
ForFault RLPAR faulty for a period of time specified by this timer, the
Timer A interface will be deleted. If this parameter is set to a
small value, the condition for uX2 interface deletion
can be easily met, leading to repetitive uX2 deletion
and self-setup. If this parameter is set to a large value,
the condition for uX2 interface deletion is difficult to
meet. Consequently, faulty uX2 interfaces cannot be
deleted in a timely manner to release uX2 interface
resources, hampering new uX2 interface setup.
Unit: min

WCDMA RAN

nd
UX2Dy BSC690 SET None None Meaning: Whether the uX2 dynamic blacklist function
nBlackL 0 UX2CT takes effect. When this switch is set to ON, faulty uX2
istSw RLPAR interfaces that are initially set up through a uX2 self-
A setup process can be deleted to release uX2 interface
resources. In this situation, if a peer NodeB is in the
dynamic blacklist, the uX2 interface to the peer
NodeB cannot be set up through a uX2 self-setup
process. When this switch is set to OFF, faulty uX2
interfaces that are initially set up through a uX2 self-
setup process cannot be deleted to release uX2
interface resources. In this situation, if all uX2
interface resources are occupied, a new uX2 interface
can be set up only after an existing uX2 interface
meets the condition for automatic deletion and is
deleted.
Unit: None
Default Value: OFF
UX2Dy BSC691 SET None None Meaning: Whether the uX2 dynamic blacklist function
nBlackL 0 UX2CT takes effect. When this switch is set to ON, faulty uX2
istSw RLPAR interfaces that are initially set up through a uX2 self-
A setup process can be deleted to release uX2 interface
resources. In this situation, if a peer NodeB is in the
dynamic blacklist, the uX2 interface to the peer
NodeB cannot be set up through a uX2 self-setup
process. When this switch is set to OFF, faulty uX2
interfaces that are initially set up through a uX2 self-
setup process cannot be deleted to release uX2
interface resources. In this situation, if all uX2
interface resources are occupied, a new uX2 interface
can be set up only after an existing uX2 interface
meets the condition for automatic deletion and is
deleted.
Unit: None
Default Value: OFF

WCDMA RAN

nd
UX2Dy BSC690 SET None None Meaning: uX2 dynamic blacklist aging timer. If a uX2
nBlackL 0 UX2CT interface stays in the dynamic blacklist for a time
istAging RLPAR longer than that specified by this parameter, the uX2
Timer A interface will be removed from the blacklist. If this
parameter is set to a small value, uX2 self-setup will
be frequently performed, resulting in excessive uX2
self-setup messages. If this parameter is set to a large
value, uX2 self-setup will be performed a long time
after uX2 interface deletion even though the fault has
been rectified.
Unit: min
Default Value: 420
UX2Dy BSC691 SET None None Meaning: uX2 dynamic blacklist aging timer. If a uX2
nBlackL 0 UX2CT interface stays in the dynamic blacklist for a time
istAging RLPAR longer than that specified by this parameter, the uX2
Timer A interface will be removed from the blacklist. If this
parameter is set to a small value, uX2 self-setup will
be frequently performed, resulting in excessive uX2
self-setup messages. If this parameter is set to a large
value, uX2 self-setup will be performed a long time
after uX2 interface deletion even though the fault has
been rectified.
Unit: min
Default Value: 420
UX2SO BTS390 SET None None Meaning: Indicates whether to enable the uX2
NSETU 0, NODEB automatic setup function. If this parameter is set to
PSW BTS390 ALGPA ON, the NodeB supports automatic uX2 setup by the
0 RA OSS. If this parameter is set to OFF, uX2 links must
WCDM LST be manually set up.
A NODEB GUI Value Range: OFF(OFF), ON(ON)
ALGPA Unit: None
RA
Default Value: ON(ON)

WCDMA RAN

nd
SEGWS BTS390 ADD WRFD- IP Meaning: Indicates whether to enable the peer end to
WITCH 0, SECURI 050402 Transmi perform IPSec negotiation with the local end through
BTS390 TYTEM WRFD- ssion an SeGW. When this parameter is set to DISABLE,
0 PLATE 140209 Introduc the peer end performs IPSec negotiation with the local
WCDM MOD tion on end directly. When this parameter is set to ENABLE,
A, SECURI GBFD-1 Iub the peer end establishes an IPSec tunnel to the local
BTS390 TYTEM 18601 Interface end through the SeGW.
0 LTE PLATE NodeB GUI Value Range: DISABLE(Disable),
GBFD-1
LST 13524 Integrate ENABLE(Enable)
SECURI d IPSec Unit: None
TYTEM LOFD-0
Abis Actual Value Range: DISABLE, ENABLE
PLATE 02004 /
over IP Default Value: DISABLE(Disable)
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
BTS390 TYHOS WRFD- ssion an SeGW. When this parameter is set to DISABLE,
0 T 140209 Introduc the peer end performs IPSec negotiation with the local
BTS390 TYHOS 18601 Interface end through a SeGW.
0 LTE T NodeB GUI Value Range: DISABLE(Disable),
GBFD-1
TYHOS LOFD-0
T 02004 /
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN

nd
SEGWC BTS390 ADD WRFD- IP Meaning: Indicates the configuration mode of the
ONFIG 0, SECURI 050402 Transmi security gateway.
MODE BTS390 TYHOS WRFD- ssion GUI Value Range:
0 T 140209 Introduc SEGW_CONFIG_ON_HOST(SeGW Config on
WCDM MOD tion on Host), SEGW_CONFIG_ON_PEER(SeGW Config
A, SECURI GBFD-1 Iub on Peer)
BTS390 TYHOS 18601 Interface
0 LTE Unit: None
T GBFD-1 NodeB
Integrate Actual Value Range: SEGW_CONFIG_ON_HOST,
LST 13524 SEGW_CONFIG_ON_PEER
SECURI d IPSec
TYHOS LOFD-0 Default Value: SEGW_CONFIG_ON_PEER(SeGW
Abis Config on Peer)
T 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
SECURI BTS390 ADD WRFD- IP Meaning: Indicates the ID of the security parameters
TYTEM 0, SECURI 050402 Transmi template referenced by the security host.
PLATEI BTS390 TYHOS WRFD- ssion GUI Value Range: 0~65535
D 0 T 140209 Introduc
WCDM tion on Unit: None
MOD
A, SECURI GBFD-1 Iub Actual Value Range: 0~65535
BTS390 TYHOS 18601 Interface Default Value: None
0 LTE T NodeB
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYHOS LOFD-0
Abis
T 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN

nd
SECURI BTS390 ADD WRFD- IP Meaning: Indicates the ID of the security parameter
TYTEM 0, SECURI 050402 Transmi template.
PLATEI BTS390 TYTEM WRFD- ssion GUI Value Range: 0~65535
D 0 PLATE 140209 Introduc
LST
A, SECURI GBFD-1 Iub Actual Value Range: 0~65535
BTS390 TYTEM 18601 Interface Default Value: None
0 LTE PLATE NodeB
GBFD-1
MOD 13524 Integrate
SECURI d IPSec
TYTEM LOFD-0
Abis
PLATE 02004 /
over IP
TDLOF
RMV BTS
D-00200
SECURI Integrate
4
TYTEM d Ipsec
PLATE LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
SIGIP1S BTS390 ADD LOFD-0 Self- Meaning: Indicates whether to enable automatic setup
ECSWI 0, SCTPH 02004 / configur of an IPSec tunnel between the local end and the peer
TCH BTS390 OST TDLOF ation end based on the SECURITYHOST and
0 MOD D-00200 Ipsec SECURITYPEER MOs. The IPSec tunnel is used to
WCDM SCTPH 4 encrypt the data to be transmitted on the Stream
A, OST LOFD-0 Control Transmission Protocol (SCTP) link that is set
BTS390 03009 / up using the First Local IP Address of the SCTP host
0 LTE LST or the data to be transmitted on the IPv6 SCTP link
SCTPH TDLOF
D-00300 that is set up using the First Local IPv6 Address of the
OST SCTP host.
9
GUI Value Range: DISABLE(Disable),
ENABLE(Enable)
Unit: None
Actual Value Range: DISABLE, ENABLE
Default Value: DISABLE(Disable)

WCDMA RAN

nd
ECSWI 0, SCTPH 02004 / configur of an IPSec tunnel between the local end and the peer
TCH BTS390 OST TDLOF ation end based on the SECURITYHOST and
WCDM SCTPH 4 encrypt the data to be transmitted on the Stream
A, OST LOFD-0 Control Transmission Protocol (SCTP) link that is set
BTS390 03009 / up using the Second Local IP Address of the sctp host
0 LTE LST or the data to be transmitted on the IPv6 SCTP link
SCTPH TDLOF
D-00300 that is set up using the Second Local IPv6 Address of
OST the sctp host.
9
ENABLE(Enable)
Unit: None
SIGIP1S BTS390 ADD LOFD-0 Self- Meaning: Indicates the ID of the security host
ECHOS 0, SCTPH 02004 / configur referenced by the first IP address of the SCTP host.
TID BTS390 OST TDLOF ation GUI Value Range: 0~65535
0 MOD D-00200 Ipsec
WCDM 4 Unit: None
SCTPH
A, OST LOFD-0 Actual Value Range: 0~65535
BTS390 03009 / Default Value: None
0 LTE LST
SCTPH TDLOF
OST D-00300
9

WCDMA RAN

nd
SECURI BTS390 ADD WRFD- IP Meaning: Indicates the security host ID.
TYHOS 0, SECURI 050402 Transmi GUI Value Range: 0~65535
TID BTS390 TYHOS WRFD- ssion
0 T Introduc Unit: None
140209
WCDM LST tion on Actual Value Range: 0~65535
A, SECURI GBFD-1 Iub Default Value: None
0 LTE T NodeB
GBFD-1
MOD 13524 Integrate
SECURI d IPSec
TYHOS LOFD-0
Abis
T 02004 /
over IP
TDLOF
RMV BTS
D-00200
SECURI Integrate
4
TYHOS d Ipsec
T LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
SIGIP2S BTS390 ADD LOFD-0 Self- Meaning: Indicates the ID of the security host
ECHOS 0, SCTPH 02004 / configur referenced by the second IP address of the SCTP host.
TID BTS390 OST TDLOF ation GUI Value Range: 0~65535
0 MOD D-00200 Ipsec
WCDM 4 Unit: None
SCTPH
A, OST LOFD-0 Actual Value Range: 0~65535
0 LTE LST
SCTPH TDLOF
OST D-00300
9

WCDMA RAN

nd
IPSECP BTS390 ADD WRFD- IP Meaning: Indicates the name of the IPSec proposal
ROPNA 0, SECURI 050402 Transmi used for IPSec negotiation between the local end and
ME BTS390 TYPEE WRFD- ssion the security gateway (SeGW).
0 R 140209 Introduc GUI Value Range: 1~15 characters
WCDM MOD tion on
A, Iub Unit: None
SECURI GBFD-1
BTS390 TYPEE 18601 Interface Actual Value Range: 1~15 characters
0 LTE R NodeB Default Value: None
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYPEE LOFD-0
Abis
R 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
PROPN BTS390 ADD LOFD-0 IPsec Meaning: Indicates the name of the IPSec proposal.
AME 0, IPSECP 03009 / GUI Value Range: 1~15 characters
BTS390 ROPOS TDLOF BTS
0 AL D-00300 Integrate Unit: None
WCDM 9 d Ipsec Actual Value Range: 1~15 characters
DSP
A, IPSECP NodeB Default Value: None
BTS390 GBFD-1
ROPOS 13524 Integrate
0 LTE AL d IPSec
LST WRFD-
IPSECP 140209
ROPOS
AL
MOD
IPSECP
ROPOS
AL
RMV
IPSECP
ROPOS
AL

WCDMA RAN

nd
PEERN BTS390 ADD WRFD- IP Meaning: Indicates the name of the IKE peer. The
AME 0, SECURI 050402 Transmi IKE peer is the security gateway that performs IKE
BTS390 TYPEE WRFD- ssion negotiation with the local end.
0 R 140209 Introduc GUI Value Range: 1~15 characters
WCDM MOD tion on
A, Iub Unit: None
SECURI GBFD-1
BTS390 TYPEE 18601 Interface Actual Value Range: 1~15 characters
0 LTE R NodeB Default Value: None
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYPEE LOFD-0
Abis
R 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
PEERN BTS390 ADD LOFD-0 IPsec Meaning: Indicates the name of the IKE peer.
AME 0, IKEPEE 03009 / GUI Value Range: 1~15 characters
BTS390 R TDLOF BTS
0 D-00300 Integrate Unit: None
DSP d Ipsec
WCDM IKEPEE 9 Actual Value Range: 1~15 characters
A, R NodeB Default Value: None
BTS390 GBFD-1
LST 13524 Integrate
0 LTE d IPSec
IKEPEE
R WRFD-
140209
MOD
IKEPEE
R
RMV
IKEPEE
R

WCDMA RAN

nd
ECSWI 0, SCTPPE 02004 / configur of an IPSec tunnel between the local end and the peer
TCH BTS390 ER TDLOF ation end based on the SECURITYHOST and
WCDM SCTPPE 4 encrypt the data to be transmitted on the Stream
A, ER LOFD-0 Control Transmission Protocol (SCTP) link that is set
BTS390 03009 / up using the First Peer IP Address of the SCTP peer or
0 LTE LST the data to be transmitted on the IPv6 SCTP link that
SCTPPE TDLOF
D-00300 is set up using the First Peer IPv6 Address of the
ER SCTP peer.
9
ENABLE(Enable)
Unit: None
ECSWI 0, SCTPPE 02004 / configur of an IPSec tunnel between the local end and the peer
TCH BTS390 ER TDLOF ation end based on the SECURITYHOST and
WCDM SCTPPE 4 encrypt the data to be transmitted on the Stream
A, ER LOFD-0 Control Transmission Protocol (SCTP) link that is set
BTS390 03009 / up using the Second Peer IP Address of the SCTP
0 LTE LST peer or the data to be transmitted on the IPv6 SCTP
SCTPPE TDLOF
D-00300 link that is set up using the Second Peer IPv6 Address
ER of the SCTP peer.
9
ENABLE(Enable)
Unit: None
SIGIP1S BTS390 ADD LOFD-0 Self- Meaning: Indicates the ID of the security peer
ECPEE 0, SCTPPE 02004 / configur referenced by the first IP address of the SCTP peer.
RID BTS390 ER TDLOF ation GUI Value Range: 0~65535,70000~79999
0 MOD D-00200 Ipsec
WCDM 4 Unit: None
SCTPPE
A, ER LOFD-0 Actual Value Range: 0~65535,70000~79999
0 LTE LST
SCTPPE TDLOF
ER D-00300
9

WCDMA RAN

nd
SECURI BTS390 ADD WRFD- IP Meaning: Indicates the ID of a security peer. The
TYPEE 0, SECURI 050402 Transmi value of SECURITYPEERID in the
RID BTS390 TYPEE WRFD- ssion SECURITYPEER MOs configured by users ranges
0 R 140209 Introduc from 0 to 65535. The value of SECURITYPEERID in
WCDM LST tion on the SECURITYPEER MOs configured by the system
A, SECURI GBFD-1 Iub ranges from 70000 to 79999.
BTS390 TYPEE 18601 Interface GUI Value Range: 0~65535,70000~79999
0 LTE R NodeB
GBFD-1 Unit: None
MOD 13524 Integrate
d IPSec Actual Value Range: 0~65535,70000~79999
SECURI
TYPEE LOFD-0 Default Value: None
Abis
R 02004 /
over IP
TDLOF
RMV BTS
D-00200
SECURI Integrate
4
TYPEE d Ipsec
R LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
SIGIP2S BTS390 ADD LOFD-0 Self- Meaning: Indicates the ID of the security peer
ECPEE 0, SCTPPE 02004 / configur referenced by the second IP address of the SCTP peer.
RID BTS390 ER TDLOF ation GUI Value Range: 0~65535,70000~79999
0 MOD D-00200 Ipsec
WCDM 4 Unit: None
SCTPPE
A, ER LOFD-0 Actual Value Range: 0~65535,70000~79999
0 LTE LST
SCTPPE TDLOF
ER D-00300
9

WCDMA RAN

nd
IPSECS BTS390 ADD WRFD- IP Meaning: Indicates whether to enable the security
WITCH 0, USERP 050402 Transmi automatic setup funciton on the user plane. When this
BTS390 LANEH WRFD- ssion parameter is set to ENABLE, an IPSec tunnel is
0 OST 140209 Introduc automatically set up between the local and peer ends
WCDM MOD tion on based on the SECURITYHOST and
A, USERP GBFD-1 Iub SECURITYPEER MOs. The IPSec tunnel encrypts
BTS390 LANEH 18601 Interface data on it to ensure its security.
0 LTE OST NodeB GUI Value Range: DISABLE(Disable),
GBFD-1
USERP d IPSec Unit: None
LANEH LOFD-0
OST 02004 /
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
SECHO BTS390 ADD WRFD- IP Meaning: Indicates the security host ID used by the
STID 0, USERP 050402 Transmi user-plane host.
BTS390 LANEH WRFD- ssion GUI Value Range: 0~65535
0 OST 140209 Introduc
MOD
A, USERP GBFD-1 Iub Actual Value Range: 0~65535
BTS390 LANEH 18601 Interface Default Value: None
0 LTE OST NodeB
GBFD-1
LST 13524 Integrate
USERP d IPSec
LANEH LOFD-0
Abis
OST 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN

nd
IPSECS BTS390 ADD WRFD- IP Meaning: Indicates whether to enable the security
WITCH 0, USERP 050402 Transmi automatic setup function on the user plane. When this
BTS390 LANEP WRFD- ssion parameter is set to ENABLE, an IPSec tunnel is
0 EER 140209 Introduc automatically set up between the local and peer ends
WCDM MOD tion on based on the SECURITYHOST and
A, USERP GBFD-1 Iub SECURITYPEER MOs. The IPSec tunnel encrypts
BTS390 LANEP 18601 Interface data on it to ensure its security.
0 LTE EER NodeB GUI Value Range: DISABLE(Disable),
GBFD-1
USERP d IPSec Unit: None
LANEP LOFD-0
EER 02004 /
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
SECPE BTS390 ADD WRFD- IP Meaning: Indicates the security peer ID used by the
ERID 0, USERP 050402 Transmi user-plane peer.
BTS390 LANEP WRFD- ssion GUI Value Range: 0~65535,70000~79999
0 EER 140209 Introduc
MOD
A, USERP GBFD-1 Iub Actual Value Range: 0~65535,70000~79999
BTS390 LANEP 18601 Interface Default Value: None
0 LTE EER NodeB
GBFD-1
LST 13524 Integrate
USERP d IPSec
LANEP LOFD-0
Abis
EER 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN

nd
IPSECP BTS390 ADD WRFD- IP Meaning: Indicates the name of the IPSec proposal
ROPNA 0, SECURI 050402 Transmi used for IPSec negotiation between the local end and
ME BTS390 TYHOS WRFD- ssion the security gateway (SeGW).
0 T 140209 Introduc GUI Value Range: 1~15 characters
WCDM MOD tion on
A, Iub Unit: None
SECURI GBFD-1
BTS390 TYHOS 18601 Interface Actual Value Range: 1~15 characters
0 LTE T NodeB Default Value: None
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYHOS LOFD-0
Abis
T 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
PEERN BTS390 ADD WRFD- IP Meaning: Indicates the name of the IKE peer.
AME 0, SECURI 050402 Transmi GUI Value Range: 1~15 characters
BTS390 TYHOS WRFD- ssion
0 T Introduc Unit: None
140209
WCDM MOD tion on Actual Value Range: 1~15 characters
0 LTE T NodeB
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYHOS LOFD-0
Abis
T 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN

nd
IPSECP BTS390 ADD WRFD- IP Meaning: Indicates the name of the IPSec proposal.
ROPNA 0, SECURI 050402 Transmi GUI Value Range: 1~15 characters
ME BTS390 TYTEM WRFD- ssion
0 PLATE Introduc Unit: None
140209
WCDM MOD tion on Actual Value Range: 1~15 characters
BTS390 TYTEM 18601 Interface
0 LTE PLATE NodeB
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYTEM LOFD-0
Abis
PLATE 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
PROPID BTS390 ADD WRFD- IP Meaning: Indicates the ID of the IKE proposal.
0, SECURI 050402 Transmi GUI Value Range: 1~99
BTS390 TYTEM WRFD- ssion
0 PLATE Introduc Unit: None
140209
WCDM MOD tion on Actual Value Range: 1~99
BTS390 TYTEM 18601 Interface
0 LTE PLATE NodeB
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYTEM LOFD-0
Abis
PLATE 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN

nd
PROPID BTS390 ADD LOFD-0 IPsec Meaning: Indicates the ID of the IKE proposal.
0, IKEPR 03009 / GUI Value Range: 1~99
BTS390 OPOSA TDLOF BTS
0 L D-00300 Integrate Unit: None
WCDM 9 d Ipsec Actual Value Range: 1~99
DSP
A, IKEPR NodeB Default Value: None
BTS390 GBFD-1
OPOSA 13524 Integrate
0 LTE L d IPSec
LST WRFD-
IKEPR 140209
OPOSA
L
MOD
IKEPR
OPOSA
L
RMV
IKEPR
OPOSA
L
BTS390 TYPEE WRFD- ssion an SeGW. When this parameter is set to DISABLE,
0 R 140209 Introduc the peer end performs IPSec negotiation with the local
BTS390 TYPEE 18601 Interface end through the SeGW.
0 LTE R NodeB GUI Value Range: DISABLE(Disable),
GBFD-1
TYPEE LOFD-0
R 02004 /
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN

nd
PACKE BTS390 ADD WRFD- IP Meaning: Indicates whether to enable the ACL rule
TFILTE 0, EPGRO 050402 Transmi self-configuration function for packet filtering. When
RSWIT BTS390 UP ssion this parameter is set to ENABLE, the system
CH 0 GBFD-1 Introduc automatically generates packet filtering rules for all
MOD 18601
WCDM EPGRO tion on links of the local end point. If this parameter is set to
A, UP LOFD-0 Iub DISABLE, the system does not generate packet
BTS390 03014 / Interface filtering rules.
0 LTE LST
EPGRO TDLOF Abis GUI Value Range: DISABLE(Disable),
UP D-00301 over IP ENABLE(Enable)
4 Unit: None
LOFD-0 Integrate
d Actual Value Range: DISABLE, ENABLE
02004 /
TDLOF Firewall Default Value: DISABLE(Disable)
D-00200 Self-
4 configur
ation
SCTPT BTS390 ADD LOFD-0 Self- Meaning: Indicates the ID of the SCTP parameter
EMPLA 0, SCTPT 02004 / configur template.
TEID BTS390 EMPLA TDLOF ation GUI Value Range: 0~65535
0 TE D-00200
WCDM 4 Unit: None
LST
A, SCTPT Actual Value Range: 0~65535
BTS390 EMPLA Default Value: None
0 LTE TE
MOD
SCTPT
EMPLA
TE
RMV
SCTPT
EMPLA
TE
RTOMI BTS390 ADD LOFD-0 Self- Meaning: Indicates the minimum value of the
N 0, SCTPT 02004 / configur retransmission timeout (RTO). According to the SCTP
BTS390 EMPLA TDLOF ation protocol, if the calculated RTO is less than this
0 TE D-00200 parameter value, the round trip delay is set to this
WCDM MOD 4 parameter value to reduce the probability of
A, SCTPT retransmission timeout.
BTS390 EMPLA GUI Value Range: 10~59999
0 LTE TE Unit: ms
LST Actual Value Range: 10~59999
SCTPT
EMPLA Default Value: 1000
TE

WCDMA RAN

nd
RTOMA BTS390 ADD LOFD-0 Self- Meaning: Indicates the maximum value of the
X 0, SCTPT 02004 / configur retransmission timeout (RTO). According to the SCTP
BTS390 EMPLA TDLOF ation protocol, it is the upper limit for the doubling
0 TE D-00200 operation of the retransmission timeout timer.
WCDM MOD 4 GUI Value Range: 11~60000
A, SCTPT
BTS390 Unit: ms
EMPLA
0 LTE TE Actual Value Range: 11~60000
LST Default Value: 3000

SCTPT
EMPLA
TE
RTOINI BTS390 ADD LOFD-0 Self- Meaning: Indicates the initial value of the
T 0, SCTPT 02004 / configur Retransmission TimeOut (RTO). It is used as the
BTS390 EMPLA TDLOF ation initial value when calculating the retransmission
0 TE D-00200 timeout in the SCTP protocol.
WCDM MOD 4 GUI Value Range: 10~59999
A, SCTPT
BTS390 Unit: ms
EMPLA
0 LTE TE Actual Value Range: 10~59999
LST Default Value: 1000

SCTPT
EMPLA
TE
RTOAL BTS390 ADD LOFD-0 Self- Meaning: Indicates the alpha value related to RTO of
PHA 0, SCTPT 02004 / configur the SCTP link. The larger the parameter value, the
BTS390 EMPLA TDLOF ation more insensitive services to the link delay. For details
0 TE D-00200 about the RtoAlpha parameter, see RFC4960. The
WCDM MOD 4 parameter value is used as smooth factor for
A, SCTPT calculating the round-trip delay in the SCTP protocol.
BTS390 EMPLA In a new estimation, (RtoAlpha/100) is obtained based
0 LTE TE on a new measurement and 1-(RtoAlpha/100) is
obtained based on the last estimation.
LST
SCTPT GUI Value Range: 1~99
EMPLA Unit: None
TE Actual Value Range: 1~99
Default Value: 12

WCDMA RAN

nd
RTOBE BTS390 ADD LOFD-0 Self- Meaning: Indicates the beta value related to RTO of
TA 0, SCTPT 02004 / configur the SCTP link. This parameter is used to calculate the
BTS390 EMPLA TDLOF ation Round Trip Time Variation (RTTVAR). A larger value
0 TE D-00200 indicates that the latest change is more important. For
WCDM MOD 4 definitions of the beta value, see RFC4960.
A, SCTPT GUI Value Range: 1~99
BTS390 EMPLA
0 LTE Unit: None
TE
LST
SCTPT Default Value: 25
EMPLA
TE
HBINT BTS390 ADD LOFD-0 Self- Meaning: Indicates the heartbeat interval,
ER 0, SCTPT 02004 / configur corresponding to the HBINTER parameter specified
BTS390 EMPLA TDLOF ation in RFC4960. SCTP periodically transmits heartbeat
0 TE D-00200 messages to an idle destination address to detect the
WCDM MOD 4 reachability. According to RFC4960, the actual
A, SCTPT interval at which heartbeat messages are transmitted
BTS390 EMPLA equals the parameter value (HBINTER) plus the
0 LTE TE retransmission timeout (RTO).
LST GUI Value Range: 1000~60000
SCTPT Unit: ms
EMPLA Actual Value Range: 1000~60000
TE
Default Value: 5000
MAXA BTS390 ADD LOFD-0 Self- Meaning: Indicates the maximum number of
SSOCR 0, SCTPT 02004 / configur retransmissions on the association of an SCTP link. If
ETR BTS390 EMPLA TDLOF ation the number of retransmissions on the SCTP link
0 TE D-00200 reaches this parameter value, this SCTP link is
WCDM MOD 4 considered broken and the eNodeB reports a link
A, SCTPT failure alarm.
0 LTE TE Unit: None
SCTPT
TE

WCDMA RAN

nd
MAXPA BTS390 ADD LOFD-0 Self- Meaning: Indicates the maximum number of
THRET 0, SCTPT 02004 / configur retransmissions over a path. When the number of
R BTS390 EMPLA TDLOF ation retransmissions over a path exceeds the value of this
0 TE D-00200 parameter, the path is regarded as failed if no
WCDM MOD 4 heartbeat acknowledgment is received. If multiple
A, SCTPT paths are used, path switching is automatically
BTS390 EMPLA performed.
0 LTE TE GUI Value Range: 1~253
LST Unit: None
SCTPT
EMPLA
TE Default Value: 5
SWITC BTS390 ADD LOFD-0 Self- Meaning: Indicates whether to switch back to the
HBACK 0, SCTPT 02004 / configur primary path upon restoration of the primary path. If
FLAG BTS390 EMPLA TDLOF ation the primary path is unavailable, the SCTP link will be
0 TE D-00200 switched to the secondary path. When this parameter
WCDM MOD 4 is set to ENABLE and the primary path is restored, the
A, SCTPT SCTP link will be switched to the primary path. When
BTS390 EMPLA this parameter is set to DISABLE and the primary
0 LTE TE path is restored, the SCTP link will not be switched to
the primary path.
LST
SCTPT GUI Value Range: DISABLE(Disable),
EMPLA ENABLE(Enable)
TE Unit: None
Default Value: ENABLE(Enable)
SWITC BTS390 ADD LOFD-0 Self- Meaning: Indicates the number of consecutive
HBACH 0, SCTPT 02004 / configur heartbeat messages that must be transmitted on the
HBNU BTS390 EMPLA TDLOF ation primary path before the system can switch back to the
M 0 TE D-00200 primary path when SWITCHBACKFLAG is set to
WCDM MOD 4 ENABLE.
A, SCTPT GUI Value Range: 1~254
BTS390 EMPLA
0 LTE Unit: None
TE
LST
SCTPT Default Value: 10
EMPLA
TE

WCDMA RAN

nd
TSACK BTS390 ADD LOFD-0 Self- Meaning: Indicates the time interval that one end of
0, SCTPT 02004 / configur SCTP link has to wait before it can send an SACK
BTS390 EMPLA TDLOF ation message in response to data reception. A larger value
0 TE D-00200 of this parameter indicates a longer time interval
WCDM MOD 4 between the reception of data and the sending of the
A, SCTPT corresponding SACK message.
0 LTE TE Unit: ms
SCTPT
TE
CHKSU BTS390 ADD LOFD-0 Self- Meaning: Indicates the checksum algorithm. The
MTYPE 0, SCTPT 02004 / configur checksum algorithms at both ends of an SCTP link
BTS390 EMPLA TDLOF ation must be the same.
0 TE D-00200 GUI Value Range: ALDER32(ALDER32),
WCDM MOD 4 CRC32(CRC32)
A, SCTPT
BTS390 Unit: None
EMPLA
0 LTE TE Actual Value Range: ALDER32, CRC32
LST Default Value: CRC32(CRC32)

SCTPT
EMPLA
TE
MAXST BTS390 ADD LOFD-0 Self- Meaning: Indicates the maximum stream number of
REAM 0, SCTPT 02004 / configur an SCTP link.
BTS390 EMPLA TDLOF ation GUI Value Range: 1~34
0 TE D-00200
WCDM 4 Unit: None
MOD
A, SCTPT Actual Value Range: 1~34
BTS390 EMPLA Default Value: 17
0 LTE TE
LST
SCTPT
EMPLA
TE

WCDMA RAN

nd
SCTPH BTS390 ADD LOFD-0 Self- Meaning: Indicates the ID of the SCTP host.
OSTID 0, SCTPH 02004 / configur GUI Value Range: 0~65535
BTS390 OST TDLOF ation
0 D-00200 Unit: None
LST
WCDM SCTPH 4 Actual Value Range: 0~65535
A, OST Default Value: None
BTS390
0 LTE MOD
SCTPH
OST
RMV
SCTPH
OST
IPVERS BTS390 ADD None None Meaning: Indicates the IP protocol version of an
ION 0, SCTPH SCTP host.
BTS390 OST GUI Value Range: IPv4(IPv4), IPv6(IPv6)
0 MOD
WCDM Unit: None
SCTPH
A, OST Actual Value Range: IPv4, IPv6
BTS390 Default Value: IPv4(IPv4)
0 LTE LST
SCTPH
OST
SIGIP2 BTS390 ADD LOFD-0 Self- Meaning: Indicates the second local SCTP IPv4
V4 0, SCTPH 02004 / configur address, which is used by the base station to establish
BTS390 OST TDLOF ation a signaling channel. That is, this address is the second
0 MOD D-00200 local IPv4 address for automatically establishing an
WCDM SCTPH 4 SCTP link.
A, OST GUI Value Range: Valid IP address
BTS390
SCTPH Actual Value Range: Valid IP address
OST
Default Value: 0.0.0.0
PN BTS390 ADD LOFD-0 Self- Meaning: Indicates the number of the local SCTP
0, SCTPH 02004 / configur port, which is used in automatic setup of a Stream
BTS390 OST TDLOF ation Control Transmission Protocol (SCTP) link.
0 MOD D-00200 GUI Value Range: 1024~65535
WCDM SCTPH 4
A, Unit: None
OST
BTS390 Actual Value Range: 1024~65535
0 LTE LST
SCTPH Default Value: None
OST

WCDMA RAN

nd
SCTPPE BTS390 ADD LOFD-0 Self- Meaning: Indicates the ID of the SCTP peer. The
ERID 0, SCTPPE 02004 / configur value of SCTPPEERID in the SCTPPEER MOs
BTS390 ER TDLOF ation configured by users ranges from 0 to 65535. The
0 BLK D-00200 value of SCTPPEERID in the SCTPPEER MOs
WCDM SCTPPE 4 configured by the system ranges from 70000 to 79999.
A, ER GUI Value Range: 0~65535,70000~79999
BTS390
SCTPPE Actual Value Range: 0~65535,70000~79999
ER
Default Value: None
MOD
SCTPPE
ER
RMV
SCTPPE
ER
UBL
SCTPPE
ER
IPVERS BTS390 ADD LOFD-0 Self- Meaning: Indicates the IP protocol version of an
ION 0, SCTPPE 02004 / configur SCTP peer.
BTS390 ER TDLOF ation GUI Value Range: IPv4(IPv4), IPv6(IPv6)
0 MOD D-00200
WCDM 4 Unit: None
SCTPPE
A, ER Actual Value Range: IPv4, IPv6
BTS390 Default Value: IPv4(IPv4)
0 LTE LST
SCTPPE
ER
SIGIP2 BTS390 ADD LOFD-0 Self- Meaning: Indicates the second peer SCTP IPv4
V4 0, SCTPPE 02004 / configur address, which is used by the base station to establish
BTS390 ER TDLOF ation a signaling channel. That is, this address is the second
0 MOD D-00200 peer IPv4 address for automatically establishing an
WCDM SCTPPE 4 SCTP link.
A, ER GUI Value Range: Valid IP address
BTS390
SCTPPE Actual Value Range: Valid IP address
ER
Default Value: 0.0.0.0

WCDMA RAN

nd
PN BTS390 ADD LOFD-0 Self- Meaning: Indicates the number of the peer SCTP port,
0, SCTPPE 02004 / configur which is used in automatic setup of a Stream Control
BTS390 ER TDLOF ation Transmission Protocol (SCTP) link.
0 MOD D-00200 GUI Value Range: 1024~65535
WCDM SCTPPE 4
A, Unit: None
ER
0 LTE LST
SCTPPE Default Value: None
ER
CTRLM BTS390 ADD LOFD-0 Self- Meaning: Indicates whether an object can be
ODE 0, SCTPPE 02004 / configur automatically modified or deleted by the system. The
BTS390 ER TDLOF ation value MANUAL_MODE in non-simplified mode
0 MOD D-00200 means that only users can modify or delete the current
WCDM SCTPPE 4 object. The value MANUAL_MODE in simplified
A, ER mode means that the users can modify or delete the
BTS390 current object, but the system can only modify the
0 LTE LST SIMPLEMODESWITCH and EPGROUPID
SCTPPE parameters. The value AUTO_MODE means that both
ER the system and users can modify or delete the current
object.
GUI Value Range: MANUAL_MODE(Manual
Mode), AUTO_MODE(Auto Mode)
Unit: None
Actual Value Range: MANUAL_MODE,
AUTO_MODE
Default Value: AUTO_MODE(Auto Mode)
UPHOS BTS390 ADD WRFD- IP Meaning: Indicates the ID of the user-plane host.
TID 0, USERP 050402 Transmi GUI Value Range: 0~65535
BTS390 LANEH ssion
0 OST GBFD-1 Introduc Unit: None
WCDM 18601 tion on Actual Value Range: 0~65535
LST
A, USERP LOFD-0 Iub Default Value: None
BTS390 LANEH 02004 / Interface
0 LTE OST TDLOF Abis
MOD D-00200 over IP
USERP 4
LANEH Self-
OST configur
ation
RMV
USERP
LANEH
OST

WCDMA RAN

nd
IPVERS BTS390 ADD WRFD- IP Meaning: Indicates the version of the user-plane host
ION 0, USERP 050402 Transmi IP address.
BTS390 LANEH ssion GUI Value Range: IPv4(IPv4), IPv6(IPv6)
0 OST GBFD-1 Introduc
MOD
A, USERP LOFD-0 Iub Actual Value Range: IPv4, IPv6
BTS390 LANEH 02004 / Interface Default Value: IPv4(IPv4)
LST D-00200 over IP
USERP 4
LANEH Self-
OST configur
ation
LOCIP BTS390 ADD WRFD- IP Meaning: Indicates the IPv4 Address of the user plane
V4 0, USERP 050402 Transmi host.
BTS390 LANEH ssion GUI Value Range: Valid IP address
0 OST GBFD-1 Introduc
MOD
A, USERP LOFD-0 Iub Actual Value Range: Valid IP address
BTS390 LANEH 02004 / Interface Default Value: None
LST D-00200 over IP
USERP 4
LANEH Self-
OST configur
ation
UPPEE BTS390 ADD WRFD- IP Meaning: Indicates the ID of the user-plane peer. The
RID 0, USERP 050402 Transmi value of UPPEERID in the USERPLANEPEER MOs
BTS390 LANEP ssion configured by users ranges from 0 to 65535. The
0 EER GBFD-1 Introduc value of UPPEERID in the USERPLANEPEER MOs
WCDM 18601 tion on configured by the system ranges from 70000 to 79999.
LST
A, USERP Iub GUI Value Range: 0~65535,70000~79999
BTS390 LANEP Interface
0 LTE Unit: None
EER Abis Actual Value Range: 0~65535,70000~79999
MOD over IP
USERP Default Value: None
LANEP
EER
RMV
USERP
LANEP
EER

WCDMA RAN

nd
IPVERS BTS390 ADD WRFD- IP Meaning: Indicates the version of the user-plane peer
ION 0, USERP 050402 Transmi IP address.
BTS390 LANEP ssion GUI Value Range: IPv4(IPv4), IPv6(IPv6)
MOD
A, USERP LOFD-0 Iub Actual Value Range: IPv4, IPv6
BTS390 LANEP 02004 / Interface Default Value: IPv4(IPv4)
LST D-00200 over IP
USERP 4
LANEP Self-
EER configur
ation
PEERIP BTS390 ADD WRFD- IP Meaning: Indicates the IPv4 Address of the user plane
V4 0, USERP 050402 Transmi peer.
BTS390 LANEP ssion GUI Value Range: Valid IP address
MOD
A, USERP LOFD-0 Iub Actual Value Range: Valid IP address
BTS390 LANEP 02004 / Interface Default Value: None
LST D-00200 over IP
USERP 4
LANEP Self-
EER configur
ation
CTRLM BTS390 ADD WRFD- IP Meaning: Indicates whether the object can be
ODE 0, USERP 050402 Transmi modified or deleted by the system. The value
BTS390 LANEP ssion MANUAL_MODE means that only the user can
0 EER GBFD-1 Introduc modify or delete the object. The value AUTO_MODE
WCDM 18601 tion on means that both the system and the user can modify or
MOD
A, USERP LOFD-0 Iub delete the object.
BTS390 LANEP 02004 / Interface GUI Value Range: MANUAL_MODE(Manual
0 LTE EER TDLOF Mode), AUTO_MODE(Auto Mode)
Abis
LST D-00200 over IP Unit: None
USERP 4
Self- Actual Value Range: MANUAL_MODE,
LANEP AUTO_MODE
EER configur
ation Default Value: AUTO_MODE(Auto Mode)

WCDMA RAN

nd
EPGRO BTS390 ADD WRFD- IP Meaning: Indicates the ID of the end point group to
UPID 0, EPGRO 050402 Transmi which an end point belongs.
BTS390 UP ssion GUI Value Range: 0~65535
0 GBFD-1 Introduc
ADD 18601 Unit: None
WCDM SCTPH tion on
A, LOFD-0 Iub Actual Value Range: 0~65535
OST2EP
BTS390 GRP 02004 / Interface Default Value: None
0 LTE TDLOF
ADD Abis
D-00200 over IP
SCTPPE
4
ER2EP
Self-
GRP
configur
ADD ation
UPHOS
T2EPG
RP
ADD
UPPEE
R2EPG
RP
DSP
EPGRO
UP
LST
EPGRO
UP
LST
SCTPH
OST2EP
GRP
LST
SCTPPE
ER2EP
GRP
LST
UPHOS
T2EPG
RP
LST
UPPEE
R2EPG
RP
MOD
EPGRO
UP

WCDMA RAN

nd
RMV
EPGRO
UP
RMV
SCTPH
OST2EP
GRP
RMV
SCTPPE
ER2EP
GRP
RMV
UPHOS
T2EPG
RP
RMV
UPPEE
R2EPG
RP
SCTPH BTS390 LST LOFD-0 Self- Meaning: Indicates the list of all SCTP hosts in the
OSTLIS 0, EPGRO 02004 / configur end point group. This parameter takes effect only in
T BTS390 UP TDLOF ation UMTS and LTE.
0 D-00200 GUI Value Range: 0~11 characters
WCDM 4
A, Unit: None
BTS390 Actual Value Range: 0~11 characters
0 LTE Default Value: None
SCTPPE BTS390 LST LOFD-0 Self- Meaning: Indicates the list of all SCTP peers in the
ERLIST 0, EPGRO 02004 / configur end point group. This parameter takes effect only in
BTS390 UP TDLOF ation UMTS and LTE.
0 D-00200 GUI Value Range: 0~3079 characters
WCDM 4
A, Unit: None
BTS390 Actual Value Range: 0~3079 characters
0 LTE Default Value: None

WCDMA RAN

nd
USERP BTS390 LST WRFD- IP Meaning: Indicates the list of all user plane hosts in
LANEH 0, EPGRO 050402 Transmi the end point group.
OSTLIS BTS390 UP ssion GUI Value Range: 0~71 characters
T 0 GBFD-1 Introduc
A, LOFD-0 Iub Actual Value Range: 0~71 characters
BTS390 02004 / Interface Default Value: None
0 LTE TDLOF Abis
D-00200 over IP
4
Self-
configur
ation
USERP BTS390 LST WRFD- IP Meaning: Indicates the list of all user plane peers in
LANEP 0, EPGRO 050402 Transmi the end point group.
EERLIS BTS390 UP ssion GUI Value Range: 0~6143 characters
T 0 GBFD-1 Introduc
A, LOFD-0 Iub Actual Value Range: 0~6143 characters
0 LTE TDLOF Abis
D-00200 over IP
4
Self-
configur
ation
TYPEF BTS390 ADD None None Meaning: Indicates the type of an end point group.
LAG 0, EPGRO When this parameter is set to COMMON, the local
BTS390 UP end point group is a common group. When this
0 MOD parameter is set to CENTRALIZED_EX2, the local
WCDM EPGRO end point group is dedicated group for the centralized
A, UP eX2. The parameter takes effect only in LTE.
BTS390 GUI Value Range: COMMON(COMMON),
0 LTE LST
EPGRO CENTRALIZED_EX2(CENTRALIZED_EX2)
UP Unit: None
Actual Value Range: COMMON,
CENTRALIZED_EX2
Default Value: COMMON(COMMON)

WCDMA RAN

nd
UX2ID BTS390 ADD None None Meaning: Indicates the uX2 object ID.
0, UX2 GUI Value Range: 0
BTS390 DSP
0 Unit: None
UX2
WCDM Actual Value Range: 0
A LST
UX2 Default Value: None
MOD
UX2
RMV
UX2
CPEPG BTS390 ADD None None Meaning: Indicates the ID of the control-plane
ROUPI 0, UX2 endpoint group used by the uX2 object.
D BTS390 MOD GUI Value Range: 0~65535
0 UX2
WCDM Unit: None
A LST Actual Value Range: 0~65535
UX2
Default Value: None
UPEPG BTS390 ADD None None Meaning: Indicates the ID of the user-plane endpoint
ROUPI 0, UX2 group used by the uX2 object.
D BTS390 MOD GUI Value Range: 0~65535
0 UX2
WCDM Unit: None
A LST Actual Value Range: 0~65535
UX2
Default Value: None
USERL BTS390 ADD None None Meaning: Indicates the uX2 object description.
ABEL 0, UX2 GUI Value Range: 0~256 characters
BTS390 MOD
0 Unit: None
UX2
WCDM Actual Value Range: 0~256 characters
A LST
UX2 Default Value: None
STATIC BTS390 ADD None None Meaning: Indicates whether to enable static UDP Ping
CHKS 0, UX2 detection over the uX2 interface. If this parameter is
W BTS390 MOD set to ON, static UDP Ping detection is enabled over
0 UX2 the uX2 interface. If this parameter is set to OFF,
WCDM static UDP Ping detection is disabled over the uX2
A LST interface.
UX2
GUI Value Range: OFF(OFF), ON(ON)
Unit: None
Default Value: OFF(OFF)

WCDMA RAN

nd
CN BTS390 ADD None None Meaning: Indicates the number of the cabinet that
0, RSCGR houses the board where a transmission resource group
BTS390 P is established.
0 DSP GUI Value Range: 0~7
WCDM RSCGR
A, Unit: None
P
0 LTE MOD
RSCGR Default Value: 0
P
RMV
RSCGR
P
LST
RSCGR
P
SRN BTS390 ADD None None Meaning: Indicates the number of the subrack that
0, RSCGR houses the board where a transmission resource group
BTS390 P is established.
WCDM RSCGR
A, Unit: None
P
0 LTE MOD
RSCGR Default Value: 0
P
RMV
RSCGR
P
LST
RSCGR
P

WCDMA RAN

nd
SN BTS390 ADD None None Meaning: Indicates the number of the slot
0, RSCGR corresponding to the board where a transmission
BTS390 P resource group is established.
WCDM RSCGR
A, Unit: None
P
0 LTE MOD
RSCGR Default Value: None
P
RMV
RSCGR
P
LST
RSCGR
P
BEAR BTS390 ADD WRFD- ATM/IP Meaning: Indicates the bearer type of the transmission
0, RSCGR 050404 Dual group. The LTE currently does not support ATM.
BTS390 P Stack GUI Value Range: ATM(ATM), IP(IP)
0 LOFD-0 Node B
DSP 03011 / Unit: None
WCDM RSCGR
A, TDLOF Enhance Actual Value Range: ATM, IP
P D-00301 d
BTS390 Default Value: None
0 LTE MOD 1 Transmi
RSCGR ssion
P GBFD-1 QoS
18605 Manage
RMV
RSCGR ment
P IP QOS
LST
RSCGR
P

WCDMA RAN

nd
PN BTS390 ADD None None Meaning: Indicates the number of the port where the
0, RSCGR transmission resource group is configured.
BTS390 P GUI Value Range: 0~15
0 DSP
WCDM Unit: None
RSCGR
A, P Actual Value Range: 0~15
BTS390 Default Value: 0
0 LTE MOD
RSCGR
P
RMV
RSCGR
P
LST
RSCGR
P
SBT BTS390 ADD None None Meaning: Indicates the type of sub-board on the
0, RSCGR transmission group. The LTE currently does not
BTS390 P support UNCHANNELLED_COVERBOARD.
0 DSP GUI Value Range: BASE_BOARD(Base Board),
WCDM RSCGR UNCHANNELLED_COVERBOARD(Unchannelled
A, P Cover Board), E1_COVERBOARD(E1 Cover Board),
BTS390 BACK_BOARD(Back Board),
0 LTE MOD
RSCGR ETH_COVERBOARD(Ethernet Cover Board)
P Unit: None
RMV Actual Value Range: BASE_BOARD,
RSCGR UNCHANNELLED_COVERBOARD,
P E1_COVERBOARD, BACK_BOARD,
LST ETH_COVERBOARD
RSCGR Default Value: None
P

WCDMA RAN

nd
PT BTS390 ADD None None Meaning: Indicates the type of port where a
0, RSCGR transmission resource group is carried. The LTE
BTS390 P currently does not support STM1, IMA, UNI, or
0 DSP FRAATM.
WCDM RSCGR GUI Value Range: IMA(IMA Group), UNI(UNI
A, P Link), STM1(STM1), FRAATM(FRAATM Link),
BTS390 PPP(PPP Link), MPGRP(Multi-link PPP Group),
0 LTE MOD
RSCGR ETH(Ethernet Port), ETHTRK(Ethernet Trunk),
P TUNNEL(Tunnel)
RMV Unit: None
RSCGR Actual Value Range: IMA, UNI, STM1, FRAATM,
P PPP, MPGRP, ETH, ETHTRK, TUNNEL
LST Default Value: None
RSCGR
P
RSCGR BTS390 ADD WRFD- Transmi Meaning: Indicates the ID of a transmission resource
PID 0, RSCGR 0213040 ssion group. When you use 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 LOFD-0 Sharing creates a transmission resource group with
RSCGR 03011 /
A, P on Transmission Resource Group ID set to
BTS390 TDLOF Iub/Iur DEFAULTPORT(Default Port). When you remove
0 LTE MOD D-00301 Interface any of the preceding objects, the system automatically
RSCGR 1 removes the transmission resource group. When you
P Enhance add a PPP link, an MP group, an Ethernet port, an
GBFD-1 d
RMV 18605 Ethernet trunk, or an uplink tunnel on the CME, if the
RSCGR Transmi default transmission resource group does not exist, the
P ssion system automatically creates a transmission resource
QoS group with Transmission Resource Group ID set to
LST Manage
RSCGR AUTOPORT(Autoport Port). When you remove any
ment of the preceding objects, the system automatically
P
IP QOS 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

WCDMA RAN

nd
RU BTS390 ADD WRFD- Transmi Meaning: Indicates the rate unit of the TX bandwidth,
0, RSCGR 0213040 ssion RX bandwidth, TX CIR, RX CIR, TX PIR and RX
BTS390 P 6 Recours PIR of the transmission resource group. The LTE
0 MOD e currently does not support CELL/S.
WCDM LOFD-0 Sharing
RSCGR 03011 / GUI Value Range: KBPS(kbit/s), CELL/S(cell/s)
A, P on
BTS390 TDLOF Iub/Iur Unit: None
0 LTE DSP D-00301 Interface Actual Value Range: KBPS, CELL/S
RSCGR 1
P Enhance Default Value: KBPS(kbit/s)
GBFD-1 d
LST 18605
RSCGR Transmi
P ssion
QoS
Manage
ment
IP QOS
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 LOFD-0 Sharing admission bandwidth and TX traffic shaping
RSCGR 03011 /
A, P on bandwidth. The minimum rate supported by the
BTS390 TDLOF Iub/Iur UMPTa, UMPTb, UMPTe, UMDU, GTMUb or
0 LTE DSP D-00301 Interface GTMUc is 64 kbit/s. The LMPT can be configured
RSCGR 1 with a maximum of 360 Mbit/s TX bandwidth. The
P Enhance WMPT, GTMUb or GTMUc can be configured with a
GBFD-1 d
LST 18605 maximum of 300 Mbit/s TX bandwidth. The UMPTa,
RSCGR Transmi UMPTb, UMDU or UTRPc can be configured with a
P ssion maximum of 1 Gbit/s TX bandwidth. The UMPTe or
QoS UCCU can be configured with a maximum of 10
Manage Gbit/s TX bandwidth. The value of TX bandwidth is
ment set to the maximum value of TX bandwidth supported
IP QOS by the board when it bigger than the maximum one.
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.
Unit: None
Default Value: None

WCDMA RAN

nd
RXBW BTS390 ADD WRFD- Transmi Meaning: Indicates the RX bandwidth of a

0, RSCGR 0213040 ssion transmission resource group. To LTE, this parameter
BTS390 P 6 Recours value is also used as the downlink transport admission
0 MOD WRFD- e bandwidth. The minimum rate supported by the
WCDM RSCGR 0106101 Sharing UMPTa, UMPTb, UMPTe, UMDU, GMTUb or
A, P 0 on GTMUc is 64 kbit/s. The LMPT can be configured
BTS390 Iub/Iur with a maximum of 540 Mbit/s RX bandwidth. The
0 LTE DSP LOFD-0 Interface WMPT, GTMUb or GTMUc can be configured with a
RSCGR 03011 / maximum of 300 Mbit/s RX bandwidth. The UMPTa,
P HSDPA
TDLOF Flow UMPTb, UMDU or UTRPc can be configured with a
LST D-00301 Control maximum of 1 Gbit/s RX bandwidth. The UMPTe or
RSCGR 1 UCCU can be configured with a maximum of 10
P Enhance Gbit/s RX bandwidth.
GBFD-1 d
18605 GUI Value Range: 32~40000000
Transmi
ssion Unit: None
QoS Actual Value Range: 32~40000000
Manage Default Value: None
ment
IP QOS
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 LOFD-0 Sharing with a maximum of 600 Mbit/s TX committed burst
RSCGR 03011 /
A, P on size. The WMPT, GTMUb or GTMUc can be
BTS390 TDLOF Iub/Iur configured with a maximum of 600 Mbit/s TX
0 LTE LST D-00301 Interface committed burst size. The UMPTa, UMPTb, UMDU
RSCGR 1 or UTRPc can be configured with a maximum of 1
P Enhance Gbit/s TX committed burst size. The UMPTe or
GBFD-1 d
18605 UCCU can be configured with a maximum of 10
Transmi Gbit/s TX committed burst size. The value of TX
ssion committed burst size is set to the maximum value of
QoS TX committed burst size supported by the board when
Manage it bigger than the maximum one.
ment
IP QOS Unit: kbit
Default Value: 64

WCDMA RAN

nd
TXEBS BTS390 ADD WRFD- Transmi Meaning: Indicates the TX excessive burst size of a
0 MOD e excessive burst size. The WMPT, GTMUb or GTMUc
WCDM LOFD-0 Sharing can be configured with a maximum of 600 Mbit/s TX
RSCGR 03011 /
A, P on excessive burst size. The UMPTa, UMPTb, UMDU or
BTS390 TDLOF Iub/Iur UTRPc can be configured with a maximum of 1
0 LTE LST D-00301 Interface Gbit/s TX excessive burst size. The UMTPe or UCCU
RSCGR 1 can be configured with a maximum of 10 Gbit/s TX
P Enhance excessive burst size. The value of TX excessive burst
GBFD-1 d
18605 size is set to the maximum value of TX excessive
Transmi burst size supported by the board when it bigger than
ssion the maximum one.
QoS
Manage GUI Value Range: 64~40000000
ment Unit: kbit
IP QOS Actual Value Range: 64~40000000
WEIGH BTS390 ADD WRFD- Transmi Meaning: Indicates the scheduling weight of a
T 0, RSCGR 0213040 ssion transmission resource group. This parameter is used in
BTS390 P 6 Recours calculating the bandwidth scheduled to a resource
0 MOD e group, which helps achieve the user admission
WCDM LOFD-0 Sharing control.
RSCGR 03011 /
A, P on GUI Value Range: 1~100
BTS390 TDLOF Iub/Iur
0 LTE LST D-00301 Interface Unit: None
RSCGR 1 Actual Value Range: 1~100
P Enhance
GBFD-1 d Default Value: 100
18605 Transmi
ssion
QoS
Manage
ment
IP QOS

WCDMA RAN

nd
TXCIR BTS390 ADD WRFD- Transmi Meaning: Indicates the transmit CIR of the
0 MOD e committed information rate. The UMPTa, UMPTb,
WCDM LOFD-0 Sharing UMDU or UTRPc can be configured with a maximum
RSCGR 03011 /
A, P on of 1 Gbit/s TX committed information rate. The
BTS390 TDLOF Iub/Iur GTMUb or GTMUc can be configured with a
0 LTE LST D-00301 Interface maximum of 300 Mbit/s TX committed information
RSCGR 1 rate. The UMPTe or UCCU can be configured with a
P Enhance maximum of 10 Gbit/s TX committed information
GBFD-1 d
18605 rate. The value of TX committed information rate is
Transmi set to the maximum value of TX committed
ssion information rate supported by the board when it
QoS bigger than the maximum one.
Manage
ment GUI Value Range: 64~40000000
Unit: None
IP QOS
Default Value: None
RXCIR BTS390 ADD WRFD- Transmi Meaning: Indicates the receive CIR of the
0, RSCGR 0213040 ssion transmission resource group. This parameter value is
BTS390 P 6 Recours used as the downlink transport admission bandwidth
0 MOD e for non-flow-control services. The LMPT can be
WCDM LOFD-0 Sharing configured with a maximum of 540 Mbit/s RX
RSCGR 03011 /
A, P on committed information rate. The UMPTa, UMPTb,
BTS390 TDLOF Iub/Iur UMDU or UTRPc can be configured with a maximum
0 LTE LST D-00301 Interface of 1 Gbit/s RX committed information rate. The
RSCGR 1 UMPTe or UCCU can be configured with a maximum
P Enhance of 10 Gbit/s RX committed information rate. The
GBFD-1 d
18605 value of RX committed information rate is set to the
Transmi maximum value of RX committed information rate
ssion supported by the board when it bigger than the
QoS maximum one. Only the LTE supports this function
Manage currently.
ment
IP QOS Unit: None
Default Value: None

WCDMA RAN

nd
TXPIR BTS390 ADD WRFD- Transmi Meaning: Indicates the transmit PIR of the
BTS390 P 6 Recours configured with a maximum of 360 Mbit/s TX peak
0 MOD e information rate. The UMPTa, UMPTb, UMDU or
WCDM LOFD-0 Sharing UTRPc can be configured with a maximum of 1
RSCGR 03011 /
A, P on Gbit/s TX peak information rate. The GTMUb or
BTS390 TDLOF Iub/Iur GTMUc can be configured with a maximum of 300
0 LTE LST D-00301 Interface Mbit/s TX peak information rate. The UMPTe or
RSCGR 1 UCCU can be configured with a maximum of 10
P Enhance Gbit/s TX peak information rate. The value of TX
GBFD-1 d
18605 peak information rate is set to the maximum value of
Transmi TX peak information rate supported by the board
ssion when it bigger than the maximum one.
QoS
ment Unit: None
Default Value: None
RXPIR BTS390 ADD WRFD- Transmi Meaning: Indicates the receive PIR of the
0, RSCGR 0213040 ssion transmission resource group. This parameter value is
BTS390 P 6 Recours used as the downlink transport admission bandwidth.
0 MOD e The LMPT can be configured with a maximum of 540
WCDM LOFD-0 Sharing Mbit/s RX peak information rate. The UMPTa,
RSCGR 03011 /
A, P on UMPTb, UMDU or URTPc can be configured with a
BTS390 TDLOF Iub/Iur maximum of 1 Gbit/s RX peak information rate. The
0 LTE LST D-00301 Interface UMPTe or UCCU can be configured with a maximum
RSCGR 1 of 10 Gbit/s RX peak information rate. The value of
P Enhance RX peak information rate is set to the maximum value
GBFD-1 d
18605 of RX peak information rate supported by the board
Transmi when it bigger than the maximum one. Only the LTE
ssion supports this function currently.
QoS
ment Unit: None
Default Value: None

WCDMA RAN

nd
TXPBS BTS390 ADD WRFD- Transmi Meaning: Indicates the size of the peak burst
0, RSCGR 0213040 ssion transmitted from the transmission resource group. The
BTS390 P 6 Recours LMPT can be configured with a maximum of 540
0 MOD e Mbit/s TX peak burst size. The UMPTa, UMPTb,
WCDM LOFD-0 Sharing UMDU or UTRPc can be configured with a maximum
RSCGR 03011 /
A, P on of 1 Gbit/s TX peak burst size. The GTMUb or
BTS390 TDLOF Iub/Iur GTMUc can be configured with a maximum of 300
0 LTE LST D-00301 Interface Mbit/s TX peak burst size. The UMPTe or UCCU can
RSCGR 1 be configured with a maximum of 10 Gbit/s TX peak
P Enhance burst size. The value of TX peak burst size is set to the
GBFD-1 d
18605 maximum value of TX peak burst size supported by
Transmi the board when it bigger than the maximum one.
ssion
QoS GUI Value Range: 64~40000000
Manage Unit: kbit
ment Actual Value Range: 64~40000000
IP QOS Default Value: None
ENDPO BTS390 ADD WRFD- IP Meaning: Indicates the end point group or user plane
INTID 0, EP2RSC 050402 Transmi peer that needs to be added to the specified
BTS390 GRP ssion transmission resource group.
0 GBFD-1 Introduc
RMV 18601 GUI Value Range: 0~65535,70000~79999
WCDM EP2RSC tion on
A, Iub Unit: None
GRP LOFD-0
BTS390 02004 / Interface Actual Value Range: 0~65535,70000~79999
0 LTE LST
EP2RSC TDLOF Abis Default Value: None
GRP D-00200 over IP
4
Self-
configur
ation
CN BTS390 ADD WRFD- IP Meaning: Indicates the number of the cabinet where
0, EP2RSC 050402 Transmi the transmission resource group to which a node maps
BTS390 GRP ssion is configured.
0 GBFD-1 Introduc
RMV 18601 GUI Value Range: 0~7
WCDM EP2RSC tion on
A, Iub Unit: None
GRP LOFD-0
BTS390 02004 / Interface Actual Value Range: 0~7
0 LTE LST
EP2RSC TDLOF Abis Default Value: 0
GRP D-00200 over IP
4
Self-
configur
ation

WCDMA RAN

nd
SRN BTS390 ADD WRFD- IP Meaning: Indicates the number of the subrack where
0, EP2RSC 050402 Transmi the transmission resource group to which a node maps
BTS390 GRP ssion is configured.
0 GBFD-1 Introduc
WCDM EP2RSC tion on
A, Iub Unit: None
GRP LOFD-0
0 LTE LST
GRP D-00200 over IP
4
Self-
configur
ation
SN BTS390 ADD WRFD- IP Meaning: Indicates the number of the slot where the
0, EP2RSC 050402 Transmi transmission resource group to which a node maps is
BTS390 GRP ssion configured.
0 GBFD-1 Introduc
WCDM EP2RSC tion on
A, Iub Unit: None
GRP LOFD-0
0 LTE LST
EP2RSC TDLOF Abis Default Value: None
GRP D-00200 over IP
4
Self-
configur
ation
SBT BTS390 ADD WRFD- IP Meaning: Indicates the subboard type of the board
0, EP2RSC 050402 Transmi where the transmission resource group to which a
BTS390 GRP ssion node maps is configured.
0 GBFD-1 Introduc
RMV 18601 GUI Value Range: BASE_BOARD(Base Board),
WCDM EP2RSC tion on E1_COVERBOARD(E1 Cover Board),
A, GRP LOFD-0 Iub BACK_BOARD(Back Board),
BTS390 02004 / Interface ETH_COVERBOARD(Ethernet Cover Board)
0 LTE LST
EP2RSC TDLOF Abis Unit: None
GRP D-00200 over IP
4 Actual Value Range: BASE_BOARD,
Self- E1_COVERBOARD, BACK_BOARD,
configur ETH_COVERBOARD
ation Default Value: None

WCDMA RAN

nd
PT BTS390 ADD WRFD- IP Meaning: Indicates the type of the port where the
0 GBFD-1 Introduc
RMV 18601 GUI Value Range: PPP(PPP Link), MPGRP(Multi-
WCDM EP2RSC tion on link PPP Group), ETH(Ethernet Port),
A, GRP LOFD-0 Iub ETHTRK(Ethernet Trunk), TUNNEL(Tunnel)
BTS390 02004 / Interface
EP2RSC TDLOF Abis
D-00200 Actual Value Range: PPP, MPGRP, ETH, ETHTRK,
GRP over IP TUNNEL
4
Self- Default Value: None
configur
ation
PN BTS390 ADD WRFD- IP Meaning: Indicates the number of the port where the
0 GBFD-1 Introduc
WCDM EP2RSC tion on
A, Iub Unit: None
GRP LOFD-0
0 LTE LST
GRP D-00200 over IP
4
Self-
configur
ation
BEAR BTS390 ADD WRFD- IP Meaning: Indicates the bearing type of the
0, EP2RSC 050402 Transmi transmission resource group to which a node maps.
BTS390 GRP ssion GUI Value Range: IP(IP)
0 GBFD-1 Introduc
RMV 18601 Unit: None
WCDM EP2RSC tion on
A, GRP LOFD-0 Iub Actual Value Range: IP
BTS390 02004 / Interface Default Value: IP(IP)
0 LTE LST
EP2RSC TDLOF Abis
GRP D-00200 over IP
4
Self-
configur
ation

WCDMA RAN

nd
RSCGR BTS390 ADD WRFD- IP Meaning: Indicates the ID of the transmission

PID 0, EP2RSC 050402 Transmi resource group to which a node maps.
BTS390 GRP ssion GUI Value Range: 0~15
0 GBFD-1 Introduc
RMV 18601 Unit: None
WCDM EP2RSC tion on
A, GRP LOFD-0 Iub Actual Value Range: 0~15
0 LTE LST
EP2RSC TDLOF Abis
GRP D-00200 over IP
4
Self-
configur
ation
IKEVE BTS390 ADD WRFD- IP Meaning: Indicates the IKE protocol version.
RSION 0, SECURI 050402 Transmi GUI Value Range: IKE_V1(IKE V1), IKE_V2(IKE
BTS390 TYTEM WRFD- ssion V2)
0 PLATE 140209 Introduc
MOD
A, SECURI GBFD-1 Iub Actual Value Range: IKE_V1, IKE_V2
BTS390 TYTEM 18601 Interface Default Value: IKE_V2(IKE V2)
0 LTE PLATE NodeB
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYTEM LOFD-0
Abis
PLATE 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN

nd
IPVERS BTS390 ADD WRFD- IP Meaning: Indicates the version of the security host IP
ION 0, SECURI 050402 Transmi address.
BTS390 TYHOS WRFD- ssion GUI Value Range: IPv4(IPv4), IPv6(IPv6)
0 T 140209 Introduc
MOD
A, SECURI GBFD-1 Iub Actual Value Range: IPv4, IPv6
BTS390 TYHOS 18601 Interface Default Value: IPv4(IPv4)
0 LTE T NodeB
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYHOS LOFD-0
Abis
T 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
LOCIK BTS390 ADD WRFD- IP Meaning: This parameter is used to designate the
EIPV4 0, SECURI 050402 Transmi physical port of the IPSec Policy Group Binding.
BTS390 TYHOS WRFD- ssion GUI Value Range: Valid IP address
0 T 140209 Introduc
MOD
A, SECURI GBFD-1 Iub Actual Value Range: Valid IP address
BTS390 TYHOS 18601 Interface Default Value: None
0 LTE T NodeB
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYHOS LOFD-0
Abis
T 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN

nd
IPVERS BTS390 ADD WRFD- IP Meaning: Indicates the version of the security peer IP
ION 0, SECURI 050402 Transmi address.
BTS390 TYPEE WRFD- ssion GUI Value Range: IPv4(IPv4), IPv6(IPv6)
0 R 140209 Introduc
MOD
A, SECURI GBFD-1 Iub Actual Value Range: IPv4, IPv6
BTS390 TYPEE 18601 Interface Default Value: IPv4(IPv4)
0 LTE R NodeB
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYPEE LOFD-0
Abis
R 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec
PEERIK BTS390 ADD WRFD- IP Meaning: Indicates the IPv4 address of the IKE peer.
EIPV4 0, SECURI 050402 Transmi GUI Value Range: Valid IP address
BTS390 TYPEE WRFD- ssion
0 R Introduc Unit: None
140209
WCDM MOD tion on Actual Value Range: Valid IP address
BTS390 TYPEE 18601 Interface
0 LTE R NodeB
GBFD-1
LST 13524 Integrate
SECURI d IPSec
TYPEE LOFD-0
Abis
R 02004 /
over IP
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN

nd
CTRLM BTS390 ADD WRFD- IP Meaning: Indicates whether the object can be
ODE 0, SECURI 050402 Transmi modified or deleted by the system. The value
BTS390 TYPEE WRFD- ssion MANUAL_MODE means that only the user can
0 R 140209 Introduc modify or delete the object. The value AUTO_MODE
WCDM MOD tion on means that both the system and the user can modify or
A, SECURI GBFD-1 Iub delete the object.
BTS390 TYPEE 18601 Interface GUI Value Range: MANUAL_MODE(Manual
0 LTE R NodeB Mode), AUTO_MODE(Auto Mode)
GBFD-1
LST 13524 Integrate Unit: None
SECURI d IPSec
Actual Value Range: MANUAL_MODE,
TYPEE LOFD-0
Abis AUTO_MODE
R 02004 /
over IP Default Value: AUTO_MODE(Auto Mode)
TDLOF
D-00200 BTS
4 Integrate
d Ipsec
LOFD-0
03009 / Self-
TDLOF configur
D-00300 ation
9
Ipsec

WCDMA RAN
uX2 Interface Management Feature Parameter Description 10 Counters
10 Counters
Table 10-1 Counters

Counter ID Counter Counter NE Feature ID Feature Name
Name Description
1542455327 VS.IP.TxBytes Number of NodeB Multi-mode: IP Transmission

bytes in the None Introduction on
successfully GSM: Abis Interface
transmitted IP GBFD-118601 IP Transmission
packets Introduction on
UMTS:
WRFD-050402 Iub Interface
LTE: None
1542455365 VS.RscGroup.T Number of NodeB Multi-mode: IP QOS

xBytes bytes in the None IP Transmission
packets GSM: Introduction on
successfully GBFD-118605 Iub Interface
transmitted by
the resource UMTS: Enhanced
group WRFD-050402 Transport QoS
LTE: Management
LOFD-003011 Enhanced
TDLOFD-0030 Transport QoS
11 Management
1542455911 VS.IPPM.Local Number of NodeB Multi-mode: IP Performance

.TxPkts packets sent by None Monitor
the IP PM local GSM: IP Transmission
end GBFD-118607 Introduction on
UMTS: Iub Interface
WRFD-050402 IP Performance
LTE: Monitoring
LOFD-0030120 IP Performance
1 Monitoring
TDLOFD-0030
1201

WCDMA RAN
uX2 Interface Management Feature Parameter Description 10 Counters
Counter ID Counter Counter NE Feature ID Feature Name

Name Description
1542455912 VS.IPPM.Peer. Number of NodeB Multi-mode: IP Performance

RxPkts packets None Monitor
received by the GSM: IP Transmission
IP PM peer end GBFD-118607 Introduction on
UMTS: Iub Interface
WRFD-050402 IP Performance
LTE: Monitoring
LOFD-0030120 IP Performance
1 Monitoring
TDLOFD-0030
1201

WCDMA RAN
uX2 Interface Management Feature Parameter Description 11 Glossary
11 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

WCDMA RAN
uX2 Interface Management Feature Parameter Description 12 Reference Documents
12 Reference Documents
1. IP Transmission Feature Parameter Description

2. IP RAN Engineering Guide Feature Parameter Description
3. IPSec Feature Parameter Description
4. Multi-Carrier HSDPA Feature Parameter Description
5. Inter-NodeB Uplink CoMP Feature Parameter Description
6. RAN Reconfiguration Guide for BSC6900
7. RAN Reconfiguration Guide for BSC6910


UX2 Interface Management (RAN18.1 - 02)

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

UX2 Interface Management (RAN18.1 - 02)

Enviado por

Direitos autorais:

Formatos disponíveis

WCDMA RAN

uX2 Interface Management Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2016-03-28) Huawei Proprietary and Confidential i

1 About This Document.................................................................................................................. 1

3 uX2 Interface Management in Common Scenarios.................................................................6

4 uX2 Interface Self-Setup in IPsec-enabled Scenarios...........................................................12

5 Important Notes for uX2 Self-Setup........................................................................................ 27

Issue 02 (2016-03-28) Huawei Proprietary and Confidential ii

Issue 02 (2016-03-28) Huawei Proprietary and Confidential iii

1 About This Document

This document applies to the following types of base stations.

Base Station Model

Macro BTS3900, BTS3900A, BTS3900C, BTS3900L, BTS3900AL, and

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 1

Changes in wording or addition of information and any related parameters affected by

Change Change Description Parameter Change

Feature None None

Editorial Optimized the monitoring over the uX2 interface. None

Change Change Description Parameter Change

Feature None None

Editorial Optimized the description about restrictions of the None

Optimized the monitoring over the uX2 interface. None

Draft A (2015-12-30) of RAN18.1

1.4 Differences Between Base Station Types

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 2

uX2 Interface Management provides the following functions:

l Automatic uX2 interface setup

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 3

Figure 2-1 uX2 interface in a network

Figure 2-2 Coordination over IP RAN

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 4

Figure 2-3 uX2 protocol stack

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 5

3 uX2 Interface Management in Common

3.1 uX2 Interface Self-Setup

3.1.1 uX2 Self-Setup with SCTPPEER and USERPLANEPEER

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 6

The uX2 self-setup procedures are as follows:

3.1.2 uX2 Self-Setup with SCTPPEER and USERPLANEPEER

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 7

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 8

Figure 3-3 Procedures for uX2 self-setup over OSS

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 9

b. The source NodeB automatically generates the SCTPLNK, CPBEARER, and

3.2 uX2 Interface Auto-Deletion

UX2AutoDeleteForFaultTimer(BSC6900,BSC6910) is specified based on network conditions. It is

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 10

3.3 uX2 Dynamic Blacklist

l UX2DynBlackListAgingTimer(BSC6900,BSC6910) is specified based on network conditions. It is

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 11

4 uX2 Interface Self-Setup in IPsec-enabled

Table 4-1 Security policies for the uX2 interface

IP RAN l IPsec can be implemented on a network where a security gateway

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 12

IPsec specifications are as follows:

4.2 uX2 Self-Setup in IPsec-enabled Scenarios with

Issue 02 (2016-03-28) Huawei Proprietary and Confidential 13