Documente Academic
Documente Profesional
Documente Cultură
GBSS16.0
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.........................................................................................................................................3
2.1 Introduction....................................................................................................................................................................3
2.2 NEs Supporting the Feature............................................................................................................................................4
3 Technical Description...................................................................................................................5
3.1 Key Technologies...........................................................................................................................................................5
4 Related Features.............................................................................................................................8
5 Engineering Guidelines...............................................................................................................9
5.1 Deploying Abis Bypass..................................................................................................................................................9
5.1.1 Deployment Requirements..........................................................................................................................................9
5.1.2 Activation..................................................................................................................................................................10
5.1.3 Activation Observation..............................................................................................................................................15
5.1.4 Deactivation...............................................................................................................................................................15
6 Parameters.....................................................................................................................................17
7 Counters........................................................................................................................................19
8 Glossary.........................................................................................................................................20
9 Reference Documents.................................................................................................................21
1.1 Scope
This document describes GBFD-116601 Abis Bypass, including its technical principles, related
features and engineering guidelines.
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
01 (2014-04-30)
This issue does not include any changes.
Draft A (2014-01-23)
Compared with Issue 01 (2013-05-06) of GBSS15.0, Draft A (2014-01-23) of GBSS16.0
includes the following changes.
2 Overview
2.1 Introduction
In the chain topology, if a BTS on the network is powered off or a transmission link is faulty,
services on all the BTSs following the faulty BTS or following the faulty transmission link are
interrupted. The GTMU stops working if the BTS is powered off. For example, in a chain
topology without the Abis Bypass as shown in Figure 2-1, if BTS 2 is powered off and its GTMU
stops working, the services on both BTS 2 and BTS 3 are interrupted.
With the Abis Bypass feature, a bypass transmission link is formed within the BTS that is
powered off to transfer data to other BTSs following the faulty BTS on the chain. Therefore, the
power failure of a BTS will not affect the normal services on the subsequent BTSs on the chain.
For example, in a chain topology with Abis Bypass as shown in Figure 2-2, the bypass board
within BTS 2 provides a bypass transmission link if the GTMU stops working upon power failure
of BTS 2. In this case, only the services on BTS 2 are interrupted without affecting the services
on BTS 3.
The BSS uses bypass loopback upon power failure to identify whether a failure is due to a faulty
transmission link or the BTS power failure.
Abis Bypass √ √ √ ×
NOTE
√ indicates that the NE supports this feature. × indicates that the NE does not support this feature.
3 Technical Description
For BTS3900 series, the Abis bypass function is implemented by setting DIP switches S4 and
S5 on the GTMU.
l When the Abis interface uses TDM transmission, DIP switches S4 and S5 must support
this function.
l When the Abis interface uses IP over E1 transmission, DIP switch S4 must support this
function.
Table 3-1 and Table 3-2 describe the bits of DIP switches S4 and S5, respectively.
S4 ON ON ON ON Abis Bypass
is supported.
S5 ON ON ON ON Abis Bypass
is not
supported.
If Abis Bypass is activated and the Abis interface uses IP over E1 transmission:
1. When an upper-level BTS experiences a power failure, call drop or mute voice problems
will be present on lower-level BTSs for about 5s. As shown in Figure 3-2, when BTS 1 is
powered off, the PPP or MLPPP link between BTS 1 and BTS 2 is interrupted. BTS 2 then
renegotiates with the BSC to reestablish a PPP or MLPPP link. After the renegotiation is
complete and an OML is reestablished, the services on the lower-level BTSs are restored.
2. When the upper-level BTS is powered on again, the services on lower-level BTSs are
interrupted. As shown in Figure 3-2, when BTS 1 is powered on again, the PPP or MLPPP
link between BTS 2 and the BSC is interrupted. BTS 2 then renegotiates with BTS 1 to
reestablish a PPP or MLPPP link. After the renegotiation is complete and an OML is
reestablished, the services on the lower-level BTSs are restored. According to laboratory
test results, the services on the adjacent lower-level BTS (BTS 2 in this example) are
interrupted for 4 to 15 minutes and the service interruption duration increases by 1 to 2
minutes for the BTS of a lower level (BTS 3 in this example).
To enable the Abis bypass function for cascaded BTSs, you need to set ABISBYPASSMODE
(BSC6900,BSC6910) to TRUE(Support) for each cascaded BTS.
l If the transmission link between BTS 1 and BTS 2 is faulty, BTS 2 and all the following
BTSs cannot be observed on the BSC.
l If BTS 2 is powered off, only BTS 2 is not observed on the BSC.
Figure 3-2 Schematic view of the BSS configured with bypass boards
The loopback function upon power failure helps to identify the BTS power failure from the
transmission link fault. The function, however, is not applicable to the last BTS on the chain.
For the last BTS on the chain, set the DIP switches on its bypass board so that the transmission
link through the last BTS is short-circuited when the BTS is powered off. Therefore, the loopback
test can be performed on the BSC side to locate the fault.
4 Related Features
5 Engineering Guidelines
Aspect Requirement
BSC None
MS None
MSC None
Aspect Requirement
5.1.2 Activation
Step 1 Run the ADD BTS command to add an upper-level BTS. In this step, set Abis ByPass Mode
to TRUE(Support).
Step 2 Run the ADD BTS command to add a lower-level BTS. In this step, set Abis ByPass Mode to
TRUE(Support).
Step 3 Run the ADD BTSCONNECT command to connect the lower-level BTS to the upper-level
BTS. Repeat this step for each cascaded BTS and set the following parameters:
l Set Dest Node Type to BTS.
l Set Dest Father BTS Port No. to the number of the port that connects the lower-level BTS
to the upper-level BTS.
NOTE
A BTS connects its upper-level BTS or the BSC through port 0 and connects its lower-level BTS through
port 2.
Step 4 (Optional) If the Abis interface uses IP over E1 transmission and the type of links carried on the
E1/T1 link is PPP, add PPP links by performing the following steps:
NOTE
Local IP address and Peer IP address must be set to 0.0.0.0 for PPP links over the port that connects the
BTS to the BSC or upper-level BTS.
1. Run the ADD PPPLNK command to add PPP links on the BSC side.
2. Run the ADD BTSPPPLNK command to add PPP links on the BTS side.
Step 5 (Optional) If the Abis interface uses IP over E1 transmission and the type of links carried on the
E1/T1 link is MLPPP link group, add MLPPP link groups by performing the following steps:
NOTE
Local IP address and Peer IP address must be set to 0.0.0.0 for MLPPP link groups over the port that
connects the BTS to the BSC or upper-level BTS.
1. Run the ADD MPGRP command to add MLPPP link groups on the BSC side.
2. Run the ADD MPLNK command to add MLPPP links on the BSC side.
3. Run the ADD BTSMPGRP command to add MLPPP link groups on the BTS side.
4. Run the ADD BTSMPLNK command to add MLPPP links on the BTS side.
----End
//BSC6900
//BSC6910
When configuring the Abis Bypass feature on the CME, you must perform a single configuration first, and
then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are advised to perform batch modifications before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 5-2. For the method of performing 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, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on the
CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
Slot No. SN
Port No. PN
Local IP LOCALIP
address
Peer IP PEERIP
address
----End
5.1.4 Deactivation
Using MML Commands
NOTE
Before performing the following step, run the DEA BTS command to deactivate the BTS if it has been
activated.
Step 1 On the BSC LMT, run the MOD BTS command with Abis ByPass Mode set to FALSE(Not
Support).
----End
When configuring the Abis Bypass feature on the CME, you must perform a single configuration first, and
then perform batch modifications if required.
You must perform a single configuration for a parameter before batch modifications of the parameter. You
are advised to perform batch modifications before logging out of the parameter setting interface.
Set parameters on the CME configuration interface according to the operation sequence
described in Table 5-3. For the method of performing 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, such as BSCs, BTSs, cells, and TRXs, in batches, click the icon on the
CME configuration interface to start the batch modification wizard. For the method of
performing batch modifications through the CME batch modification center, press F1 on the
wizard interface to obtain online help.
----End
6 Parameters
Actual Value
Range:FALSE,
TRUE
Default
Value:FALSE
(Not Support)
7 Counters
8 Glossary
9 Reference Documents