Professional Documents
Culture Documents
RAN15.0
Issue 01
Date 2013-04-28
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
1 Introduction....................................................................................................................................1
1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
7 Parameters.....................................................................................................................................44
8 Counters........................................................................................................................................92
9 Glossary.......................................................................................................................................161
10 Reference Documents.............................................................................................................162
1 Introduction
1.1 Scope
This document merges the basic ATM transport principle. It describes protocol stacks,
transmission resources, transmission resource management (TRM), and associated parameters.
Document Issues
The document issues are as follows:
l 01 (2013-04-28)
l Draft A (2013-01-30)
01 (2013-04-28)
This is the first commercial release of RAN15.0.
Compared with issue Draft A (2013-01-30) of RAN15.0, this issue has no change.
Draft A (2013-01-30)
This is the draft of the document for RAN15.0
Compared with issue 01 (2012-07-20) of RAN14.0, this issue incorporates the changes described
in the following table.
Huawei radio access network (RAN) provides ATM-based Iub/Iu(Iu-CS and Iu-PS)/Iur
interfaces and ATM TRM, such as admission control based on AAL2 path bandwidth;
transmission resource mapping based on ATM QoS classes, and Iub overbooking.
NOTE
3 Protocol Stacks
The transport network layer of the Iub interface consists of the transport network layer user plane
(area A), transport network layer control plane (area B), and transport network layer user plane
(area C).
l Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the three
areas can be carried on common physical links.
l Links in areas A and B are carried on SAAL links. Based on the type of carried information,
the upper layer of area A is classified into the NodeB Control Port (NCP) and the
Communication Control Port (CCP). Only Q.AAL2 links are carried in area B.
l In area C, the user plane data is carried on AAL2 paths. The bearer at the lower layer is the
ATM PVC. Under the control of Q.AAL2, AAL2 connections can be dynamically set up
or released for upper-layer services. Therefore, each AAL2 path must have its
corresponding controlling Q.AAL2.
NOTE
The RINT shown in Figure 3-2 refers to ATM interface boards UOIa/UOIc, AOUa/AOUc, and AEUa for
BSC6900, UOIc/AOUc for BSC6910.
NOTE
The RINT shown in Figure 3-3 refers to ATM interface boards UOIa/UOIc, AOUa/AOUc, and AEUa for
BSC6900, UOIc/AOUc for BSC6910.
Network Segments
Iub OM channel travels through the following network segments before reaching the NodeB:
l The 80.168.3.0 segment (with network mask of 255.0.0.0) between the OM board and the
ATM interface board. This network segment is set before delivery of the BSC6900.
l The 12.13.1.0 segment (with network mask of 255.255.255.0) between the ATM interface
board and the NodeBs. When setting this network segment, you need to take field conditions
into consideration.
The transport network layer of the Iu-CS interface consists of the following areas:
l Transport network layer user plane (area A)
l Transport network layer control plane (area B)
l Transport network layer user plane (area C)
Areas A, B, and C share the physical layer and ATM layer. Therefore, all links in the three areas
can be carried on common physical links.
The MSC in an R99 network implements the functions in areas A, B, and C of the protocol stack.
The MSC server and MGW in an R4/R5/R6/R7/R8 network implement their functions as
follows:
l The MSC server implements the functions in area A.
l The MGW implements the functions in areas B and C.
NOTE
The RINT shown in Figure 3-5 refers to ATM interface boards UOIa/UOIc for BSC6900, UOIc for
BSC6910.
The network may require multiple MGWs depending on the traffic volume.
In practice, the MSC server is often not directly connected to the RNC. Data is forwarded
between the MSC server and the RNC through the routes configured on the MGW. Figure
3-7 shows an example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/
R7/R8.
Figure 3-7 Example of the network structure on the Iu-CS interface in the 3GPP R4/R5/R6/R7/
R8
In the 3GPP R4/R5/R6/R7/R8, the RNC needs to be configured with the following two types of
Iu-CS signaling point:
Table 3-1 describes the differences between signaling point configuration in R99 and that in
R4/R5/R6/R7/R8.
Table 3-1 Differences between signaling point configuration in R99 and that in R4/R5/R6/R7/
R8
The transport network layer of the Iu-PS interface consists of the transport network layer user
plane (area A) and the transport network layer user plane (area C).
Areas A and C share the physical layer and ATM layer. Therefore, all links in the two areas can
be carried on common physical links.
NOTE
NOTE
The RINT shown in Figure 3-10 refers to ATM interface boards UOIa/UOIc.
Table 3-2 IPoA data on the user plane of the ATM-based Iu-PS interface
Item Description
Local IP address of the IPoA PVC (IPADDR Device IP address on the ATM interface
(UMTS BSC6900,UMTS BSC6910)) board of the RNC
Peer IP address of the IPoA PVC IP address of the gateway on the SGSN side
(PEERIPADDR(UMTS BSC6900,UMTS
BSC6910))
Route between the interface board carrying If the IP address of the interface board
the IPoA data and the network segment of the carrying the IPoA data and the IP address of
peer SGSN the peer SGSN are located on different
subnets, routes to the destination IP address
need to be configured at the RNC. DSTIP
(UMTS BSC6900,UMTS BSC6910) is the IP
address of the SGSN, and NEXTHOP
(UMTS BSC6900,UMTS BSC6910) is the IP
address of the gateway on the SGSN side.
NOTE
On the Iu-PS interface, the SGSN must be configured with routes to the network segment to which the IP
address of the RNC interface board belongs. The next hop is the gateway on the RNC side. Otherwise, PS
services cannot be provided.
The transport network layer of the ATM-based Iur interface consists of the following areas:
l Transport network layer user plane (area A)
l Transport network layer control plane (area B)
l Transport network layer user plane (area C)
NOTE
The RINT shown in Figure 3-12 refers to ATM interface boards UOIa/UOIc for BSC6900, UOIc for
BSC6910.
NOTE
The RINT shown in Figure 3-13 refers to Iu-PS IP interface boards GOUa/GOUc, FG2a/FG2c, and UOIa
(UOIa_IP) for BSC6900, GOUc/FG2c/EXOUa for BSC6910.
Figure 3-14 Mapping between the ATM cell and the E1 timeslots in UNI mode
The UNI mode has the characteristics of scrambling, line coding, 16-timeslot enabling, and clock
mode. The related parameters are as follows:
l Scrambling switch: specifies whether to enable scrambling.
l Line coding method: specifies the line coding method.
l 16-timeslot switch: specifies whether to use timeslot 16 or not.
The settings of scrambling switch, line coding method, and 16-timeslot switch at both ends of
E1/T1 must be identical.
The parameters corresponding to UNI mode are shown in Table 3-3.
Note:
Clock Mode
There are two clock modes on the RNC side:
l Common Transmit Clock (CTC): In CTC clock mode, all links in an IMA group share one
clock source. The clock source may be extracted from the same external clock or from a
link.
l Independent Transmit Clock (ITC): In ITC mode, the clocks used by the links within an
IMA group are derived from at least two clock sources. The loopback clock mode is a
special case of the ITC mode.
The clock mode on the RNC is not configurable, and the default clock mode on the RNC side
is CTC.
The clock mode on the NodeB side is specified by the parameter CLKM(UNI mode/fractional
mode)/CLKM(IMA mode). The clock mode settings at both ends of E1/T1 must be identical.
The coding methods of E1 port are HDB3 and AMI, and the HDB3 is recommended. HDB3
represents high-density bipolar code. It is not easy to be interfered, and the transmission distance
is about several kilometers.
The coding methods of T1 port are B8ZS and AMI, and B8ZS is recommended. It helps prevent
clock signals from being lost, while AMI cannot perform this function.
If multiple E1/T1 trunks exist between the transmission end and the reception end and work in
IMA mode, such an IMA mode is called fractional IMA. In fractional IMA mode, an IMA group
contains multiple fractional ATM links.
The fractional ATM mode has the characteristics of scrambling, line coding, and clock mode.
For details about clock mode, see Clock Mode. The related parameters are as follows:
l Scrambling switch: specifies whether to enable scrambling.
l Line coding method: specifies the line coding method.
l E1/T1 timeslot: specifies the timeslot used to transmit the ATM cell.
The setting of scrambling switch, line coding method, and E1/T1 timeslot at both ends of E1/
T1 must be identical.
The parameters corresponding to fractional mode are shown in Figure 3-16.
Note:
Only AEUa support the parameter PTCODE.
Overview
IMA mode (WRFD-050304 IMA Transmission for E1T1 or Channelized STM-1/OC-3 on Iub
Interface) is applicable to the Transmission Convergence (TC) sublayer of the physical layer.
The IMA function is implemented by the IMA group, which is composed of either IMA links
or fractional IMA links.
All IMA links within an IMA group must be of the same type, either common IMA link or
fractional IMA link. If an IMA group is composed of fractional IMA links, the quantity of
timeslots carrying each fractional IMA link must be identical.
l At the transmission end, the IMA group receives the ATM cell stream from the ATM layer
and distributes the cells among the E1/T1 links.
l At the reception end, the IMA group reassembles the cells to restore the original ATM cell
stream, and then transfers the cell stream to the ATM layer.
The physical layer provides high-speed transport channels for ATM cells from the perspective
of the ATM layer.
In IMA mode, ATM cells, IMA Control Protocol (ICP) cells, and filler cells form an IMA frame
to implement necessary controlling functions.
The length of an IMA frame, m, is defined during the setup of an IMA group. The parameter
FRMLEN(UMTS BSC6900,UMTS BSC6910)(at the RNC)/FRMLEN (at the NodeB) is used
to specify the length of an IMA frame.
Figure 3-18 shows an IMA frame. The mapping between the ATM cell and the physical link
(that is, the E1/T1 link) is similar to that in UNI mode.
The IMA mode has the characteristics of scrambling, line coding, 16-timeslot enabling, and
clock mode. The clock mode of an IMA group is defined from the perspective of an IMA group
rather than a single link. For details about clock mode, see Clock Mode. The related parameters
are as follows:
The setting of scrambling switch, line coding method, and 16-timeslot switch at both ends of
E1/T1 must be identical.
NOTE
NOTE
Neither the source timeslot nor the target timeslot of a timeslot cross connection can be used by other
applications, such as fractional ATM, IMA, and UNI.
If an E1 link is configured with a timeslot cross connection, the E1 link cannot carry any IMA or UNI link.
The other timeslots on this E1 link can carry fractional ATM or fractional IMA links.
Variable Bit Rate (RT-VBR), Non-Real-Time Variable Bit Rate (NRT-VBR), Unspecified Bit
Rate (UBR), and UBR_PLUS (UBR+).
Table 3-7 describes the types of service.
Feedback on No No No No No
congestion
The ATM service type is also called ATM QoS class. The CBR, RT-VBR, NRT-VBR, or UBR
ATM QoS classes can be configured for AAL2 path, and the UBR+ ATM QoS class is generally
used for Iub OAM connection.
The service types carried on the AAL2 paths can be determined by running the ADD
ATMTRF command, and then the mapping between the service types and the transmission
resources for the adjacent node can be configured by running the ADD TRMMAP command.
Traffic Parameters
Traffic parameters refer to the parameters used by each PVC for flow control.
Parameter ID Description
Parameter ID Description
NOTE
l In practice, ATM traffic records should be negotiated between the local and the peer equipment.
l The ATM traffic parameters, such as PCR(UMTS BSC6900,UMTS BSC6910) and SCR(UMTS
BSC6900,UMTS BSC6910), should be configured depending on the traffic model in use.
l When configuring ATM traffic records for links, you need to consider the traffic on the interface boards
of the RNC.
3.8 AAL5
In ATM transport mode, AAL5 connections are used to carry the signaling on the Iub/Iur/Iu
interface (WRFD-05030105 permanent AAL5 connections for control plane traffic). As defined
in 3GPP specifications, UNI-SAAL is used for control plane connections on the Iub interface,
and NNI-SAAL is used for control plane connections on the Iur and Iu interfaces. The AAL5
connections for Iub/Iu-CS/Iur are set up by configuring the SAAL links.
You can run the ADD SAALLNK command to configure the AAL5 connections on the Iub/
Iur/Iu interface. On the RNC side, when an AAL5 connection is configured, the TXTRFX
(UMTS BSC6900,UMTS BSC6910) and RXTRFX(UMTS BSC6900,UMTS BSC6910)
parameters need to be set. The TXTRFX(UMTS BSC6900,UMTS BSC6910) and RXTRFX
(UMTS BSC6900,UMTS BSC6910) parameters record the ATM traffic, and they can be
configured through the ADD ATMTRF command.
An SAAL link is carried on an ATM PVC. The parameters CARRYVPI(UMTS
BSC6900,UMTS BSC6910) and CARRYVCI(UMTS BSC6900,UMTS BSC6910) are used to
identify the PVCs on the RNC side, and the parameters VPI and VCI are used to identify the
PVCs on the NodeB side. The PVC identifier and other PVC attributes must be negotiated
between the RNC and the peer end.
The signaling messages carried on the UNI-SAAL links are classified into NCP, CCP, and
ALCAP, and the signaling messages carried on the NNI-SAAL links are MTP3, as described in
Table 3-11.
l CBR
l RT-VBR
l NRT-VBR
l UBR
According to different types of service (R99, HSDPA, and HDUPA), the following types of
AAL2 path can be configured:
l R99
l HSPA
l SHARE
The AAL2 path can be configured through the ADD AAL2PATH command. On the RNC side,
when an AAL2 path is configured, the TXTRFX(UMTS BSC6900,UMTS BSC6910) and
RXTRFX(UMTS BSC6900,UMTS BSC6910) parameters need to be set. They determine the
type of path. The TXTRFX(UMTS BSC6900,UMTS BSC6910) and RXTRFX(UMTS
BSC6900,UMTS BSC6910) parameters record the ATM traffic, and they can be configured
through the ADD ATMTRF command. For details, see section 3.7.3 ATM Traffic Records.
NOTE
l Even if the destination node and the adjacent node are the same, an AAL2 route needs to be configured.
l The AAL2 route cannot be configured for the adjacent node of the IUPS type.
3.10 MTP3
l If the MSC server is directly connected to the RNC, at least one MTP3 link is required for
the MSC server (IUCS_RANAP signaling point). It is recommended that more than one
MTP3 link be configured.
l If the MSC server is connected to the RNC through the MGW, the MSC server
(IUCS_RANAP signaling point) does not require any MTP3 link.
l If the MSC server is connected to the RNC not only directly but also through the MGW,
as shown in Figure 3-24, the MSC server (IUCS-RANAP) requires at least one MTP3 link.
It is recommended that more than one MTP3 link be configured.
Figure 3-24 Example of connections between the MSC server and the RNC
l If the RNC is directly connected to the neighboring RNC, the Iur interface requires at least
one MTP3 link. It is recommended that more than one MTP3 link be configured.
l If the RNC is connected to the neighboring RNC through a Signaling Transfer Point (STP),
no MTP3 link is required.
It is recommended that the SAAL links of NNI type be evenly distributed to the CPUS
subsystems in the MPS/EPS so that the signaling exchange can be reduced between the CPUS
subsystems.
Figure 3-25 Relation between signaling link mask and signaling route mask
3.12 F5
Huawei supports operations on ATM OAM F5 end-to-end flows specified in ITU I.610
(WRFD-05030110 F5):
l Fault management
AIS: alarm indication signal
RDI: remote defect indication
CC: continuity check and loopback
l Performance management
Forward monitoring
Backward reporting
l Activation and deactivation
The CC can be activated to monitor the end-to-end AAL2 path virtual connect link (VCL) and
Iu-PS user plane VCL. When one VCL for AAL2 path or Iu-PS GTPU is loss of continuity
(LOC), AIS, or RDI, this VCL is blocked. Then the service is established on other alternative
VCLs to prevent the failure of the call. You can run the ACT VCLCC command to activate the
CC function and the DEA VCLCC command to deactivate the CC function. When the parameter
VCLTYPE is set to CC, the CC function is activated.
Huawei also supports proprietary delay detection function. When an NE receives a detection
start command from the NMS, it starts detecting delay on the current AAL2 link or AAL5 link
and periodically reports the delay to the NMS. The 8-byte reserved IE (LB IE) in the loopback
message is used to store the message transmission time. When an NE receives the loopback
message, it calculates the delay based on the time difference between transmission and reception.
ATM transmission resources can be classified into physical resources, logical ports, resource
groups, and paths. The transmission resources for Iub/Iu/Iur interfaces vary according to
different networking. Huawei supports the following types of ATM transmission:
l ATM over E1T1 on Iub interface (WRFD-05030101 ATM over E1T1 on Iub interface)
The BSC6910 does not support this feature.
l ATM over channelized STM-1/OC-3 on Iub interface (WRFD-05030102 ATM over
channelized STM-1/OC-3 on Iub interface)
l ATM over non-channelized STM-1/OC-3c on Iub/Iu/Iur interface (WRFD-05030103
ATM over non-channelized STM-1/OC-3c on Iub/Iu/Iur interface)
For details about the ATM transmission resources, see "Transmission Resources" in the
Transmission Resource Management Feature Parameter Description.
For ATM transport, Huawei provides the following transmission resource management:
l Admission control (WRFD-05030106 Call Admission Based on Used AAL2 Path
Bandwidth), which is used to allow more users to be admitted with the QoS guaranteed.
l Transmission resource mapping, in which the CBR, RT-VBR, NRT-VBR, and UBR ATM
QoS classes are used to implement differentiated services.
l Iub overbooking (WRFD-050405 Overbooking on ATM Transmission, WRFD-050406
ATM QoS Introduction on Hub Node B (Overbooking on Hub Node B Transmission)),
which is used to improve the usage efficiency on ATM transport scenario
For details about admission control, transmission resource mapping, and Iub overbooking, see
the Transmission Resource Management Feature Parameter Description.
6 Engineering Guidelines
6.1.1 Prerequisites
l Dependencies on Hardware
BTS3902E and BTS3803E does not support this feature.
l Dependencies on Other Features
None
l License
This feature is not under license control.
l Other Prerequisites
The RAN is based on ATM transmission.
6.1.2 Procedure
Activation Procedure
Step 1 Run the RNC MML command ADD ADJNODE (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > Adjacent Node, IUR Configuration
Express > ATM Transport > Adjacent Node, IUCS Configuration Express > ATM Transport >
Adjacent Node; CME batch modification center: not supported) to add an adjacent node. Set the
parameter Adjacent Node Type to IUB, IUR, or IUCS, and the parameter Transport Type to
ATM. If the node is the lowest leaf node of the switching network, set the parameter Is Root
Node to YES; otherwise, set the parameter Is Root Node to NO.
NOTE:
For an adjacent node on the Iur or Iu-CS interface, the parameter Adjacent Node Type of its
upper-level hub node must be NNI_AAL2SWITCH; for an adjacent node on the Iub interface,
the parameter Adjacent Node Type of its upper-level hub node must be
UNI_AAL2SWITCH.
Step 2 Run the RNC MML command ADD AAL2PATH (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > AAL2 Path, IUCS Configuration
Express > ATM Transport > AAL2 Path, IUR Configuration Express > ATM Transport > AAL2
Path; CME batch modification center: not supported) to add an AAL2 path. The parameters
CARRYVPI and CARRYVCI must be consistent with those of the AAL2 path configured on
the peer end.
----End
Verification Procedure
Step 1 Run the RNC MML command DSP AAL2PATH to query the status of the AAL2 path on the
Iub interface.
Expected result: The value of Operation state is Available.
Step 2 In the Iub/Iu-CS ATM transmission scenario, a UE in idle state camps on CELL1 and the control
plane is correctly configured. Originate the speech and data services. If the service access is
normal, the AAL2 path on the Iub/Iu-CS interface is set up successfully.
Step 3 Optional: In the ATM transmission scenario on the Iur interface, a UE in idle state camps on
CELL1 and the control plane is correctly configured. Originate a cross-Iur handover. If the
handover is successful, the AAL2 path on the Iur interface is set up successfully.
----End
Deactivation Procedure
This feature does not need to be deactivated.
6.1.3 Example
//Activating Dynamic AAL2 Connections in Iub/IuCS/Iur Interface
//Adding an adjacent node
ADD ADJNODE: ANI=2, NAME="MSC1", NODET=IUCS, TRANST=ATM, IsROOTNODE=YES, DPX=1;
//Adding an AAL2 path
ADD AAL2PATH: ANI=2, PATHID=1, CARRYT=UNI, CARRYF=1, CARRYSN=14, CARRYUNILNKN=0,
RSCGRPFLAG=NO, VPI=12, VCI=126, TXTRFX=111, RXTRFX=111, AAL2PATHT=R99;
6.2.1 Prerequisites
l Dependencies on Hardware
BTS3902E and BTS3803E does not support this feature.
6.2.2 Procedure
Activation Procedure
Step 1 Run the RNC MML command ADD SAALLNK (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > SAAL Signaling Link, IUCS
Configuration Express > ATM Transport > SAAL Signaling Link, IUR Configuration Express
> ATM Transport > SAAL Signaling Link; CME batch modification center: not supported) to
add an SAAL link. If the interface is Iub, set the parameter Interface type to UNI. If the interface
is Iu or Iur, set Interface type to NNI.
Step 2 Optional: Run the RNC MML command ADD UNCP (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > NCP Link; CME batch modification
center: not supported) to add a NodeB Control Port (NCP) link.
Step 3 Optional: Run the RNC MML command ADD UCCP (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > CCP Link; CME batch modification
center: not supported) to add a Communication Control Port (CCP) link.
----End
NOTE:
An SAAL link can carry only one NCP or CCP link. Therefore, choose to perform step 2 or step
3 based on the actual situation.
Verification Procedure
Run the RNC MML command DSP SAALLNK to query the status of the SAAL link.
Deactivation Procedure
NOTE:
An SAAL link can carry only one NCP or CCP link. Therefore, choose to remove the NCP or
CCP link carried by the SAAL link, based on the actual situation.
Step 1 Optional: Run the RNC MML command RMV UNCP (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > NCP Link; CME batch modification
center: not supported) to remove the NCP link carried by the SAAL link.
Step 2 Optional: Run the RNC MML command RMV UCCP (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > CCP Link; CME batch modification
center: not supported) to remove the CCP link carried by the SAAL link.
Step 3 Run the RNC MML command RMV SAALLNK (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > SAAL Signaling Link, IUCS
Configuration Express > ATM Transport > SAAL Signaling Link, IUR Configuration Express
> ATM Transport > SAAL Signaling Link; CME batch modification center: not supported) to
remove the SAAL link.
----End
6.2.3 Example
//Activating Permanent AAL5 Connections for Control Plane Traffic
ADD SAALLNK: SRN=1, SN=2, SAALLNKN=10, CARRYT=UNI, CARRYSRN=0, CARRYSN=14,
CARRYUNILNKN=2, CARRYVPI=10, CARRYVCI=55, TXTRFX=100, RXTRFX=100, SAALLNKT=UNI;
ADD UCCP: NODEBNAME="NodeB1", PN=0, CARRYLNKT=SAAL, SAALLNKN=10;
//Verifying Permanent AAL5 Connections for Control Plane Traffic
DSP SAALLNK: SRN=1, SN=2, SAALLNKN=10;
//Deactivating Permanent AAL5 Connections for Control Plane Traffic
RMV UCCP: NODEBNAME="NodeB1", PN=0; RMV SAALLNK: SRN=1, SN=2, SAALLNKN=10;
6.3.1 Prerequisites
l Dependencies on Hardware
BTS3902E and BTS3803E does not support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
6.3.2 Procedure
Activation Procedure
Step 1 Run the RNC MML command ADD ATMTRF (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > ATM Traffic Record; CME batch
modification center: not supported) to set parameters to appropriate values. For example, set
Service type to NRTVBR, Peak cell rate to 100, and Sustainable cell rate to 80.
Step 2 Run the RNC MML command ADD AAL2PATH (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > AAL2 Path; CME batch modification
center: not supported) to add an ATM Adaptation Layer type 2 (AAL2) path. In this step, set
TXTRFX and RXTRFX in accordance with the settings in step 1.
----End
Verification Procedure
Step 1 Assume that the verification is based on the preceding parameter settings and the peer end is
configured with the corresponding AAL2 path link. Originate a PS interactive service. If the
data rate is 64 kbit/s, the UE successfully accesses the network.
Step 2 Run the RNC MML command DSP AAL2PATH to view that the used bandwidth of the path
is about 37 kbit/s, which is the admission bandwidth of the control plane.
Step 3 Originate a PS interactive service. If the data rate is 128 kbit/s, the UE fails to access the network.
----End
Deactivation Procedure
This feature does not need to be deactivated.
6.3.3 Example
//Activation procedure
ADD ATMTRF: TRFX=100, ST=NRTVBR, UT=CELL/S, PCR=100, SCR=80;
ADD AAL2PATH: ANI=0, PATHID=10, CARRYT=UNI, CARRYF=1, CARRYSN=14, CARRYUNILNKN=0,
RSCGRPFLAG=NO, VPI=12, VCI=126, TXTRFX=100, RXTRFX=100, AAL2PATHT=R99;
6.4.1 Prerequisites
l Dependencies on Hardware
BTS3902E and BTS3803E does not support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
6.4.2 Procedure
Activation Procedure
Run the RNC MML command ADD ATMTRF (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > ATM Traffic Record; CME batch
modification center: not supported) to add an ATM traffic record. To add more ATM traffic
records, run this command repeatedly.
Verification Procedure
Run the RNC MML command LST ATMTRF to query the ATM traffic configuration. The
expected result is that the query result is consistent with the configuration information.
Deactivation Procedure
Run the RNC MML command RMV ATMTRF (CME single configuration: NodeB
Configuration Express > IUB_RNC > ATM Transport > ATM Traffic Record; CME batch
modification center: not supported) to delete an ATM traffic record. To delete more ATM traffic
records, run this command repeatedly.
6.4.3 Example
//Activating CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
ADD ATMTRF: TRFX=105, ST=CBR, UT=CELL/S, PCR=1000;
//Verifying CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
LST ATMTRF: TRFX=105;
Deactivating CBR, rt-VBR, nrt-VBR, UBR ATM QoS Classes
RMV ATMTRF: TRFX=105;
6.5 WRFD-05030110 F5
This section describes how to activate, verify, and deactivate the basic feature WRFD-05030110
F5. (This feature cannot be configured using the CME. )
6.5.1 Prerequisites
l Dependencies on Hardware
Dependencies on the RNC side
None.
Dependencies on the NodeB side
Only 3900 series Base Station supports the passive detection based on IE LB.
BTS3902E and BTS3803E does not support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l Other Prerequisites
The basic information about the RNC is configured. For details, see the Configuring
the Basic Data.
The SAALLNK, AAL2PATH, or IPOAPVC link exists.
6.5.2 Procedure
Activation Procedure
Step 1 Run the RNC MML command ACT VCLCC to activate the VCL CC or loopback function for
a link. To activate the function for multiple links, run this command repeatedly. There are three
types of links, that is, SAALLNK, AAL2PATH, and IPOAPVC.
Step 2 Run the RNC MML command ACT VCLPM to activate the VCL PM function for a link. To
activate the function for multiple links, run this command repeatedly. There are three types of
links, that is, SAALLNK, AAL2PATH, and IPOAPVC.
----End
Verification Procedure
Step 1 Run the RNC MML command DSP VCLCC to query the CC result of a VCL.
l If the VCL CC is activated and the PVC is functional, the SINK activated state and
SOURCE activated state are UP, and LOC, AIS, and RDI alarm state is normal.
l If the loopback is activated and the PVC is functional, the loopback query result is UP, and
LOC, AIS, and RDI alarm state is normal.
Step 2 Run the RNC MML command DSP VCLPM to query the PM result of a VCL.
l If the VCL PM is activated, the SINK activated state and SOURCE activated state are
PM_UP, and PM Active Fail Alarm is Normal.
----End
Deactivation Procedure
Step 1 Run the RNC MML command DEA VCLCC to deactivate the VCL CC or loopback function
for a link. To deactivate the function for multiple links, run this command repeatedly. There are
three types of links, that is, SAALLNK, AAL2PATH, and IPOAPVC.
Step 2 Run the RNC MML command DEA VCLPM to deactivate the VCL PM for a link. To deactivate
the function for multiple links, run this command repeatedly. There are three types of links, that
is, SAALLNK, AAL2PATH, and IPOAPVC.
----End
6.5.3 Example
//Activating F5
ACT VCLCC: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0, VCLTYPE=CC;
ACT VCLPM: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;
//Verifying F5
DSP VCLCC: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;
DSP VCLPM: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;
//Deactivating F5
DEA VCLCC: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;
DEA VCLPM: LNKT=SAALLNK, SRN=3, SN=2, SAALLNKN=0;
6.6.1 Prerequisites
l Dependencies on Hardware
BTS3902E and BTS3803E does not support this feature.
l Dependencies on Other Features
This feature does not depend on other features.
l License
This feature is not under license control.
l Other Prerequisites
The basic information about the RNC is configured. For details, see the Configuring the
Basic Data.
6.6.2 Procedure
Activation Procedure
Run the MML command ADD ATMTRF (CME single configuration: NodeB Configuration
Express > IUB_RNC > ATM Transport > ATM Traffic Record; CME batch modification center:
not supported) to add an ATM traffic record of the UBR+ class. To add more ATM traffic
records, run this command repeatedly.
Verification Procedure
Run the MML command LST ATMTRF to query the ATM traffic configuration.
Expected result: The query result is consistent with the configuration information.
Deactivation Procedure
Run the MML command RMV ATMTRF (CME single configuration: NodeB Configuration
Express > IUB_RNC > ATM Transport > ATM Traffic Record; CME batch modification center:
not supported) to delete an ATM traffic record of the UBR+ class. To delete more ATM traffic
records, run this command repeatedly.
6.6.3 Example
//Adding UBR+ ATM QoS Class
ADD ATMTRF: TRFX=105, ST=UBR_PLUS, UT=CELL/S, MCR=100;
//Verifying UBR+ ATM QoS Class
LST ATMTRF: TRFX=105;
//Deactivating UBR+ ATM QoS Class
RMV ATMTRF: TRFX=105;
7 Parameters
ATM Default
Transmission Value:None
Introduction
Package
TS24
(Time_slot_24),
TS25
(Time_slot_25),
TS26
(Time_slot_26),
TS27
(Time_slot_27),
TS28
(Time_slot_28),
TS29
(Time_slot_29),
TS30
(Time_slot_30),
TS31
(Time_slot_31)
Unit:None
Actual Value
Range:TS1,
TS2, TS3, TS4,
TS5, TS6, TS7,
TS8, TS9, TS10,
TS11, TS12,
TS13, TS14,
TS15, TS16,
TS17, TS18,
TS19, TS20,
TS21, TS22,
TS23, TS24,
TS25, TS26,
TS27, TS28,
TS29, TS30,
TS31
Default
Value:None
TS24
(Time_slot_24),
TS25
(Time_slot_25),
TS26
(Time_slot_26),
TS27
(Time_slot_27),
TS28
(Time_slot_28),
TS29
(Time_slot_29),
TS30
(Time_slot_30),
TS31
(Time_slot_31)
Unit:None
Actual Value
Range:TS1,
TS2, TS3, TS4,
TS5, TS6, TS7,
TS8, TS9, TS10,
TS11, TS12,
TS13, TS14,
TS15, TS16,
TS17, TS18,
TS19, TS20,
TS21, TS22,
TS23, TS24,
TS25, TS26,
TS27, TS28,
TS29, TS30,
TS31
Default
Value:None
TS29(Time
Slot29), TS30
(Time Slot30),
TS31(Time
Slot31)
Unit:None
Actual Value
Range:TS1,
TS2, TS3, TS4,
TS5, TS6, TS7,
TS8, TS9, TS10,
TS11, TS12,
TS13, TS14,
TS15, TS16,
TS17, TS18,
TS19, TS20,
TS21, TS22,
TS23, TS24,
TS25, TS26,
TS27, TS28,
TS29, TS30,
TS31
Default
Value:None
TS24
(Time_slot_24),
TS25
(Time_slot_25),
TS26
(Time_slot_26),
TS27
(Time_slot_27),
TS28
(Time_slot_28),
TS29
(Time_slot_29),
TS30
(Time_slot_30),
TS31
(Time_slot_31)
Unit:None
Actual Value
Range:TS1,
TS2, TS3, TS4,
TS5, TS6, TS7,
TS8, TS9, TS10,
TS11, TS12,
TS13, TS14,
TS15, TS16,
TS17, TS18,
TS19, TS20,
TS21, TS22,
TS23, TS24,
TS25, TS26,
TS27, TS28,
TS29, TS30,
TS31
Default
Value:None
TS24
(Time_slot_24),
TS25
(Time_slot_25),
TS26
(Time_slot_26),
TS27
(Time_slot_27),
TS28
(Time_slot_28),
TS29
(Time_slot_29),
TS30
(Time_slot_30),
TS31
(Time_slot_31)
Unit:None
Actual Value
Range:TS1,
TS2, TS3, TS4,
TS5, TS6, TS7,
TS8, TS9, TS10,
TS11, TS12,
TS13, TS14,
TS15, TS16,
TS17, TS18,
TS19, TS20,
TS21, TS22,
TS23, TS24,
TS25, TS26,
TS27, TS28,
TS29, TS30,
TS31
Default
Value:None
8 Counters
9 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
10 Reference Documents