Академический Документы
Профессиональный Документы
Культура Документы
Issue 01
Date 2014-04-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Contents
2 Overview.........................................................................................................................................4
2.1 Protocol Stack.................................................................................................................................................................5
2.2 Transmission Mode Configuration.................................................................................................................................7
3 Networking.....................................................................................................................................8
4 Related Features...........................................................................................................................10
4.1 Features Related to WRFD-050404 ATM/IP Dual Stack NodeB................................................................................10
5 Network Impact...........................................................................................................................11
5.1 WRFD-050404 ATM/IP Dual Stack NodeB................................................................................................................11
6 Engineering Guidelines.............................................................................................................12
6.1 WRFD-050404 ATM/IP Dual Stack NodeB................................................................................................................12
6.1.1 When to Use ATM/IP Dual Stack NodeB.................................................................................................................12
6.1.2 Required Information................................................................................................................................................12
6.1.3 Planning.....................................................................................................................................................................12
6.1.4 Deployment...............................................................................................................................................................13
6.1.5 Performance Monitoring............................................................................................................................................19
6.1.6 Troubleshooting.........................................................................................................................................................19
7 Parameters.....................................................................................................................................22
8 Counters........................................................................................................................................32
9 Glossary.........................................................................................................................................51
10 Reference Documents...............................................................................................................52
1.1 Scope
This document describes WRFD-050404 ATM/IP Dual Stack NodeB, including its technical
principles, related features, network impact, and engineering guidelines.
Before reading this document, familiarize yourself with the following documents:
NE Type NE Model
RNC BSC6900
NE Type NE Model
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier version
RAN16.0 01 (2014-04-30)
This issue does not include any changes.
WRFD- ATM/IP Y N Y N N Y
050404 Dual
Stack
NodeB
NOTE
Y indicates that a feature is supported; N indicates that a feature is not supported; NA indicates that an NE is
not involved, that is, a feature does not require the support of the NE.
2 Overview
The Iub interface connects the RNC and the NodeB. When the Iub interface uses ATM and IP
hybrid transmission, the Iub over ATM&IP protocol stack is used.
This chapter describes the Iub over hybrid ATM&IP transmission mode of the BSC6900 when
the Iub interface works in non-transmission-resource-pool mode. For details about the
simultaneous use of ATM&IP hybrid transmission and transmission resource pool mode over
the Iub interface of the BSC6900 or BSC6910, see Transmission Resource Pool in RNC Feature
Parameter Description.
The ATM configurations and principles are the same for the BSC6900 and BSC6910.
When Iub over ATM&IP is used, the RNC supports the following transmission modes at the
data link layer:
l ATM: ATM over E1/T1, ATM over channelized STM-1/OC-3, and ATM over
unchannelized STM-1/OC-3c
l IP: IP over E1/T1, IP over channelized STM-1/OC-3, and IP over FE/GE
When Iub over ATM&IP is used, the BTS3900, BTS3900A, DBS3900 support the following
transmission modes at the data link layer:
l ATM: ATM over E1/T1 and ATM over unchannelized STM-1/OC-3c
l IP: IP over E1/T1 and IP over FE/GE
Control Plane
NodeB Application Part (NBAP) is the signaling protocol used to transmit control plane
messages between the NodeB and the controlling RNC (CRNC) at the radio network layer.
In Iub over ATM&IP, the control plane can be configured in active/standby mode (an SAAL
link and an SCTP link are configured) to improve transmission reliability. Figure 2-2 illustrates
a configuration instance for the NodeB control port (NCP), which is the same for the
communication control port (CCP).
To add an NCP or CCP, you need to specify the bearer mode by setting the CARRYLNKT
(NCP)/CARRYLNKT(CCP) parameter on the RNC side.
In active/standby mode, each NCP or CCP is configured with an SAAL link and an SCTP link.
On the RNC side, you can specify the active link by setting the MAINLINK(ADD UCCP)/
MAINLINK(ADD UNCP) parameter on the RNC side and the BELONG parameter on the
NodeB side.
NCP data and CCP data are preferentially transmitted on the active link. If the active link is
unavailable, the data is automatically switched over to the standby link.
User Plane
The user plane at the radio network layer over the Iub interface uses a series of frame protocols
(FPs), including DCH FP, RACH FP, RACH FP, PCH FP, HS-DSCH FP, and E-DCH FP. These
FPs are responsible for transmitting data frames and control frames between the NodeB and
RNC, including user data and user-related control data over the Uu interface.
In Iub over ATM&IP, the user plane can work in active/standby mode (an AAL2 path and an
IP path are configured) to improve transmission reliability, as illustrated in Figure 2-3.
NOTE
The configuration illustrated in Figure 2-3 is applicable only when the BSC6900 and BSC6910 use IP
transmission pools.
You can configure multiple AAL2 and IP paths over the Iub interface and specify the usage of
each path. You can specify the usage of an IP path by setting the PATHT parameter and the
usage of an AAL2 path by setting the AAL2PATHT(BSC6900,BSC6910) parameter on the RNC
side.
You can use the ADD TRMMAP command to configure the transmission resource mapping
table and specify the active path and standby path for each service type. For example, you can
specify the active and standby paths for the AMR voice service by setting the
VOICEPRIPATH and VOICESECPATH parameters, respectively. The RNC provides a
default transmission resource mapping table.
When admitting a new call, the RNC preferentially uses the active path. When the active path
fails, the RNC tries to admit the new call on the standby path. For details, see Transmission
Resource Management Feature Parameter Description.
NOTE
If an AAL2 or IP path is unavailable, services carried on this path will be interrupted. A new service request
will be carried on an available path selected according to the information in the transmission resource
mapping table.
OM Plane
Configure the OM channel in ATM or IP transmission mode according to the network plan. For
details, see ATM Transport Feature Parameter Description and IP Transmission Feature
Parameter Description, respectively.
If the OM channel works in active/standby mode (not recommended), two OM channels are
configured on the base station side. At the same time, you need to configure two IP addresses
of the base station on the U2000, one for the OM channel in ATM transmission mode and the
other for the OM channel in IP transmission mode.
For information about the ATM transmission protocol stack, see ATM Transport Feature
Parameter Description.
For information about the IP transmission protocol stack, see IP Transmission Feature
Parameter Description.
For detailed configurations, see BSC6900 UMTS Initial Configuration Guide (or BSC6910
UMTS Initial Configuration Guide) and 3900 Series Base Station Initial Configuration Guide.
3 Networking
As network data services are booming and the High Speed Packet Access (HSPA) technique is
widely applied, the demand for bandwidth over the Iub interface is growing. A single ATM
network can provide high QoS but has high transmission costs, whereas an IP network can reduce
transmission costs. ATM&IP dual-stack transmission over the Iub interface combines the
advantages of both so services with different QoS requirements can be transmitted on different
networks.
Figure 3-1 illustrates the networking in Iub over ATM&IP.
As illustrated in Figure 3-1, the ATM network and IP network can carry services with different
QoS requirements.
l High-QoS ATM network: carries voice services, streaming services, and signaling.
l Low-QoS IP network: carries services with low QoS requirements, such as PS best effort
(BE) services.
In an actual network, both the RNC and NodeB must be configured with ATM interface boards
for connecting to the ATM network and IP interface boards for connecting to the IP network.
In Iub over ATM&IP, the ATM network can guarantee QoS while the IP network can reduce
transmission costs and provide high bandwidth for high-speed services over the Iub interface.
However, maintaining the ATM network and IP network simultaneously is more complex and
expensive.
In addition to the preceding non-transmission-resource mode, the BSC6900 can also use the
transmission resource pool mode in Iub over ATM&IP. For details, see Transmission Resource
Pool in RNC Feature Parameter Description.
The BSC6910 must use the transmission resource pool mode in Iub over ATM&IP. For details,
see Transmission Resource Pool in RNC Feature Parameter Description.
4 Related Features
Impacted Features
None
5 Network Impact
Network Performance
No impact.
6 Engineering Guidelines
The Iub interface supports the configuration of IP paths or transmission resource pools. This
document provides the engineering guidelines when IP paths are used. For the engineering
guidelines when the transmission resource pool is used, see Transmission Resource Pool in RNC
Feature Parameter Description.
l Physical layer data: port and VLAN configuration of the peer equipment.
l Transport layer data: IP addresses, maximum transmission units (MTUs), and differentiated
services code points (DSCPs) of the peer equipment and next-hop equipment. To deploy
ATM transmission, the permanent virtual channel (PVC), AAL2 configuration, and AAL5
configuration of the peer equipment are necessary.
l Data Link layer data: Stream Control Transmission Protocol (SCTP) link configuration on
the peer equipment.
6.1.3 Planning
Hardware Planning
l The following boards of the BSC6900 support this feature: UOIa/UOIc, AOUa/
AOUcAEUa, FG2a/FG2c, and GOUa/GOUc.
l The following boards of the BSC6910 support this feature: UOIc, AOUc, GOUc, XOUa,
and FG2c.
l The following boards of the BTS3900 support this feature: WMPT, UMPT, UTRP2,
UTRP3, UTRP4, UTRP9, and UTRPc.
l The BTS3902E and BTS3803E do not support this feature.
6.1.4 Deployment
Deployment Process
Figure 6-1 outlines the deployment process on the RNC side.
Figure 6-1 Iub over ATM&IP deployment process on the RNC side
NOTE
The process outlined in Figure 6-1 applies to ATM transmission deployment on the RNC side. For
information about deploying IP transmission on the BSC6900, see IP RAN Engineering Guide. For
information about deploying IP transmission on the BSC6910, see Transmission Resource Pool in RNC
Feature Parameter Description.
Figure 6-2 Iub over ATM&IP deployment process on the NodeB side
NOTE
The process shown in Figure 6-2 applies to ATM transmission deployment on the NodeB side. For
information about deploying IP transmission on the NodeB side, see IP RAN Engineering Guide.
Requirements
l Other Features
This feature depends on the following features:
– WRFD-050402 IP Transmission Introduction on Iub Interface
– WRFD-150243 Iub IP Transmission Based on Dynamic Load Balancing
l License
For details about how to activate the license, see License Management Feature Parameter
Description.
l Others
The ATM and IP transmission links from the RNC to the NodeB have been established.
Data Preparation
For data preparation on the RNC side, see section "Data Preparation for Initial Configuration"
in BSC6900 UMTS Initial Configuration Guide (MML-Based) or BSC6900 UMTS Initial
Configuration Guide (MML-Based).
For data preparation on the NodeB side, see section "NodeB Transport Data" in 3900 Series
Base Station Initial Configuration Guide.
Initial Configuration
l For details about activation using MML commands on the RNC side, see Configuring the
Interfaces > Configuring the Iub Interface (in ATM/IP Dual Stack Mode) in BSC6900
UMTS Initial Configuration Guide (MML-Based) or BSC6910 UMTS Initial Configuration
Guide (MML-Based). For details about activation using the CME on the RNC side, see
Configuring BSC6900 Data (General Configuration) > Configuring Interface Data in
BSC6900 UMTS Initial Configuration (CME-based) or BSC6910 UMTS Initial
Configuration (CME-based).
l For details about activation on the NodeB side, see 3900 Series Base Station Initial
Configuration (CME-based) > Creating Base Stations > Creating NodeBs > Creating
a Single NodeB > Configuring NodeB Transport Data > Configuring Physical NodeB
Transport Data (Non-Secure Networking) in 3900 Series Base Station Initial
Configuration Guide.
Activation Observation
l On the RNC side
Expected result: High-priority services are carried on the ATM path and low-priority services
are carried on the IP path.
Step 2 Run the BSC6900 MML command DSP IPPATH to check the status of the IP path and whether
any path resources are occupied.
Expected result: The command output indicates that the value of the Operation state parameter
is set to Available and the Used forward bandwidth of path and Used backward bandwidth
of path parameters are not set to 0. For the operations on the BSC6910, see Transmission
Resource Pool in RNC Feature Parameter Description.
Step 3 Run the BSC6900 MML command DSP AAL2PATH to check the status of the AAL2 path and
whether any path resources are occupied.
Expected result: The command output indicates that the Operation state parameter is set to
Available and the Used forward bandwidth of path and Used backward bandwidth of
path parameters are not set to 0.
Step 4 Run the BSC6900/BSC6910 MML command DSP SCTPLNK to check whether the SCTP link
is available.
Expected result: The command output indicates that the Operation state parameter is set to
Available.
Step 5 Run the BSC6900/BSC6910 MML command DSP SAALLNK to check whether the SAAL
link is available.
Expected result: The command output indicates that he Operation state parameter is set to
Available.
Step 6 (Optional) Start a Cell Trace task on the BSC6900/BSC6910 LMT. On the FMR tab, select
Transport Data Periodic Report and specify SCCPCH ID and Report Period of the cell to
be traced.
Expected result: On the Results of cell message tracing window, Trace Type is IP Interface
Trace.
Step 7 (Optional) Start an Iub Interface Trace task on the BSC6900/BSC6910 LMT. On the Basic
tab page, select SCTP, SAAL, and QAAL2. On the SAAL tab page, specify SAAL Link No.
On the SCTP tab page, specify SCTP Link No and select SCTP Message.
Expected result: On the Results of Tracing Messages on the Iub Interface window, Trace
Type is QAAL2 Message Trace and SCTP Message Trace.
----End
Table 6-1 lists the counters related to ATM&IP dual-stack transmission over the Iub interface
on the RNC side.
Table 6-1 Counters related to ATM&IP dual-stack transmission over the Iub interface on the
RNC side (BSC6900)
NOTE
For counters related to ATM&IP dual-stack transmission over the Iub interface on the BSC6910, see
Transmission Resource Pool in RNC Feature Parameter Description.
Step 1 Run the NodeB MML command DSP ETHPORT to check the Ethernet physical port status.
Step 2 Run the NodeB MML command DSP AAL2PATH to check whether the AAL2 path is available.
Step 3 Run the NodeB MML command DSP SAALLNK to check whether the SAAL link is available.
Step 4 Run the NodeB MML command DSP SCTPLNK to check whether the SCTP link is available.
Step 5 (Optional) Start the Iub Interface Trace, MAC Message Statistics and PPP Message
Statistics tasks on the NodeB LMT.
Expected result: There are traced messages. Services are carried on the SCTP link, Ethernet port,
and IP path.
----End
Table 6-2 lists the counters related to ATM&IP dual-stack transmission over the Iub interface
on the NodeB side.
Table 6-2 Counters related to ATM&IP dual-stack transmission over the Iub interface on the
NodeB side
Reconfiguration
For detailed operations, see RAN Reconfiguration Guide.
Deactivation
This feature does not need to be deactivated.
6.1.6 Troubleshooting
For details about troubleshooting on the RNC side, see section "Troubleshooting ATM
Transmission Faults" and "Troubleshooting IP Transmission Faults" in RAN Troubleshooting
Guide. For details about alarm handling procedures on the RNC side, see section "Transport
Alarm" in BSC6900 UMTS Alarm Reference or BSC6910 UMTS Alarm Reference.
7 Parameters
CARRY BSC690 ADD WRFD- IP Meaning: When the NCP/CCP is based on ATM, set
LNKT 0 UNCP 050402 Transmi Bearing link type to SAAL. When the NCP/CCP is
MOD WRFD- ssion based on IP, set Bearing link type to SCTP. When the
UNCP 050404 Introduc NCP/CCP is based on ATM/IP, set Bearing link type to
tion on SAAL-SCTP. For detailed information of this
Iub parameter, see 3GPP TS 25.430.
Interface GUI Value Range: SAAL(SAAL Link Type), SCTP
ATM/IP (SCTP Link Type), SAAL-SCTP(SAAL-SCTP Link
Dual Type)
Stack Unit: None
Node B
Actual Value Range: SAAL, SCTP, SAAL-SCTP
Default Value: None
CARRY BSC690 ADD WRFD- IP Meaning: When the NCP/CCP is based on ATM, set
LNKT 0 UCCP 050402 Transmi Bearing link type to SAAL. When the NCP/CCP is
MOD WRFD- ssion based on IP, set Bearing link type to SCTP. When the
UCCP 050404 Introduc NCP/CCP is based on ATM/IP, set Bearing link type to
tion on SAAL-SCTP. For detailed information of this
Iub parameter, see 3GPP TS 25.430.
Interface GUI Value Range: SAAL(SAAL Link Type), SCTP
ATM/IP (SCTP Link Type), SAAL-SCTP(SAAL-SCTP Link
Dual Type)
Stack Unit: None
Node B
Actual Value Range: SAAL, SCTP, SAAL-SCTP
Default Value: None
MAINL BSC690 ADD WRFD- ATM/IP Meaning: Preferred type of the link used to carry a link
INK 0 UCCP 050404 Dual when the bearer link type is SAAL-SCTP. When the
MOD Stack current bearer link fails, it will be automatically carried
UCCP Node B on the other type of bearer link. For detailed description
of this parameter, see 3GPP TS 25.430.
GUI Value Range: SAAL(SAAL Link Type ), SCTP
(SCTP Link Type)
Unit: None
Actual Value Range: SAAL, SCTP
Default Value: SAAL(SAAL Link Type )
MAINL BSC690 ADD WRFD- ATM/IP Meaning: Preferred type of the link used to carry a link
INK 0 UNCP 050404 Dual when the bearer link type is SAAL-SCTP. When the
MOD Stack current bearer link fails, it will be automatically carried
UNCP Node B on the other type of bearer link. For detailed description
of this parameter, see 3GPP TS 25.430.
GUI Value Range: SAAL(SAAL Link Type ), SCTP
(SCTP Link Type)
Unit: None
Actual Value Range: SAAL, SCTP
Default Value: SAAL(SAAL Link Type )
BELON BTS390 ADD None None Meaning: Indicates the flag of the transport channel to
G 0, IUBCP which an Iub control port belongs.
BTS390 DSP GUI Value Range: MASTER(MASTER), SLAVE
0 IUBCP (SLAVE)
WCDM
A RMV Unit: None
IUBCP Actual Value Range: MASTER, SLAVE
LST Default Value: MASTER(MASTER)
IUBCP
PATHT BSC690 ADD WRFD- One Meaning: This parameter specifies the type of an IP
0 IPPATH 020111 Tunnel path. It indicates the priority of the user plane data that
WRFD- IP is carried on the IP path. The mapping between the
050402 Transmi priority of the user plane data and IP path is configured
ssion through the "ADD TRMMAP" command. An IP path is
WRFD- of either the QoS type or the non-QoS type. For
050403 Introduc
tion on example, the IP paths used to carry BE data, AF data,
WRFD- Iub and EF data are all of the non-QoS type. Different data
050404 Interface can share the bandwidth of a QoS-type IP path. The
WRFD- bandwidth of a non-QoS type IP path, however, cannot
Hybrid be shared. IP path in hybrid IP transmission can be
050409 Iub IP further categorized into high-priority IP path and low-
Transmi priority IP path (identified as LQ_xx). When the bearing
ssion type of the physical port is PPP or MP, the IP path is
ATM/IP recommended to be configured as a high-priority path.
Dual When the physical port is an Ethernet port, the IP path
Stack is recommended to be configured as a low-priority path.
Node B For the non-QoS type IP path, the priority of EF data is
IP higher than that of AF data, which in turn is higher than
Transmi that of BE data. The actual priority of user plane data,
ssion however, is set through the "SET PHBMAP" command.
Introduc GUI Value Range: BE(BE), AF11(AF11), AF12
tion on (AF12), AF13(AF13), AF21(AF21), AF22(AF22),
Iu AF23(AF23), AF31(AF31), AF32(AF32), AF33
Interface (AF33), AF41(AF41), AF42(AF42), AF43(AF43), EF
(EF), QoS(QoS), LQ_BE(LQ_BE), LQ_AF11
(LQ_AF11), LQ_AF12(LQ_AF12), LQ_AF13
(LQ_AF13), LQ_AF21(LQ_AF21), LQ_AF22
(LQ_AF22), LQ_AF23(LQ_AF23), LQ_AF31
(LQ_AF31), LQ_AF32(LQ_AF32), LQ_AF33
(LQ_AF33), LQ_AF41(LQ_AF41), LQ_AF42
(LQ_AF42), LQ_AF43(LQ_AF43), LQ_EF(LQ_EF),
LQ_QOS(LQ_QOS)
Unit: None
Actual Value Range: QoS, BE, AF11, AF12, AF13,
AF21, AF22, AF23, AF31, AF32, AF33, AF41, AF42,
AF43, EF, LQ_QOS, LQ_BE, LQ_AF11, LQ_AF12,
LQ_AF13, LQ_AF21, LQ_AF22, LQ_AF23,
LQ_AF31, LQ_AF32, LQ_AF33, LQ_AF41,
LQ_AF42, LQ_AF43, LQ_EF
Default Value: None
AAL2P BSC690 ADD WRFD- Dedicate Meaning: Service type of carried over the PATH. For
ATHT 0 AAL2P 0213050 d Iub R99, only the R99 service can be carried. For HSPA,
ATH 1 Transmi only the HSPA service can be carried. For SHARE, R99
MOD WRFD- ssion and HSPA services can be carried at the same time.
AAL2P 0503010 Control GUI Value Range: R99(R99), HSPA(HSPA), SHARE
ATH 4 Dynami (SHARE)
c AAL2 Unit: None
Connect
ions in Actual Value Range: R99, HSPA, SHARE
Iub/ Default Value: None
IuCS/Iur
Interface
AAL2P BSC691 ADD WRFD- Dedicate Meaning: Service type of carried over the PATH. For
ATHT 0 AAL2P 0213050 d Iub R99, only the R99 service can be carried. For HSPA,
ATH 1 Transmi only the HSPA service can be carried. For SHARE, R99
MOD WRFD- ssion and HSPA services can be carried at the same time.
AAL2P 0503010 Control GUI Value Range: R99(R99), HSPA(HSPA), SHARE
ATH 4 Dynami (SHARE)
c AAL2 Unit: None
Connect
ions in Actual Value Range: R99, HSPA, SHARE
Iub/ Default Value: None
IuCS/Iur
Interface
VOICE BSC690 ADD WRFD- ATM Meaning: AMR voice service bearer primary path.
PRIPAT 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
H AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE, LQAF11,
TRMM Hub LQAF12, LQAF13, LQAF21, LQAF22, LQAF23,
AP Node B LQAF31, LQAF32, LQAF33, LQAF41, LQAF42,
(Overbo LQAF43, LQEF
oking on
Hub Unit: None
Node B Actual Value Range: CBR, RT_VBR, NRT_VBR,
Transmi UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
ssion) AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF
Default Value: None
VOICE BSC690 ADD WRFD- ATM Meaning: AMR voice service bearer secondary path.
SECPA 0 TRMM 050406 QoS GUI Value Range: CBR, RT_VBR, NRT_VBR, UBR,
TH AP Introduc BE, AF11, AF12, AF13, AF21, AF22, AF23, AF31,
MOD tion on AF32, AF33, AF41, AF42, AF43, EF, LQBE, LQAF11,
TRMM Hub LQAF12, LQAF13, LQAF21, LQAF22, LQAF23,
AP Node B LQAF31, LQAF32, LQAF33, LQAF41, LQAF42,
(Overbo LQAF43, LQEF, NULL
oking on
Hub Unit: None
Node B Actual Value Range: CBR, RT_VBR, NRT_VBR,
Transmi UBR, BE, AF11, AF12, AF13, AF21, AF22, AF23,
ssion) AF31, AF32, AF33, AF41, AF42, AF43, EF, LQBE,
LQAF11, LQAF12, LQAF13, LQAF21, LQAF22,
LQAF23, LQAF31, LQAF32, LQAF33, LQAF41,
LQAF42, LQAF43, LQEF, NULL
Default Value: None
TnlBear BSC690 ADD WRFD- IP Meaning: Transport type of the Iub interface.
erType 0 UNODE 050402 Transmi GUI Value Range: ATM_TRANS(ATM circuit
B ssion transmission), IP_TRANS(IP transmission),
MOD Introduc ATMANDIP_TRANS(ATM and IP transmission),
UNODE tion on HYBRID_IP_TRANS(Hybrid IP transmission)
B Iub
Interface Unit: None
Actual Value Range: ATM_TRANS, IP_TRANS,
ATMANDIP_TRANS, HYBRID_IP_TRANS
Default Value: ATM_TRANS(ATM circuit
transmission)
TnlBear BSC691 ADD None None Meaning: Transport type of the Iub interface.
erType 0 UNODE GUI Value Range: ATM_TRANS(ATM circuit
B transmission), IP_TRANS(IP transmission),
MOD ATMANDIP_TRANS(ATM and IP transmission)
UNODE Unit: None
B
Actual Value Range: ATM_TRANS, IP_TRANS,
ATMANDIP_TRANS
Default Value: ATM_TRANS(ATM circuit
transmission)
NODET BSC690 ADD WRFD- Hybrid Meaning: Type of the adjacent node.
0 ADJNO 050403 Iub IP GUI Value Range: IUB(Iub Interface), IUR(Iur
DE WRFD- Transmi Interface), IUCS(Iu-CS Interface), IUPS(Iu-PS
MOD 050404 ssion Interface), UNI_AAL2SWITCH(the adjacent node of
ADJNO WRFD- ATM/IP the ATM switch on the Iub interface),
DE 020111 Dual NNI_AAL2SWITCH(the adjacent node of ATM switch
Stack on Iur or Iu-CS interface), IURP(Iurp Interface)
WRFD- Node B
150211 Unit: None
One Actual Value Range: IUB, IUR, IUCS, IUPS,
WRFD- Tunnel
0213050 UNI_AAL2SWITCH, NNI_AAL2SWITCH, IURP
1 RNC in Default Value: None
Pool
WRFD- Load
0503010 Sharing
4
Dedicate
WRFD- d Iub
140207 Transmi
WRFD- ssion
140208 Control
WRFD- Dynami
150212 c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
Iu/Iur
Transmi
ssion
Resourc
e Pool in
RNC
Iub
Transmi
ssion
Resourc
e Pool in
RNC
RNC in
Pool
Node
Redunda
ncy
NODET BSC691 ADD WRFD- RNC in Meaning: Type of the adjacent node.
0 ADJNO 150212 Pool GUI Value Range: IUB(Iub Interface), IUR(Iur
DE WRFD- Node Interface), IUCS(Iu-CS Interface), IUPS(Iu-PS
MOD 150211 Redunda Interface), UNI_AAL2SWITCH(the adjacent node of
ADJNO ncy the ATM switch on the Iub interface),
WRFD-
DE 150244 RNC in NNI_AAL2SWITCH(the adjacent node of ATM switch
Pool on Iur or Iu-CS interface), IURP(Iurp Interface), SE(SE
WRFD- Load Interface)
0503010 Sharing
4 Unit: None
Iu/Iur IP Actual Value Range: IUB, IUR, IUCS, IUPS,
WRFD- Transmi
150243 UNI_AAL2SWITCH, NNI_AAL2SWITCH, IURP,
ssion SE
WRFD- Based
020111 on Default Value: None
Dynami
c Load
Balance
Dynami
c AAL2
Connect
ions in
Iub/
IuCS/Iur
Interface
Iub IP
Transmi
ssion
Based
on
Dynami
c Load
Balance
One
Tunnel
ISIPPO BSC690 ADD WRFD- UDP Meaning: Whether the networking mode of the interface
OL 0 ADJNO 050412 MUX boards of the RNC connected to this adjacent node is IP
DE WRFD- for Iu- POOL. If this mode is selected, load will be shared
MOD 050402 CS among boards in the pool. When the capacity of the peer
ADJNO Transmi NEs is expanded, the RNC requires no configuration
WRFD- ssion modification. When the transmission capacity is
DE 050410
IP expanded, base stations do not need to be swapped and
WRFD- Transmi services will not be interrupted.
050409 ssion GUI Value Range: NO(No), YES(Yes)
WRFD- Introduc Unit: None
140207 tion on
Iub Actual Value Range: NO, YES
WRFD-
140208 Interface Default Value: NO(No)
WRFD- IP
050420 Transmi
ssion
Introduc
tion on
Iur
Interface
IP
Transmi
ssion
Introduc
tion on
Iu
Interface
Iu/Iur
Transmi
ssion
Resourc
e Pool in
RNC
Iub
Transmi
ssion
Resourc
e Pool in
RNC
FP
MUX
for IP
Transmi
ssion
8 Counters
9 Glossary
10 Reference Documents