Escolar Documentos
Profissional Documentos
Cultura Documentos
V900R013C00
Technical Description
Issue Draft A
Date 2011-01-31
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 the warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
Purpose
This document describes the structure, working principles, signal flows, and transmission and
networking of the BSC6900. It helps the reader understand the implementation and working
principles of the BSC6900.
Product Version
The following table lists the product version related to the document.
BSC6900 V900R013C00
Intended Audience
This document is intended for:
l Network planners
l System engineers
l Field engineers
Organization
1 Changes in the BSC6900 GSM Technical Description
This document describes the changes in the BSC6900 GSM Technical Description.
2 Hardware Configuration Modes
The BSC6900 supports flexible hardware configuration modes. The hardware configuration
mode varies according to the scenario.
3 Overall Structure
This chapter describes the interactions between the modules in the BSC6900.
4 Working Principles
This chapter describes the working principles of the BSC6900 in the following ways: power
supply, environment monitoring, clock synchronization, and OM.
5 Signal Flow
The BSC6900 signal flow consists of the user-plane signal flow, control-plane signal flow, and
OM signal flow.
The transmission and networking between the BSC6900 and other NEs can be classified into
the following types: transmission and networking on the A/Gb interface, on the Abis interface,
on the Ater interface, and on the Pb interface.
7 Parts Reliability
The BSC6900 guarantees its operation reliability by means of board redundancy and port
redundancy.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Convention Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Contents
4 Working Principles....................................................................................................................4-1
4.1 Power Supply Principle...................................................................................................................................4-2
4.2 Environment Monitoring Principle.................................................................................................................4-3
4.3 Clock Synchronization Principle.....................................................................................................................4-6
4.3.1 Clock Sources.........................................................................................................................................4-6
4.3.2 Structure of the clock synchronization subsystem.................................................................................4-7
4.3.3 Clock Synchronization Process..............................................................................................................4-9
4.4 OM Principle.................................................................................................................................................4-11
4.4.1 Dual OM Plane.....................................................................................................................................4-12
4.4.2 OM Network........................................................................................................................................4-13
4.4.3 Active/Standby Workspaces................................................................................................................4-15
4.4.4 Data Configuration Management.........................................................................................................4-17
4.4.5 Security Management...........................................................................................................................4-20
4.4.6 Performance Management....................................................................................................................4-24
4.4.7 Alarm Management..............................................................................................................................4-25
4.4.8 Loading Management...........................................................................................................................4-27
4.4.9 Upgrade Management..........................................................................................................................4-31
4.4.10 BTS Loading Management................................................................................................................4-33
4.4.11 BTS Upgrade Management................................................................................................................4-34
5 Signal Flow..................................................................................................................................5-1
5.1 User-Plane Signal Flow...................................................................................................................................5-2
5.1.1 CBC Signal Flow...................................................................................................................................5-2
7 Parts Reliability..........................................................................................................................7-1
7.1 Concepts Related to Parts Reliability..............................................................................................................7-2
7.1.1 Backup....................................................................................................................................................7-2
7.1.2 Resource Pool.........................................................................................................................................7-3
7.1.3 Port Trunking.........................................................................................................................................7-3
7.1.4 Port Load Sharing...................................................................................................................................7-4
7.2 Board Redundancy..........................................................................................................................................7-4
7.2.1 Backup of EIUa Boards..........................................................................................................................7-5
7.2.2 Backup of OIUa Boards.........................................................................................................................7-5
7.2.3 Backup of PEUa Boards.........................................................................................................................7-6
7.2.4 Backup of POUc Boards........................................................................................................................7-7
7.2.5 Backup of SCUa/SCUb Boards..............................................................................................................7-8
7.2.6 Backup of TNUa Boards........................................................................................................................7-8
7.2.7 Backup of FG2a/FG2c Boards...............................................................................................................7-9
7.2.8 Backup of GCUa/GCGa Boards..........................................................................................................7-10
7.2.9 Backup of GOUa/GOUc Boards..........................................................................................................7-11
7.2.10 Backup of OMUa/OMUb/OMUc Boards..........................................................................................7-12
7.2.11 Backup of XPUa/XPUb Boards.........................................................................................................7-13
7.2.12 Resource Pool of DPUa/DPUc/DPUd/DPUf/DPUg Boards..............................................................7-13
7.3 Port Redundancy...........................................................................................................................................7-14
7.3.1 Optical Port Backup.............................................................................................................................7-14
7.3.2 FE/GE Port Backup..............................................................................................................................7-15
7.3.3 Port Load Sharing.................................................................................................................................7-16
Figures
Tables
This document describes the changes in the BSC6900 GSM Technical Description.
Draft A (2011-01-31)
This is the Draft A release of V900R013C00.
Compared with issue 03 (2010-09-20) of V900R012C01, this issue does not include any new
topics.
Compared with issue 03 (2010-09-20) of V900R012C01, this issue incorporates the following
changes.
Content Description
7.2.5 Backup of SCUa/SCUb Boards The description of the SCUb board is added.
Compared with issue 03 (2010-09-20) of V900R012C01, this issue does not exclude any topics.
The BSC6900 supports flexible hardware configuration modes. The hardware configuration
mode varies according to the scenario.
BM/TC
The main processing subrack (MPS) and extended processing subrack (EPS) are collectively
known as basic module (BM) subrack. The transcoder subrack (TCS) is known as TC subrack.
Main TCS
The TCS that forwards the OM signals to other TCSs is called the main TCS. All other TCSs
are called extension TCSs.
The main TCS is determined by both the cable connections and the data configuration. For details
of the cable connections, see switching subsystem.
In A over IP mode, layer 3 (network layer) of the protocol stack on the A interface adopts
the IP protocol. In this case, the BSC6900 is configured with the MPS and EPS but not
with the TCS. The TC function is performed by the Media Gateway (MGW).
Characteristics: In this mode, the BSC6900 has fewer cabinets and subracks. The
BSC6900 must be interconnected with a specific MGW.
One BSC6900 uses only one configuration mode.
3 Overall Structure
This chapter describes the interactions between the modules in the BSC6900.
Physical Structure
The BSC6900 cabinet consists of power distribution boxes and subracks, as listed in Table
3-1.
Independent fan subrack Each cabinet must be configured with one independent fan
subrack.
Power distribution box Each cabinet must be configured with one power distribution
box.
NOTE
If the customer purchase the Nastar product of Huawei, the customer needs to install the SAU board in the MPS
or EPS of the BSC6900 cabinet (the SAU board occupies two slots that work in active/standby mode). For details
on how to install the SAU board, how to install the software on the SAU board, and how to maintain the SAU
board, see the SAU User Guide of Nastar documents.
Software Structure
The software of the BSC6900 has a distributed architecture. It is classified into the host software
and OMU software.
l Host software
The host software is distributed on the service boards. It consists of the operating system,
middleware, and application software. See Figure 3-1.
– Operating system
The VxWorks real-time embedded operating system runs on each service board.
– Middleware
The Versatile Protocol Platform (VPP) and the Virtual Operating System (VOS)
function as the middleware. The middleware enables the upper-layer application
software to be independent from the lower-layer operating system so that software
functions can be transplanted between different platforms.
– Application software
Boards of different types can be installed with different application software. The
application software is classified into radio resource processing software, resource
control-plane processing software, base station management software, and
configuration maintenance management software.
l OMU software
The Operation and Maintenance Unit (OMU) software runs on the OMUa board, OMUb
board, OMUc board, and GBAM. The OMU is responsible for the operation and
maintenance of the BSC6900. The OMU software consists of the operating system and the
OMU application software. See Figure 3-2.
– Operating system
The Dopra Linux, Suse Linux, or Windows Server 2003 operating system is used.
– OMU application software
The OMU application software runs on the lower-level operating system and provides
various service processes, including the LMT process, fault diagnosis process, and
authentication process.
Logical Structure
Figure 3-3 and Figure 3-4 show the logical structure of the BSC6900.
The TCS that forwards the OM signals to other TCSs is called the main TCS.
The channel for the TCS and the MPS to exchange information varies according to the location
of the TCS: local or remote.
l In local TCS mode, the SCUa board in the main TCS is connected to the SCUa board in
the MPS through the crossover cable.
l In remote TCS mode, the TCS is located in the TCR, which is separate from the cabinet
that houses the MPS/EPS. The main TCS and the MPS are connected through the cable
between the Ater interface boards.
Subsystems
Logically, the BSC6900 consists of the following five subsystems:
3.1 Switching Subsystem
The switching subsystem performs switching of traffic data, signaling, and OM signals.
3.2 Service Processing Subsystem
The BSC6900 service processing subsystem performs the control functions defined in the 3GPP
protocols and processes services of the BSC6900.
3.3 Interface Processing Subsystem
The interface processing subsystem provides transmission ports and resources, processes
transport network messages, and enables interaction between the BSC6900 internal data and
external data.
3.4 Clock Synchronization Subsystem
The clock synchronization subsystem provides clock signals for the BSC6900 and provides
reference clock signals for base stations.
3.5 OM Subsystem
The OM subsystem enables the management and maintenance of the BSC6900 in the following
scenarios: routine maintenance, emergency maintenance, upgrade, and capacity expansion.
Functions
l Provides intra-subrack Medium Access Control (MAC) switching
l Provides intra-subrack Time Division Multiplexing (TDM) switching
l Provides inter-subrack MAC switching and TDM switching
l Distributes clock signals to the service processing boards
Hardware Involved
The switching subsystem consists of the SCUa/SCUb boards, TNUa boards, high-speed
backplane channels in each subrack, crossover cables between SCUa/SCUb boards, and inter-
TNUa cables.
l Star topology
One node functions as the center node and it is connected to each of the other nodes. The
communication between the other nodes is switched by the center node.
l Mesh topology
There is a connection between every two nodes. When any node is out of service, the
communication between other nodes is not affected.
l Chain topology
There is a connection between every two adjacent nodes. If an intermediate node is out of
service, the communications between other nodes are affected. The bandwidth utilization
in this topology is high.
In the switching subsystem of the BSC6900, the star or chain topology is established among the
MAC switching logical modules, and the mesh topology is established among the TDM
switching logical modules.
Inter-Subrack Connection
The MAC switching logical modules switch the ATM/IP traffic data, OM signals, and signaling.
Switching is performed by the SCUa boards and the Ethernet cables between the SCUa boards.
The inter-subrack connections related to MAC switching can be classified into the following
types:
Figure 3-8 Interconnections between subracks through the crossover cables between the SCUa
boards (MPS/EPS)
Figure 3-9 Interconnections between subracks through the crossover cables between the SCUa
boards (TCS)
Switching is performed by the SCUb boards and the Ethernet cables between the SCUb boards.
The inter-subrack connections related to MAC switching can be classified into the following
types:
l Interconnections between the MPS and the EPSs
The MPS functions as the main subrack. Star interconnections are established between the
MPS and the EPSs in the MPR through the Ethernet cables between the SCUb boards.
Chain interconnections are established between the EPSs in the MPR and other EPSs
through the Ethernet cables between the SCUb boards, as shown in Figure 3-10.
l Interconnections between the TCSs
Any TCS functions as the main subrack. Star interconnections are established between the
center TCS and the other TCSs in center TCR through the Ethernet cables between the
SCUb boards. Chain interconnections are established between the two TCSs in the center
TCR and other TCSs through the Ethernet cables between the SCUb boards, as shown in
Figure 3-11.
Figure 3-10 Interconnections between subracks through the crossover cables between the SCUb
boards (MPS/EPS)
Figure 3-11 Interconnections between subracks through the crossover cables between the SCUb
boards (TCS)
As shown in Figure 3-10 and Figure 3-11, subracks 0, 1, and 2 are in the same cabinet and star
interconnections are established between them through the Ethernet cables between the SCUb
boards. Chain interconnections are established between subracks 2 and 3 through the Ethernet
cables between the SCUb boards. Data is exchanged between subrack 0 and subrack 3 through
subrack 2.
The TDM switching logical modules switch the TDM-based traffic data. Switching is performed
by the TNUa boards and the inter-TNUa cables. The inter-subrack connections related to TDM
switching can be classified into the following types:
Figure 3-12 Interconnections between subracks through the inter-TNUa cables (MPS/EPS)
Figure 3-13 Interconnections between subracks through the inter-TNUa cables (TCS)
NOTE
For details about the definitions of CP and UP, see 5 Signal Flow.
Functions
The service processing subsystem performs the following functions:
l User data transfer
l System admission control
l Radio channel ciphering and deciphering
l Data integrity protection
l Mobility management
l Radio resource management and control
l Cell broadcast service control
l System information and user message tracing
l Data volume reporting
l Radio access management
l CS service processing
l PS service processing
Service processing subsystems communicate with each other through the switching subsystem
to form a resource pool and perform tasks cooperatively. They can be increased as required,
according to the linear superposition principle, thereby improving the service processing
capability of the BSC6900.
Hardware Involved
The service processing subsystem consists of the XPUa, XPUb, DPUc, DPUd, DPUf and DPUg
boards. The XPUa and XPUb boards process signaling. The DPUc, DPUd, DPUf and DPUg
boards process services.
Functions
l The interface processing subsystem provides the following types of IP and TDM interfaces.
– E1/T1 electrical ports
Hardware Involved
The interface processing subsystem consists of the Abis, A, Ater, Gb, and Pb interface boards.
Figure 3-17 Position of the clock synchronization subsystem in the BSC6900 system
Functions
The clock synchronization subsystem provides the following clock sources for the BSC6900
and ensures the reliability of the clock signals:
Hardware Involved
The clock synchronization subsystem consists of the GCUa/GCGa board.
3.5 OM Subsystem
The OM subsystem enables the management and maintenance of the BSC6900 in the following
scenarios: routine maintenance, emergency maintenance, upgrade, and capacity expansion.
Functions
The OM subsystem provides:
l 4.4.4 Data Configuration Management
l 4.4.5 Security Management
Hardware Involved
The OM subsystem consists of the OMUa board, OMUb board, OMUc board, or GBAM.
4 Working Principles
This chapter describes the working principles of the BSC6900 in the following ways: power
supply, environment monitoring, clock synchronization, and OM.
NOTE
The DC PDF and the DC power distribution panel are not regarded as the components of the BSC6900.
The physical entity of the OMU can be the OMUa board, OMUb board, or GBAM. The following takes the
OMUa board as an example to describe environment monitoring.
Power Monitoring
Power monitoring involves monitoring the power subsystem in real time, reporting the operating
status of the power supply, and generating alarms when faults occur.
Figure 4-2 shows the working principle of power monitoring.
distribution box. Then, the fan subrack forwards the power monitoring signals to the active
SCUa board in the power monitoring subrack.
3. The SCUa board processes the monitoring signals. If faults occur, the SCUa board generates
alarms and reports the alarms to the OMUa board. The OMUa board then forwards the
alarms to the LMT or M2000.
Fan Monitoring
Fan monitoring involves monitoring the operating status of the fans in real time and adjusting
the speed of the fans based on the temperature in the subrack.
Each subrack is configured with a built-in fan box. The temperature sensor next to the air outlet
can detect the temperature in the subrack.
Besides the built-in fan box in the subrack, there is an independent fan subrack at the bottom of
the cabinet. This improves the heat dissipation capability of the cabinet.
Figure 4-3 shows the working principle of fan monitoring.
Environment Monitoring
Environment monitoring involves monitoring the temperature, humidity, operating voltage, door
status, water damage, smoke, and infrared. The environment monitoring function is performed
by the Environment Monitor Units (EMUs).
If the power distribution box can transfer signals, the environment monitoring process is as
follows:
1. The sensors monitor the environment in real time and send the monitoring signals to the
EMU.
2. The EMU sends the monitoring signals to the power distribution box through the serial
cable.
3. The signal transfer board in the power distribution box transmits the monitoring signals to
the active SCUa board in the power monitoring subrack through the monitoring signal cable
of the power distribution box.
4. The active SCUa board in the power monitoring subrack transmits the monitoring signals
to the SCUa board in the MPS through the Ethernet cables between the SCUa boards.
5. The SCUa board in the MPS processes the monitoring signals. If faults occur, the SCUa
board generates alarms and reports the alarms to the OMUa board. The OMUa board then
forwards the alarms to the LMT or M2000.
If the power distribution box cannot transfer signals, the environment monitoring process is as
follows:
1. The sensors monitor the environment in real time and send the monitoring signals to the
EMU.
2. The EMU sends the monitoring signals to the active SCUa board in the lowest subrack
through the serial cable.
3. The active SCUa board in the lowest subrack transmits the monitoring signals to the SCUa
board in the MPS through the Ethernet cables between the SCUa boards.
4. The SCUa board in the MPS processes the monitoring signals. If faults occur, the SCUa
board generates alarms and reports the alarms to the OMUa board. The OMUa board then
forwards the alarms to the LMT or M2000.
External Clocks
The external clocks of the BSC6900 are of two types:
l BITS Clock
– The BITS clock signals are of three types: 2 MHz, 2 Mbit/s, and 1.5 Mbit/s. The 2 MHz
and 2 Mbit/s clock signals are E1 clock signals, and the 1.5 Mbit/s clock signals are T1
clock signals.
– The BITS clock has two input modes: BITS0 and BITS1. BITS0 and BITS1 correspond
to the CLKIN0 and CLKIN1 ports on the GCUa/GCGa board respectively. The
BSC6900 obtains the BITS clock signals through the CLKIN0 or CLKIN1 port.
l External 8 kHz Clock
Through the COM1 port on the GCUa/GCGa board, the BSC6900 obtains 8 kHz standard
clock signals from an external device.
LINE Clock
The LINE clock is an 8 kHz clock that is transmitted from an interface board in the MPS to the
GCUa/GCGa board through the backplane channel. The LINE clock has two input modes:
LINE0 and LINE1.
NOTE
LINE0 and LINE1 correspond to backplane channel 1 and backplane channel 2 respectively.
GPS Clock
The GPS clock provides 1 Pulse Per Second (PPS) clock signals. The BSC6900 obtains the GPS
clock signals from the GPS system. The GCGa board is configured with a GPS card, and the
BSC6900 receives the GPS signals at the ANT port on the GCGa board.
NOTE
The GCUa board is not configured with a GPS card. Therefore, when the BSC6900 is configured with the GCUa
board instead of the GCGa board, the GPS clock is unavailable to the BSC6900.
Local Oscillator
If the BSC6900 fails to obtain any external clock, the BSC6900 can obtain its working clock
signals from the local oscillator.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
l The clock board of the BSC6900 can be the GCUa or GCGa board. The BSC6900 cannot
be configured with both the GCUa and GCGa boards simultaneously. Depending on the
clock type, it can have either the GCUa board or the GCGa board.
l If the MPS extracts the clock signals, the clock signals enter the MPS in any of the following
ways:
– The clock signals enter the port on the panel of the GCUa/GCGa board.
– The clock signals enter the port on the panel of an interface board that can extract line
clock signals, include EIUa/OIUa/PEUa board. The clock signals are then switched to
the GCUa/GCGa board through the backplane.
– The GCUa/GCGa board generates oscillator clock signals.
l If the EPS extracts the clock signals, the interface board that extracts clock signals must be
the EIUa/OIUa/PEUa board.
l If the BSC6900 is configured with the Gb interface board, the Gb interface board extracts
clock signals either from the backplane or from the CN. The Gb interface board, however,
cannot extract clock signals from them simultaneously. If the PS services and CS services
use different clock sources and the clock signals are extracted from the CN, the Gb interface
board serves only the Gb interface.
Figure 4-6 shows the connections of the clock cables between the clock boards in the MPS and
the SCUa boards in the EPS when the BSC6900 is configured with active and standby clock
boards and SCUa boards.
The active and standby clock boards in the MPS are connected to the active and standby SCUa
boards in the EPS through the Y-shaped clock signal cables. This connection mode ensures that
the system clock of the BSC6900 works properly in the case of a single-point failure of the clock
board, Y-shaped clock signal cable, or SCUa board. In addition, the Y-shaped clock signal cable
ensures the proper working of the SCUa boards during the switchover of the active and standby
clock boards.
NOTE
In the MPS, the clock board sends clock signals to the SCUa board in the same subrack through the backplane
channel. Therefore, a Y-shaped clock signal cable is not required.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
l Figure 4-7 shows the process of clock synchronization in the MPS/EPS when the clock
board extracts clock signals from an external device or from the GPS.
l Figure 4-8 shows the process of clock synchronization in the MPS/EPS when the clock
board extracts LINE clock signals from the A interface.
As shown in Figure 4-7 and Figure 4-8, the process of clock synchronization in the MPS/EPS
is as follows:
1. If an external clock is used, external clock signals travel to the clock board through the port
on the panel of the clock board. If the GPS clock is used, clock signals travel to the clock
board through the GPS antenna port. If the LINE clock is used, clock signals travel to the
clock board through the backplane.
2. The clock source is phase-locked in the clock board to generate clock signals. The clock
signals, then, are sent to the SCUa board in the MPS through the backplane and to the SCUa
board in each EPS through the clock signal output ports.
3. The SCUa board in the MPS/EPS transmits the clock signals to the other boards in the same
subrack through the backplane.
NOTE
The Abis interface boards transmit the clock signals to the base stations.
1. The TCS extracts LINE clock signals from the A interface. Then, the LINE clock signals
are processed by the A interface board to obtain the required clock signals.
2. In the TCS, the A interface board transmits the clock signals to the SCUa board through
the backplane. Then, the SCUa board transmits the clock signals to the other boards in the
TCS.
NOTE
l In A over IP over Ethernet mode, the BSC6900 can extract only external clock signals.
l In A over IP over E1/T1 mode, the BSC6900 can extract only LINE clock signals.
4.4 OM Principle
OM is performed in the following scenarios: routine maintenance, emergency maintenance,
troubleshooting, device upgrade, and capacity expansion. In addition, OM can be performed to
rapidly adjust device status.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
If the internal network and external network are on different network segments, ensure that
the two networks are isolated.
The dual OM plane design is implemented by the hardware that works in active/standby mode.
When an active component is faulty but the standby component works properly, a switchover
is automatically performed between the active and standby components, to ensure that the OM
channel works properly.
The active/standby OMUa boards use the same external virtual IP address to communicate with
the LMT or M2000 and use the same internal virtual IP address to communicate with the SCUa
board.
l When the active OMUa board is faulty, an active/standby switchover is performed
automatically, and the standby OMUa board takes over the OM task. In this case, the
internal and external virtual IP addresses remain unchanged. Thus, the proper
communication between the internal and external networks of the BSC6900 is ensured.
l When a single-point failure occurs on the switching network, the active/standby SCUa
boards in each subrack are switched over automatically to ensure that the OM channel
works properly.
4.4.2 OM Network
The OM network of the BSC6900 consists of the M2000, LMT, OMU, SCUa/SCUb boards,
and OM modules in other boards.
NOTE
Either the OMUa, OMUb, or OMUc board, or GBAM can serve as an OMU. This chapter uses the OMUa board
as an example for your reference.
Either the SCUa or SCUb board can serve as an SCU. This chapter takes the SCUa board as an example for
your reference.
NOTE
M2000
The M2000 is a centralized network management system. The M2000 is connected to the
BSC6900 through Ethernet cables. One M2000 can remotely manage multiple BSC6900s.
LMT
The LMT is connected to the OMUa board of the BSC6900 and works on the Windows XP
Professional or Windows Vista operating system. One or more LMTs can be connected to the
OMUa board directly or through networks. The maintenance of the BSC6900 can be performed
locally or remotely through the LMT. The LMT is connected to an alarm box through a serial
cable.
OMUa Board
The OMUa board is the back administration module of the BSC6900. It is connected to an
external device through the Ethernet cable. The BSC6900 can be configured with one OMUa
board in independent mode or with two OMUa boards in active/standby mode.
The OMUa board functions as a bridge between the BSC6900 and the LMT/M2000. The OM
network of the BSC6900 is classified into the following networks:
l Internal network: implements the communication between the OMUa board and the host
boards of the BSC6900.
l External network: implements the communication between the OMUa board and external
devices, such as the LMT or M2000.
SCUa Board
The SCUa board is the switching and control board of the BSC6900. It is responsible for the
OM of the subrack where it is located. If a subrack is configured with two SCUa boards, then
the two boards work in active/standby mode.
The SCUa board performs OM on other boards in the same subrack through the backplane
channels. The SCUa boards in different subracks are connected through crossover cables.
The relation between the active/standby workspaces is relative. The active/standby relation
depends on the storage location of the running version. The workspace that stores the running
OMU version files is the active workspace, and the other is the standby workspace.
5. A switchover is performed between the active and standby workspaces of the standby OMU
to ensure that the versions of the workspaces are consistent with those of the active OMU.
6. The OMU version upgrade is complete.
After the OMU version upgrade, the standby workspaces of the active and standby OMUs store
the files of the old version. In this case, version rollback can be performed as required.
The working principles of the OMU active/standby workspaces in the case of version rollback
are as follows:
1. A switchover is performed between the active and standby workspaces of the active OMU.
The running version of the active OMU is rolled back to the pre-upgrade version.
2. The active OMU runs the pre-upgrade version.
3. A switchover is performed between the active and standby workspaces of the standby OMU
to ensure that the versions of the workspaces are consistent with those of the active OMU.
4. The OMU version rollback is complete.
Relation Between the Active/Standby Workspaces of Host Boards and the Active/
Standby Workspaces of the OMU
On the active workspaces of the host boards, files can be loaded only from the active workspace
of the OMU. On the standby workspaces of the host boards, files can be loaded only from the
standby workspace of the OMU.
Relation Between the Active/Standby Workspaces of Host Boards and the Active/
Standby Workspaces of the OMU
On the active workspaces of the host boards, files can be loaded only from the active workspace
of the OMU. On the standby workspaces of the host boards, files can be loaded only from the
standby workspace of the OMU.
WARNING
Data configuration rollback cannot be performed when the CM control enable switch is set to
ON, when the fast configuration mode is selected, or when batch configuration is performed.
l The data configuration rights management enables only one user to perform data
configuration on the BSC6900 through the LMT or M2000 at a time.
l The user must have data configuration rights.
With the data configuration rights management, users cannot configure data for the BSC6900
at the same time.
Figure 4-14 Check of the data consistency between the OMU and the host boards
The procedure for checking the data consistency between the OMU and the host boards is as
follows:
1. On the LMT, a data consistency check command is sent to the OMU automatically on a
regular basis or manually.
2. The OMU analyzes the parameters of the command and checks whether the data in the
board databases is the same as that in the OMU database.
3. The OMU generates a result file and sends it to the LMT.
Rights Management
The rights management is performed to identify a user and define the rights of the user.
The BSC6900 supports multi-user operations. It performs hierarchical rights management for
users to ensure security. The BSC6900 authorizes users at multiple levels and assigns certain
rights to the users at each level. To log in to the LMT of the BSC6900, a user must enter the
registered user name and password, through which the BSC6900 identifies the user.
l User types
– Local users: refer to the accounts (including the default local account admin) managed
by only the BSC6900 LMT. This type of LMT users can log in to the LMT during the
BSC6900 installation and during the disconnection from the M2000.
– Domain users: refer to the accounts that are created, changed, authenticated, and
authorized on the M2000. Domain users can manage the BSC6900 after logging in to
the LMT or after logging in to the M2000 server through the M2000 client.
l User rights
Guest Guest can only G_0 The objects in this command group are used to
browse data. query system information, such as users,
command groups, logs, NTP, EMS, and time
zones.
User In addition to G_7 The objects in this command group are used to
the rights perform performance management, for example,
granted to the to activate a performance task file or to upload a
Guest, User performance result file.
can perform
system OM.
Operator In addition to G_3 The objects in this command group are used to
the rights configure data, for example, the data for a new
granted to the cell.
User, the
Operator can G_5 The objects in this command group are used to
perform data perform alarm management, for example, to
configuration clear an alarm or to set the alarm level.
on the
equipment.
Adminis Administrator G_1 The objects in this command group are used to
trator has the highest manage system information, for example, to
operation manage a user, to set the time zone, to set the
rights. It can daylight saving time, or to perform batch
manage all the configuration.
other users.
Log Management
Log management records the operation history and saves the related logs about the BSC6900.
Thus, it helps analyze and identify faults.
Table 4-2 lists the types of logs that are recorded when the BSC6900 is running.
Type Description
Running log Records the information on the operating status of the system. The
information is used to analyze and locate faults.
Security log Records the information on the operations that may affect the system
security, for example, the information on the change of user
password.
The OMU saves the log information in the buffer. When the log information reaches the specified limit
or the current time reaches the log record period, the OMU records the log file.
Inventory Management
The inventory management refers to the efficient and centralized management of the primary
configuration information about the equipment in the network.
By exporting and uploading the inventory information files on the M2000, you can learn the
physical and logical configurations of NEs. The inventory management system is deployed on
the M2000. It obtains the required inventory information from NEs through the related interfaces.
NEs report inventory information to the M2000 in the form of files, which contain the
information on the following aspects:
l Equipment
l Connection
l Modules
l Configurations
l Peer equipment
l Host version
l Cabinets
l Subracks
l Boards and the Flash electronic labels of the boards
l Slots
l Ports
l Antennas
Figure 4-15 shows the process of collecting performance measurement data periodically by the
BSC6900.
1. The user registers a performance measurement task and specifies the object, time, and item
attributes of the task on the M2000 client.
2. Based on the performance measurement task, the M2000 server modifies the measurement
task file, sends it to the OMU, and issues a command to activate the modified measurement
task file.
3. Based on the modified measurement task file, the OMU requests host boards to collect data
according to the new requirements. The OMU receives the measurement results from the
host boards and saves them as files.
4. The OMU notifies the M2000 server of the measurement results and uploads the files into
the M2000 server. The M2000 server processes the files and saves them into the database.
5. Based on the performance measurement task registered by the M2000 client, the M2000
server obtains the relevant results from the database, performs certain calculation on them,
and then sends the result to the M2000 client.
Measurement Types
Performance measurement objects are of three types: default measurement objects, optional
measurement objects, and real-time measurement objects.
Each board detects alarms and reports them to the OMU automatically. The OMU then classifies
these alarms into different severity levels and sends them to the LMT or the M2000 server. You
can view and manage alarm information on the LMT or M2000 client.
The alarm management module of the OMU provides the following functions:
l Alarm storage
The alarm management module stores the alarms in the database of the OMU.
l Alarm processing
The alarm management module processes the operation commands from the LMT or
M2000 client and then returns the operation results to the LMT or M2000 client. These
commands include querying active alarms, querying alarm logs, and modifying alarm
configuration items.
l Alarm triggering
If the generation of an alarm triggers another alarm, the alarm management module reports
the two alarms to the LMT or M2000 client.
l Alarm recovery
After an alarm is handled, the system automatically clears the alarm. At the same time, the
alarm management module clears the alarm information from the LMT or M2000.
Alarm Box
The alarm box generates audible and visual alarms. The red, orange, yellow, and green alarm
indicators on the alarm box indicate the critical, major, minor, and warning alarms respectively.
Different alarm severity levels have different alarm sounds. Figure 4-17 shows the working
principle of the alarm box.
The alarm box is connected to the LMT through a serial cable. When an alarm is reported, the
LMT forwards it to the alarm box. The alarm box then generates an audible and visual alarm.
You can stop alarm sounds, turn off alarm indicators, and reset the alarm box through the LMT.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
Principle of Loading
The OMUa board and the active SCUa board in each subrack play important roles during the
BSC6900 loading process.
l The OMUa board functions as the first-level center of the entire BSC6900 loading
management process. The loading and power-on of the OMUa board are independent of
other boards. The OMUa board processes the loading control requests of other boards.
l The active SCUa board functions as the second-level center of the loading management
process. If the OMUa board is not in position, the active SCUa board in a subrack processes
the loading control requests from the other boards in the same subrack. If the SCUa boards
in an extension subrack are not started, the active SCUa board in the main subrack processes
the loading control requests from the boards in the extension subrack.
l The SCUa board in the main TCS functions as the file transfer server during the TCS loading
process. If a board in a TCS needs to load files from the OMUa board, the SCUa board in
the main TCS downloads the files from the OMUa board and then processes the file
download request from the board.
Loading Process
The BSC6900 loading process varies according to the configuration mode of subracks and the
location of TCS.
l Scenario 1: BM/TC separated and local TCS
Figure 4-18 shows the loading process.
In this scenario, the Ater interface functions as the loading path between the BM and the
TC. Figure 4-19 shows the loading process.
Upgrade Scenarios
The BSC6900 needs to be upgraded to rectify the existing defects and to support new functions,
higher specifications, and later protocol standards. The upgraded version can provide better QoS.
Upgrade Mode
You can use the dedicated upgrade tool to upgrade the BSC6900 through the OM network of
the BSC6900. See Figure 4-21.
NOTE
Upgrade Process
The BSC6900 is upgraded remotely by using the dedicated upgrade tool, which consists of the
upgrade client and the upgrade server. Figure 4-22 shows the upgrade process.
NOTE
1. The user sends the upgrade version files and the upgrade server program to the specified
directories of the active OMU through the network.
2. The user connects the client PC to the active OMU and then starts the upgrade client on
the client PC and the upgrade server on the active OMU to set up the connection between
the upgrade client and the upgrade server.
3. The upgrade server synchronizes the version files of the standby OMU with those of the
active OMU.
4. The user starts the upgrade server on the standby OMU and sets up the connection between
the upgrade server on the standby OMU and the upgrade server on the active OMU.
5. The upgrade server on the active OMU performs health check on the data and files in the
active workspace of the active OMU and then backs them up before the upgrade.
6. The upgrade server of the active OMU upgrades the software in the standby workspace of
the active OMU. At the same time, the upgrade server of the standby OMU upgrades the
software in the standby workspace of the standby OMU.
7. The upgrade server of the active OMU upgrades the data in the standby workspace of the
active OMU.
8. The upgrade server of the active OMU issues a command to load the host program, DSP,
BOOTROM, and data files in the standby workspace of the active OMU onto the standby
workspaces of the host boards so that the standby workspaces of the boards are
synchronized with the standby workspace of the active OMU.
9. The upgrade server of the active OMU issues a command to switch over the active and
standby workspaces of the active OMU to upgrade the active OMU.
10. The upgrade server of the active OMU issues a command to reset all the standby boards of
the BSC6900.
11. After the reset, all the standby boards of the BSC6900 automatically load the program files
and data files from the standby workspaces of their flash memories to upgrade the boards.
12. After the upgrade server of the active OMU detects that all the standby boards are started,
it issues a command to reset all the active boards of the BSC6900.
13. When the active boards are being reset, the original standby boards become active.
Similarly, after the reset, all the original active boards automatically load the program files
and data files from the standby workspaces of their flash memories to upgrade themselves.
14. After the service verification is successful, the upgrade server of the active OMU issues a
command to switch over the active and standby workspaces of the standby OMU so as to
upgrade the standby OMU. After the switchover, the standby OMU automatically
synchronizes with the active OMU.
The upgrade is complete.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
l For the BTS connected to an IP Abis interface board, the loading management process is
as follows:
1. After the BTS is started, it attempts to establish the OML and then broadcasts a DHCP
request over the OML.
2. After receiving the DHCP request, the SCUa board in the subrack, in which the Abis
interface board connected to the BTS is located, processes the request and sends a
DHCP response to the BTS. Through this response, the SCUa board notifies the BTS
of the IP address of the BTS board and the IP address of the OMUa board.
3. Based on the version number of the BTS, the BSC6900 reads the version configuration
file from the corresponding BTS version directory on the hard disk of the OMUa board,
obtains the information about the software version numbers of all the BTS boards,
and then sends the information to the BTS.
4. After obtaining the software version numbers, the BTS automatically checks whether
the number of the version running on each board is the same as the obtained number.
If there is any inconsistency, the BTS requests the BSC6900 to load and activate the
version software.
5. After running the version software, the BTS requests the BSC6900 for configuration
data.
6. The OMUa board obtains the BTS configuration data from its database and sends it
to the BTS through messages. Then, the BTS is initialized.
l For the BTS connected to a non-IP Abis interface board, the loading management process
is as follows:
1. After the BTS is started, it attempts to establish the OML.
2. The BSC6900 sends a version check request to the BTS. Then, the BTS reports its
version information to the BSC6900.
3. The BSC6900 checks the BTS version number. If the BTS version does not match the
BSC6900 version, the BSC6900 sends a version loading request to the BTS,
instructing the BTS boards to obtain and load program files from the OMUa board.
4. After receiving a loading completion indication message from the BTS, the
BSC6900 sends a version activation request to the BTS, instructing the BTS boards
to run the new version.
5. After running the version software, the BTS requests the BSC6900 for configuration
data.
6. The OMUa board obtains the BTS configuration data from its database and sends it
to the BTS through messages. Then, the BTS is initialized.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
5 Signal Flow
The BSC6900 signal flow consists of the user-plane signal flow, control-plane signal flow, and
OM signal flow.
Definitions
l User plane
User plane refers to the set of logical functions of the BSC6900 that process the service
data, including the speech data and packet data.
l Control plane
Control plane refers to the set of logical functions of the BSC6900 that process the control
signaling, including the call control signaling and the connection control signaling.
5.1 User-Plane Signal Flow
The user plane of the BSC6900 processes the user-plane messages on each interface.
5.2 Control-Plane Signal Flow
The control plane of the BSC6900 processes the control-plane messages on each interface.
5.3 OM Signal Flow
OM signal flow refers to the messages transmitted between the BSC6900 and the LMT/M2000.
The LMT or M2000 maintains and monitors the BSC6900 in real time through the OM signal
flow.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
Figure 5-1 shows the signal flow from the CBC-BSC interface to the Abis interface.
NOTE
l The INT in the figure stands for the interface board. You can use different interface boards as required.
l The boards shown in Figure 5-1 are only examples.
1. The CBC sends the broadcast data to the XPUa board of the BSC6900 over the CBC-BSC
interface. The XPUa board processes the data according to the related protocols and then
sends it to the Abis interface board.
NOTE
If the XPUa board in a subrack cannot process the data, the data is switched by the MPS to the XPUa
board in another subrack.
2. The Abis interface board processes the data and then sends it to the BTS.
3. The BTS broadcasts the data to the MSs in the cells served by the base station.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
NOTE
l The Abis, Ater, and A interface boards can be the EIUa/OIUa/POUc board. The boards shown in Figure
5-2, Figure 5-3, and Figure 5-4 are only examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
3. The CS signals are multiplexed in the Ater interface board. Each full-rate CS signal uses a
16 kbit/s sub-timeslot, and each half-rate CS signal uses an 8 kbit/s sub-timeslot. The CS
signals are then transmitted to the Ater interface board in the TCS over the Ater interface.
4. The CS signals are demultiplexed in the Ater interface board of the TCS. Each CS signal
uses a 64 kbit/s timeslot and is transmitted to the DPUc board through the TNUa board.
5. The DPUc board performs speech codec and rate adaptation on the CS signals, which are
converted into 64 kbit/s PCM signals. The 64 kbit/s PCM signals are transmitted to the A
interface board through the TNUa board and then to the MSC over the A interface.
The downlink flow is the reverse of the uplink flow.
Figure 5-3 shows the CS signal flow in Abis over TDM, Ater over IP, A over TDM, and BM/
TC separated mode.
NOTE
l The Abis interface board can be the PEUa/FG2a/GOUa/POUc/FG2c/GOUc board, and the Ater and A
interface boards can be the EIUa/OIUa/POUc board. The boards shown in Figure 5-5, Figure 5-6, and
Figure 5-7 are only examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
1. The uplink CS signals are sent from the BTS to the Abis interface board in the MPS/EPS.
2. The CS signals are transmitted from the Abis interface board to the DPUc board through
the SCUa board.
3. The DPUc board reorders PTRAU frames, eliminates jitter, and converts PTRAU frames
into TRAU frames. Then, the TRAU frames are transmitted to the Ater interface board
through the TNUa board.
4. The CS signals are multiplexed in the Ater interface board in the MPS/EPS, and then are
transmitted to the Ater interface board in the TCS.
5. The CS signals are demultiplexed in the Ater interface board of the TCS. Each CS signal
uses a 64 kbit/s timeslot and is transmitted to the DPUc board through the TNUa board.
6. The DPUc board performs speech codec and rate adaptation on the CS signals, which are
converted into 64 kbit/s PCM signals. The 64 kbit/s PCM signals are transmitted to the A
interface board through the TNUa board and then to the MSC over the A interface.
The downlink flow is the reverse of the uplink flow.
Figure 5-6 shows the CS signal flow in Abis over IP, Ater over IP, A over TDM, and BM/TC
separated mode.
In the case of BM/TC combined mode, the Ater interface does not exist. Figure 5-7 shows the
CS signal flow in Abis over IP and A over TDM mode.
NOTE
l The Abis interface board can be the EIUa/OIUa/POUc board, and the A interface board can be the FG2a/
GOUa/FG2c/GOUc/POUc board. The boards shown in Figure 5-8 are only examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
1. The uplink CS signals are sent from the BTS to the Abis interface board in the MPS/EPS.
2. The CS signals are demultiplexed in the Abis interface board. Each CS signal uses a 64
kbit/s timeslot and is transmitted to the DPUc board through the TNUa board.
3. The DPUc board converts PTRAU frames into RTP frames, reorders RTP frames, and
eliminates jitter.
4. The SCUa board transmits the CS signals to the A interface board, which then transmits
the signals to the MGW over the A interface.
The downlink flow is the reverse of the uplink flow.
NOTE
l The Abis interface board can be the PEUa/FG2a/GOUa/POUc/FG2c/GOUc board, and the A interface board
can be the FG2a/GOUa/PEUa/FG2c/GOUc/POUc board. The boards shown in Figure 5-9 are only
examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
NOTE
l The Abis interface board can be the EIUa/OIUa/POUc board, and the Gb interface board can be the PEUa/
FG2a/POUc/FG2c/GOUc board. The boards shown in Figure 5-10 are only examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
Abis over IP
Figure 5-11 shows the PS signal flow in Abis over IP transmission mode.
NOTE
l The Abis interface board can be the PEUa/FG2a/GOUa/POUc/FG2c/GOUc board, and the Gb interface
board can be the PEUa/FG2a/POUc/FG2c/GOUc board. The boards shown in Figure 5-11 are only
examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
A over TDM
In A over TDM mode, the signaling flow on the A interface varies according to the configuration
mode of BSC6900 subracks.
l Figure 5-12 shows the signaling flow on the A interface in BM/TC separated mode.
l Figure 5-13 shows the signaling flow on the A interface in BM/TC combined mode.
NOTE
l The A interface board can be the EIUa/OIUa/POUc board, and the XPUa/XPUb board processes signaling.
The boards shown in Figure 5-12 and Figure 5-13 are only examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
Figure 5-12 Signaling flow on the A interface in A over TDM mode (BM/TC separated)
As shown in Figure 5-12, the uplink signaling flow on the A interface is as follows:
1. In the MPS/EPS, the XPUa board processes the signaling according to the MTP3, SCCP,
and BSSAP protocols. Then, the signaling is transmitted to the Ater interface board through
the SCUa board.
2. The Ater interface board processes the signaling according to the MTP2 protocol. Then,
the signaling is transmitted to the Ater interface board in the TCS.
3. In the TCS, the Ater interface board transparently transmits the signaling to the TNUa board
and then to the A interface board. Then, the signaling is transmitted to the MSC over the
A interface.
The downlink flow is the reverse of the uplink flow.
Figure 5-13 Signaling flow on the A interface in A over TDM mode (BM/TC combined)
As shown in Figure 5-13, the uplink signaling flow on the A interface is as follows:
1. In the MPS/EPS, the XPUa board processes the signaling according to the MTP3, SCCP,
and BSSAP protocols. Then, the signaling is transmitted to the A interface board through
the SCUa board.
2. The A interface board processes the signaling according to the MTP2 protocol. Then, the
signaling is transmitted to the MSC over the A interface.
The downlink flow is the reverse of the uplink flow.
A over IP
Figure 5-14 shows the signaling flow on the A interface in A over IP mode.
NOTE
l The A interface board can be the FG2a/GOUa/FG2c/GOUc/POUc board, and the XPUa/XPUb board
processes signaling. The boards shown in Figure 5-14 are only examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
As shown in Figure 5-14, the uplink signaling flow on the A interface is as follows:
1. In the MPS/EPS, the XPUa board processes the signaling according to the BSSAP, SCCP,
SCTP, and M3UA protocols. Then, the signaling is transmitted to the A interface board
through the SCUa board.
2. The A interface board processes the signaling according to the IP protocol. Then, the
signaling is transmitted to the MSC server through the MGW.
The downlink flow is the reverse of the uplink flow.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
NOTE
l The Abis interface board can be the EIUa/OIUa/POUc board, and the XPUa/XPUb board performs signaling
processing. The boards shown in Figure 5-15 are only examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
Figure 5-15 Signaling flow on the Abis interface in Abis over TDM mode
As shown in Figure 5-15, the uplink signaling flow on the Abis interface is as follows:
1. The signaling from the BTS is transmitted to the Abis interface board in the MPS/EPS over
the Abis interface and is then transmitted to the SCUa board.
2. The SCUa board transmits the signaling to the signaling processing board.
The downlink flow is the reverse of the uplink flow.
Abis over IP
Figure 5-16 shows the signaling flow on the Abis interface in Abis over IP mode.
NOTE
l The Abis interface board can be the FG2a/GOUa/PEUa/FG2c/GOUc/POUc board, and the XPUa/XPUb
board performs signaling processing. The boards shown in Figure 5-16 are only examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
Figure 5-16 Signaling flow on the Abis interface in Abis over IP mode
As shown in Figure 5-16, the uplink signaling flow on the Abis interface is as follows:
1. The signaling from the BTS is transmitted to the Abis interface board in the MPS/EPS over
the Abis interface.
2. The Abis interface board processes the signaling according to the MAC, IP, and UDP
protocols. Then, the signaling is transmitted to the signaling processing board through the
SCUa board.
The downlink flow is the reverse of the uplink flow.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
NOTE
l The Gb interface board can be the PEUa/FG2a/POUc/FG2c board, and the XPUa/XPUb board performs
signaling processing. The boards shown in Figure 5-17 are only examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
As shown in Figure 5-17, the uplink signaling flow on the Gb interface is as follows:
1. In the MPS/EPS, the signaling processing board processes the signaling according to the
NS and BSSGP protocols. Then, the signaling is transmitted to the Gb interface board
through the SCUa board.
2. The Gb interface board processes the signaling according to the IP or FR protocol. Then,
the signaling is transmitted to the SGSN over the Gb interface.
The downlink flow is the reverse of the uplink flow.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
NOTE
l The Pb interface board can be the EIUa/OIUa/POUc board, and the XPUa board performs signaling
processing. The boards shown in Figure 5-18 are only examples.
l The INT in the figure stands for the interface board. You can use different interface boards as required.
As shown in Figure 5-18, the uplink signaling flow on the Pb interface is as follows:
1. In the MPS/EPS, the signaling processing board processes the signaling according to the
IP and RR protocols. Then, the signaling is transmitted to the Pb interface board through
the SCUa board.
2. The Pb interface board processes the signaling according to the LAPD protocol. Then, the
signaling is transmitted to the PCU over the Pb interface.
The downlink flow is the reverse of the uplink flow.
NOTE
Select a board according to the board function. For more information, see Boards. All the boards listed in
this chapter are used as examples for your reference.
1. The OM signal is transmitted from the LMT or M2000 to the OMUa board in the
MPS.
2. After the OM signal is processed by the OMUa board, it is transmitted to the SCUa
board through the backplane of the MPS.
3. The SCUa board then transmits the OM signal to the service boards to be maintained.
l OM signal flow in the EPS
1. The OM signal is transmitted from the LMT or M2000 to the OMUa board in the
MPS.
2. After the OM signal is processed by the OMUa board, it is transmitted to the SCUa
board through the backplane of the MPS.
3. The SCUa board in the MPS transmits the OM signal to the SCUa board in the EPS
through the Ethernet cable between the SCUa boards.
4. In the EPS, the SCUa board transmits the OM signal to the service boards to be
maintained.
l OM signal flow in the TCS
1. The OM signal is transmitted from the LMT or M2000 to the OMUa board in the
MPS.
2. After being processed by the OMUa board, the OM signal is transmitted to the SCUa
and Ater interface boards through the backplane of the MPS.
3. The OM signal is transmitted from the Ater interface board in the MPS to the Ater
interface board in the main TCS through the E1/T1 or optical cable between the Ater
interface boards. In the main TCS, the OM signal is transmitted from the Ater interface
board to the SCUa board through the backplane.
4. In the main TCS, the backplane switches the signal from the SCUa board to the service
boards to be maintained. The OM signal is transmitted from the SCUa board in the
main TCS to the SCUa board in the extension TCS through the Ethernet cable between
the SCUa boards. In the extension TCS, the backplane switches the signal from the
SCUa board to the service boards to be maintained.
Scenario 3: A over IP
In BM/TC combined mode, no TCS is configured, and the TC function is performed by the
media gateway (MGW). The OM signal flow in A over IP mode is the same as that in BM/TC
combined mode.
The transmission and networking between the BSC6900 and other NEs can be classified into
the following types: transmission and networking on the A/Gb interface, on the Abis interface,
on the Ater interface, and on the Pb interface.
IP over E1 Networking
In this networking mode, the PEUa/POUc board of the BSC6900 functions as the A interface
board. The PEUa board provides E1/T1 ports, and the POUc board provides channelized STM-1
ports and OC-3 ports. Figure 6-4 shows the IP over E1 networking on the A interface. The Gb
interface does not support the IP over E1 networking mode.
TDM-Based Networking
In this networking mode, the EIUa/OIUa/POUc board of the BSC6900 functions as the Abis
interface board. The EIUa board provides E1/T1 ports, the OIUa board provides channelized
STM-1 ports, and the POUc board provides channelized STM-1 ports and OC-3 ports. Figure
6-6 shows the TDM-based networking on the Abis interface.
IP over E1 Networking
In this networking mode, the BSC6900 and the base station communicate with each other through
the SDH/PDH network. The PEUa/POUc board functions as the Abis interface board. The PEUa
board provides E1/T1 ports, and the POUc board provides STM-1 ports and OC-3 ports. See
Figure 6-7.
Disadvantages:
l IP over E1 Networking
This networking mode does not meet the requirements of the evolution from the telecom
network to the IP network.
l IP over Ethernet Networking
The QoS of the network cannot be guaranteed easily. Therefore, the end-to-end QoS
mechanism must be adopted.
TDM-Based Networking
In this networking mode, the EIUa/OIUa/POUc board of the BSC6900 functions as the Ater
interface board. The EIUa board provides E1/T1 ports, the OIUa board provides channelized
STM-1 ports, and the POUc board provides channelized STM-1 ports and OC-3 ports. Figure
6-10 shows the TDM-based networking on the Ater interface.
Disadvantages: The cost of the TDM networking mode is higher than that of the IP networking
mode.
IP-Based Networking
In this networking mode, the POUc board of the BSC6900 functions as the Ater interface board
and provides channelized STM-1 ports and OC-3 ports. Figure 6-11 shows the IP-based
networking on the Ater interface.
TDM-Based Networking
In this networking mode, the EIUa/OIUa/POUc board of the BSC6900 functions as the Pb
interface board. The EIUa board provides E1/T1 ports, the OIUa board provides channelized
STM-1 ports, and the POUc board provides channelized STM-1 ports and OC-3 ports. Figure
6-12 shows the TDM-based networking on the Pb interface.
7 Parts Reliability
The BSC6900 guarantees its operation reliability by means of board redundancy and port
redundancy.
7.1 Concepts Related to Parts Reliability
The concepts related to parts reliability are board backup, port backup, resource pool, port
trunking, and port load sharing.
7.2 Board Redundancy
Board redundancy of the BSC6900 is of two types: board backup and resource pool.
7.3 Port Redundancy
Port redundancy is of three types: optical port backup, FE/GE port backup, port load sharing,
and port trunking.
7.1.1 Backup
Backup is a process of synchronization between the active and standby units. In backup mode,
two units of the same type work in active/standby mode, with one working as the active unit and
the other working as the standby unit. When the active unit is faulty, the active and standby units
are switched over, and the standby unit takes over the tasks from the active unit. In this manner,
the impact of unit failure on services is minimized.
Backup Types
l Board Backup
In board backup mode, two boards work in active/standby mode, with one working as the
active board and the other working as the standby board. Services can be processed by
either the active board only or both the active and standby boards. If the active board is
faulty, the BSC6900 automatically switches over the active and standby boards.
l Port Backup
In port backup mode, two ports work in active/standby mode, with one working as the
active port and the other working as the standby port. Data is transmitted through either the
active port only or both the active and standby ports. If the active port is faulty, the
BSC6900 automatically switches over the active and standby ports.
When the active and standby units working in 1+1 warm backup mode are switched over, the established
services may or may not be disrupted. If the established services are not disrupted and the impact on the
services is acceptable, the impact on the services in 1+1 warm backup mode is equivalent to that in hot
backup mode.
l 1+1 Cold Backup
The active and standby units work simultaneously, but the standby unit does not back up
the necessary signaling and service data of the active unit. When the active and standby
units are switched over, the established services are disrupted. When the active unit is faulty,
the standby unit takes over the tasks from the active unit.
l N+1 Warm Backup
The active and standby N+1 units work simultaneously, with N units being active and one
unit being standby. The standby unit backs up the necessary signaling and service data of
the active N units. When the active and standby units are switched over, services may be
slightly affected. When any active unit is faulty, the standby unit takes over the tasks from
this active unit.
l N+1 Cold Backup
The active and standby N+1 units work simultaneously, with N units being active and one
unit being standby. The standby unit does not back up the signaling and service data of the
active N units. When the active and standby units are switched over , the established services
are disrupted. When any active unit is faulty, the standby unit takes over the tasks from this
active unit.
NOTE
l The active and standby XPUa/XPUb boards of the BSC6900 work in 1:1 backup or 1+1 warm backup mode.
l The DPUa/DPUc/DPUd/DPUf/DPUg boards of the BSC6900 work in resource pool mode.
l Other active and standby boards of the BSC6900 work in 1+1 warm backup mode.
In resource pool mode, the system allocates resources nodes to the services that access the
resource pool and provides proper service resources.
Port trunking works in trunk groups. Multiple physical links form a trunk group. If a physical
link in the trunk group becomes faulty, the data carried on the faulty link is transferred to other
links in the trunk group. Thus, the link failure does not disrupt the communication between both
ends of the trunk group.
The traffic of the trunk group at the most can reach the total traffic on all the physical links in
the trunk group. Port trunking helps enhance transmission reliability and increase transmission
bandwidth.
When two GOUa/GOUc boards are configured in adjacent active and standby slots in a subrack
of the BSC6900, the two boards can be configured to work in one of the following two modes:
board backup with no port backup and board backup with port backup.
7.2.10 Backup of OMUa/OMUb/OMUc Boards
When the BSC6900 is configured with two OMUa/OMUb/OMUc boards in the MPS, the two
boards work in backup mode.
7.2.11 Backup of XPUa/XPUb Boards
When two XPUa/XPUb boards are configured in adjacent active and standby slots in a subrack
of the BSC6900, the two boards can be configured to work in backup mode.
7.2.12 Resource Pool of DPUa/DPUc/DPUd/DPUf/DPUg Boards
The DPUa/DPUc/DPUd/DPUf/DPUg boards of the BSC6900 and the Digital Signal Processors
(DSPs) in all the DPUa/DPUc/DPUd/DPUf/DPUg boards work in resource pool mode.
When two EIUa boards are configured to work in backup mode, one EIUa board is active and
the other is standby. The standby board synchronizes its data with that on the active board in
real time.
The backup mode of the EIUa board is configurable when the ADD BRD command is used to
add an EIUa board.
Switchover Modes
The SWP BRD command can be used to switch over the active and standby EIUa boards.
Switchover Process
When the active and standby EIUa boards are switched over, the active EIUa board becomes
standby after being reset, and the other EIUa board becomes active.
When two OIUa boards are configured to work in backup mode, one OIUa board is active and
the other is standby. The standby board synchronizes its data with that on the active board in
real time.
The backup mode of the OIUa board is configurable when the ADD BRD command is used to
add an OIUa board.
Switchover Modes
The SWP BRD command can be used to switch over the active and standby OIUa boards.
Switchover Process
When the active and standby OIUa boards are switched over, the active OIUa board becomes
standby after being reset, and the other OIUa board becomes active.
When two PEUa boards are configured to work in backup mode, one PEUa board is active and
the other is standby. The standby board synchronizes its data with that on the active board in
real time. Y-shaped E1/T1 cables are used to connect the active and standby boards to the peer
equipment. The E1/T1 ports on only the active board are used to transmit, receive, and process
data.
The backup mode of the PEUa board is configurable when the ADD BRD command is used to
add a PEUa board.
Switchover Modes
The SWP BRD command can be used to switch over the active and standby PEUa boards.
Switchover Process
When the active and standby PEUa boards are switched over, the active PEUa board becomes
standby after being reset, and the other PEUa board becomes active.
When two POUc boards are configured to work in board backup mode, one POUc board is active
and the other is standby. The standby board synchronizes its data with that on the active board
in real time. Port backup adopts the MSP 1:1 or MSP 1+1 backup mode. Services are processed
by the board where the active port is located. Active ports may be located on both the active and
standby boards because the switchover between the optical ports on the active and standby boards
does not affect the active/standby relation between the boards. In that case, both the active and
standby boards can process services. For details about the backup of the POUc optical ports, see
7.3.1 Optical Port Backup.
The backup mode of the POUc board is configurable when the ADD BRD command is used to
add a POUc board. If Backup is set to YES, both the POUc boards and their optical ports work
in backup mode. Therefore, the backup mode of the optical ports does not need to be configured
again.
Switchover Modes
l Automatic switchover: The active and standby POUc boards perform a switchover
automatically.
l Manual switchover: The SWP BRD command can be used to switch over the active and
standby POUc boards.
Switchover Process
When the active and standby POUc boards are switched over, the active POUc board becomes
standby after being reset, and the other POUc board becomes active.
NOTE
After an active/standby switchover, the BSC6900 determines the active and standby ports according to the
MSP protocol strategy.
When two SCUa/SCUb boards are configured to work in backup mode, one SCUa/SCUb board
is active and the other is standby. The standby board synchronizes its data with that on the active
board in real time. The data switched by the SCUa/SCUb boards consists of the user-plane data
and the control-plane data. The user-plane data is processed by the active and standby SCUa/
SCUb boards. The control-plane data is processed by the active SCUa/SCUb board.
Switchover Modes
l Automatic switchover: The active and standby SCUa/SCUb boards perform a switchover
automatically.
l Manual switchover: The SWP BRD command can be used to switch over the active and
standby SCUa/SCUb boards.
Switchover Process
When the active and standby SCUa/SCUb boards are switched over, the active SCUa/SCUb
board becomes standby after being reset, and the other SCUa/SCUb board becomes active.
When two TNUa boards are configured to work in backup mode, one TNUa board is active and
the other is standby. The standby board synchronizes its data with that on the active board in
real time.
Switchover Modes
l Automatic switchover: The active and standby TNUa boards perform a switchover
automatically.
l Manual switchover: The SWP BRD command can be used to switch over the active and
standby TNUa boards.
Switchover Process
When the active and standby TNUa boards are switched over, the active TNUa board becomes
standby after being reset, and the other TNUa board becomes active.
Switchover Modes
l Automatic switchover: The active and standby FG2a/FG2c boards perform a switchover
automatically.
l Manual switchover: The SWP BRD command can be used to switch over the active and
standby FG2a/FG2c boards.
l The active FG2a/FG2c board is reset, but the standby FG2a/FG2c board works properly.
l The active FG2a/FG2c board is faulty, but the standby FG2a/FG2c board works properly.
Switchover Process
When the active and standby FG2a/FG2c boards are switched over, the active FG2a/FG2c board
becomes standby after being reset, and the other FG2a/FG2c board becomes active.
NOTE
If the FG2a/FG2c boards work in board backup with port backup mode, after an active/standby switchover,
the BSC6900 determines the active and standby ports and defines the port load sharing strategy.
When two GCUa/GCGa boards are configured to work in backup mode, one GCUa/GCGa board
is active and the other is standby. The active board processes services. The standby board
synchronizes its data with the data on the active board in real time.
Switchover Modes
l Automatic switchover: The active and standby GCUa/GCGa boards perform a switchover
automatically.
l Manual switchover: The SWP BRD command can be used to switch over the active and
standby GCUa/GCGa boards.
The GCGa board supports the GPS clock. If the satellite card in the active GCGa board is faulty but that
in the standby GCGa board works properly, the active and standby GCGa boards are switched over.
Switchover Process
When the active and standby GCUa/GCGa boards are switched over, the active GCUa/GCGa
board becomes standby after being reset, and the other GCUa/GCGa board becomes active.
Switchover Modes
l Automatic switchover: The active and standby GOUa/GOUc boards perform a switchover
automatically.
l Manual switchover: The SWP BRD command can be used to switch over the active and
standby GOUa/GOUc boards.
Switchover Process
When the active and standby GOUa/GOUc boards are switched over, the active GOUa/GOUc
board becomes standby after being reset, and the other GOUa/GOUc board becomes active.
NOTE
If the GOUa/GOUc boards work in board backup with port backup mode, the BSC6900 determines the
active and standby ports and defines the port load sharing strategy after an active/standby switchover.
l When the GOUa/GOUc boards work in board backup with port backup mode, the
switchover between the active and standby GOUa/GOUc boards slightly affects data
transmission but does not disrupt ongoing services.
Switchover Modes
l Automatic switchover: The active and standby OMUa/OMUb/OMUc boards perform a
switchover automatically.
l Manual switchover: The SWP OMU command can be used to switch over the active and
standby OMUa/OMUb/OMUc boards.
By default, the period for automatic switchover between the active and standby OMUa/OMUb/
OMUc boards is 90 days. You can also use the SET ASWPARA command to set the period for
automatic switchover.
l Manual switchover can be performed only when the standby OMUa/OMUb/OMUc board
works properly and the state of data synchronization between the active and standby OMUa/
OMUb/OMUc boards is Data synchronization is successful.
NOTE
You can use the DSP OMU command to query the state of data synchronization between the active
and standby OMUa/OMUb/OMUc boards.
Switchover Process
When the active and standby OMUa/OMUb/OMUc boards are switched over, the active OMUa/
OMUb/OMUc board becomes standby, and the other OMUa/OMUb/OMUc board becomes
active.
switchover, the communication between the operation and maintenance terminal and the host
boards is interrupted for about one or two minutes. At that time, you cannot perform operation
and maintenance on the BSC6900. The switchover, however, does not affect ongoing services
of the BSC6900.
When two XPUa/XPUb boards are configured to work in backup mode, one XPUa/XPUb board
is active and the other is standby. The active board processes services. The standby board
synchronizes its data with that on the active board in real time.
Switchover Modes
l Automatic switchover: The active and standby XPUa/XPUb boards perform a switchover
automatically.
l Manual switchover: The SWP BRD command can be used to switch over the active and
standby XPUa/XPUb boards.
Switchover Process
When the active and standby XPUa/XPUb boards are switched over, the active XPUa/XPUb
board becomes standby after being reset, and the other XPUa/XPUb board becomes active.
Services in a subrack are preferentially processed by DPU boards in the same subrack. If the
DPU boards in the subrack are unavailable, the services are allocated to the DPU boards in
another subrack.
The priorities of DSPs to be allocated in descending order are DSPs in the same board, DSPs in
the same subrack, and DSPs in different subracks.
In MSP 1:1 backup mode, one optical port is active and the other is standby. Only the active
optical port transmits and receives data.
In MSP 1+1 backup mode, one optical port is active and the other is standby. Both the active
and standby optical ports transmit data, but only the active optical port receives data.
The SET MSP command is used to set the attributes of MSP backup.
Switchover Modes
l Automatic switchover: The active and standby optical ports perform a switchover
automatically.
l Manual switchover: The SET MSPCMD command can be used to switch over the active
and standby optical ports.
l The active optical port is faulty, but the standby optical port works properly.
l The active board is faulty, but the standby board works properly.
l The optical transmission device connected to the active optical port is faulty, but the optical
transmission device connected to the standby optical port works properly.
Switchover Process
When the active and standby optical ports are switched over, the active optical port stops
receiving data and becomes standby, and the original standby optical port starts to receive data
and becomes active.
Switchover Modes
l Automatic switchover: The active and standby ports on the active and standby FG2a/GOUa/
FG2c/GOUc boards perform a switchover automatically.
l Manual switchover: The SWP ETHPORT command can be used to switch over the active
and standby ports on the FG2a/GOUa/FG2c/GOUc boards.
Switchover Process
When the active and standby ports are switched over, the active port stops receiving and sending
data and becomes standby, and the original standby port starts to receive and send data and
becomes active.
Prerequisites
The BSC6900 supports load sharing between FE/GE ports that are located either on the same
board or on active and standby boards.
NOTE
l The BSC6900 does not support load sharing between the FE/GE ports on non-active/standby boards.
l The BSC6900 does not support load sharing between active and standby ports.
Working Principles
Load sharing between FE/GE ports is based on the user type. That is the data of a type of user
is carried on one FE/GE port, and that of another type of user is carried on another FE/GE port.
NOTE
The data of one user is transmitted through only one FE/GE port.
Application Scenario
When the FE/GE ports of the BSC6900 work in load sharing mode, the data towards the same
IP address may be transmitted through different ports, and thus different IP routes must be
configured. For example, load sharing between two FE/GE ports requires two IP routes. The IP
routes must have the same destination IP address, subnet mask, and priority, but different next-
hop IP addresses.
NOTE
Benefits
l Data traffic is shared by the ports to avoid the condition where some ports are busy whereas
others are idle.
l Load sharing enhances the reliability of data transmission.
Benefits
l In a trunk group, the bandwidth is evenly allocated to the GE/FE ports, thus fulfilling load
balancing.
l If a GE/FE link in a trunk group is faulty, the data stream on the link is automatically
switched to other GE/FE links.
l If an SCUa/SCUb or another service board is faulty, no associated switchover occurs.