BSC6900 UMTS Technical Description(V900R017C10_01)(PDF)-En

8/18/2019 BSC6900 UMTS Technical Description(V900R017C10_01)(PDF)-En

1/89

BSC6900 UMTS

V900R017C10

Technical Description

Issue 01

Date 2015-03-25

HUAWEI TECHNOLOGIES CO., LTD.


2/89

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd. All other trademarks and trade names mentioned in this document are the property of their respective holders. Notice

The purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd. Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.com

Email: [email protected]

Issue 01 (2015-03-25) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://www.huawei.com/


3/89

About This Document

PurposeThis document describes the logical structure, signal flow, transmission and networking, andreliability of the BSC6900. It helps the reader understand the implementation and working

principles of the BSC6900.

NOTE

The OMU board can be OMUa/OMUb/OMUc board. The SCU board can be SCUa/SCUb board. The SAU board can be SAUa/SAUc board.

Product VersionThe following table lists the product version related to the document.

Product Name Product Version Solution VersionBSC6900 V900R017C10 RAN17.1

Intended AudienceThis document is intended for:

l Network plannersl System engineersl Field engineers

Organization1 Change Description

This section provides information about the changes in different document versions. There aretwo types of changes, including function changes and editorial changes. Function changes refer to changes in functions of a specific product version. Editorial changes refer to changes inwording or addition of information that was not described in the earlier version.

BSC6900 UMTSTechnical Description About This Document


ii


4/89

2 Logical Structure

Logically, the BSC6900 consists of the following subsystems: the switching subsystem (MACswitching), service processing subsystem (RNC CP/RNC UP), interface processing subsystem(ATM/IP interface board), clock synchronization subsystem, and O&M subsystem (OMU

board).

3 Signal Flow

The BSC6900 signal flow consists of the user-plane signal flow, control-plane signaling flow,and O&M signal flow.

4 Transmission and Networking

The transmission and networking between the BSC6900 and other NEs can be classified intothe following types: transmission and networking on the Iub interface and on the Iu/Iur interface.

5 Reliability

The BSC6900 guarantees its operation reliability using board redundancy and port redundancy.

ConventionsSymbol Conventions

The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates an imminently hazardous situation which, if notavoided, will result in death or serious injury.

Indicates a potentially hazardous situation which, if notavoided, could result in death or serious injury.

Indicates a potentially hazardous situation which, if notavoided, may result in minor or moderate injury.

Indicates a potentially hazardous situation which, if notavoided, could result in equipment damage, data loss,

performance deterioration, or unanticipated results.

NOTICE is used to address practices not related to personalinjury.

Calls attention to important information, best practices andtips.

NOTE is used to address information not related to personalinjury, equipment damage, and environment deterioration.

General Con ventions



iii


5/89

The general conventions that may be found in this document are defined as follows.

Convention Description

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are inboldface . For example, log in as user root .

Italic Book titles are in italics .

Courier New Examples of information displayed on the screen are inCourier New.

Command Conventions

The command conventions that may be found in this document are defined as follows.


Boldface The keywords of a command line are in boldface .

Italic Command arguments are in italics .

[ ] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated byvertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated byvertical bars. One item is selected or no item is selected.

{ x | y | ... } * Optional items are grouped in braces and separated byvertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ] * Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI Conventions

The GUI conventions that may be found in this document are defined as follows.


Boldface Buttons, menus, parameters, tabs, window, and dialog titlesare in boldface . For example, click OK .

> Multi-level menus are in boldface and separated by the ">"signs. For example, choose File > Create > Folder .



iv


6/89

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 meansthe 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 movingthe pointer.

Double-click Press the primary mouse button twice continuously andquickly without moving the pointer.

Drag Press and hold the primary mouse button and move the pointer to a certain position.



v


7/89

Contents

About Thi s Document.....................................................................................................................ii

1 Change Description.......................................................................................................................1

2 Logical Structure............................................................................................................................22.1 Switching Subsystem......................................................................................................................................................4

2.2 Service Processing Subsystem........................................................................................................................................6

2.3 Interface Processing Subsystem.....................................................................................................................................6

2.4 Clock Synchronization Subsystem.................................................................................................................................7

2.4.1 Clock S ources..............................................................................................................................................................7

2.4.2 Structur e of the Clock Synchronization Subsystem....................................................................................................8

2.4.3 Clock S ynchronization Process.................................................................................................................................10

2.4.4 PLL Wo rking Principles............................................................................................................................................11

2.5 O&M Sub system..........................................................................................................................................................13

2.5.1 Dual O& M Plane.......................................................................................................................................................132.5.2 O&M N etwork...........................................................................................................................................................14

2.5.3 Data Co nfiguration Management..............................................................................................................................15

2.5.4 Security Management................................................................................................................................................18

2.5.5 Perform ance Management.........................................................................................................................................21

2.5.6 Alarm M anagement...................................................................................................................................................23

2.5.7 BSC690 0 Loading Management...............................................................................................................................25

2.5.8 BSC690 0 Upgrade Management...............................................................................................................................25

3 Signal Flow...................................................................................................................................363.1 User-Plane Signal Flow................................................................................................................................................37

3.1.1 UMTS Signal Flow Between Iub and Iu-CS/Iu-PS...................................................................................................37

3.1.2 CBC Signal Flow.......................................................................................................................................................39

3.2 Control-Pl ane Signaling Flow......................................................................................................................................40

3.2.1 Signalin g Flow on the Uu Interface...........................................................................................................................40

3.2.2 Signalin g Flow on the Iub Interface .........................................................................................................................42

3.2.3 Signaling Flow on the Iu/Iur Interface .....................................................................................................................43

3.3 O&M Signal Flow........................................................................................................................................................44

4 Transmission and Networking.................................................................................................464.1 Transmission and Networking on the Iu/Iur/Iur-p Interface ........................................................................................47

BSC6900 UMTSTechnical Description Contents


vi


8/89

4.1.1 ATM-based Networking on the Iu/Iur Interface........................................................................................................47

4.1.2 IP-based Networking on the Iu/Iur/Iur-p Interface....................................................................................................51

4.2 Transmission and Networking on the Iub Interface.....................................................................................................56

4.2.1 ATM-based Networking on the Iub Interface...........................................................................................................56

4.2.2 IP-based Networking on the Iub Interface.................................................................................................................58

4.2.3 ATM/IP Dual-Stack Networking on the Iub Interface..............................................................................................62

5 Reliability......................................................................................................................................645.1 Board Redundancy.......................................................................................................................................................67

5.1.1 Backup of AEUa Boards...........................................................................................................................................67

5.1.2 Backup of AOUa/AOUc Boards...............................................................................................................................68

5.1.3 Resource Pool of DEUa Boards................................................................................................................................69

5.1.4 Backup of FG2a/FG2c Boards..................................................................................................................................69

5.1.5 Backup of GCUa/GCUb/GCGa/GCGb Boards.........................................................................................................705.1.6 Backup of GOUa/GOUc/GOUe Boards....................................................................................................................71

5.1.7 Resource Pool of NIUa Boards.................................................................................................................................72

5.1.8 Backup of OMUa/OMUc Boards..............................................................................................................................72

5.1.9 Backup of PEUa/PEUc Boards..................................................................................................................................73

5.1.10 Backup of POUa/POUc Boards...............................................................................................................................74

5.1.11 Indepe ndent Mode of SAUa/SAUc Board..............................................................................................................75

5.1.12 Backup of SCUa/SCUb Boards...............................................................................................................................75

5.1.13 Backup of UOIa/UOIc Boards................................................................................................................................76

5.1.14 Backup of SPUa/SPUb/SPUc Boards......................................................................................................................775.2 Port Redu ndancy...........................................................................................................................................................78

5.2.1 STM-1 Optical Port Backup......................................................................................................................................78

5.2.2 Ethernet Port Backup.................................................................................................................................................79

5.2.3 Ethernet Port Load Sharing.......................................................................................................................................80

5.2.4 Ethernet Port Trunking..............................................................................................................................................80

BSC6900 UMTSTechnical Description Contents


vii


9/89

1 Change DescriptionThis section provides information about the changes in different document versions. There aretwo types of changes, including function changes and editorial changes. Function changes refer to changes in functions of a specific product version. Editorial changes refer to changes inwording or addition of information that was not described in the earlier version.

01 (2015-03-25)

This issue does not include any changes.

Draft A (2014-01-15)

Compared with 02 (2014-06-30) of V900R016C00, this issue includes the following changes.

Change Type Change Description

Functionalchange

Added None.

Modified Deleted the description that the DEUa board preferentially processes services in the subrack where itis installed from 5.1.3 Resource Pool of DEUaBoards .

Added the following description to 5.1.14 Backup of SPUa/SPUb/SPUc Boards : Backup data may be lostand ongoing services may be interrupted if the interval

between active/standby switchovers of SPUa/SPUb/SPUc boards is shorter than 5 minutes.

Deleted None.

Editorial change None.

BSC6900 UMTSTechnical Description 1 Change Description


1


10/89

2 Logical StructureAbout This Chapter

Logically, the BSC6900 consists of the following subsystems: the switching subsystem (MACswitching), service processing subsystem (RNC CP/RNC UP), interface processing subsystem(ATM/IP interface board), clock synchronization subsystem, and O&M subsystem (OMU

board).

Figure 2-1 shows the logical structure of the BSC6900.

Figure 2-1 Logical structure

2.1 Switching SubsystemThe switching subsystem manages the switching of data flow, signaling flow, and O&M signals.

2.2 Service Processing SubsystemThe service processing subsystem performs the control functions defined in 3GPP protocols and

processes services of the BSC6900.

2.3 Interface Processing Subsystem

BSC6900 UMTSTechnical Description 2 Logical Structure


2


11/89

The interface processing subsystem provides transmission ports and resources, processestransport—layer and network—layer messages, and enables interaction between the BSC6900internal data and external data.

2.4 Clock Synchronization SubsystemThe clock synchronization subsystem of the BSC6900 consists of the GCUa/GCUb/GCGa/GCGb board and the clock processing units of each subrack. It provides working clocks andreference clocks for base stations for the BSC6900.

2.5 O&M SubsystemThe O&M subsystem enables management and maintenance in the following scenarios: routinemaintenance, emergency maintenance, upgrades, and capacity expansion. It enablesmanagement in data configuration, security, performance, alarm, loading, and upgrade. TheO&M subsystem consists of the EOMUa board.



3


12/89

2.1 Switching Subsystem

The switching subsystem manages the switching of data flow, signaling flow, and O&M signals.

Functions

The switching subsystem performs the following functions:

l Provides intra-subrack Medium Access Control (MAC) switching

l Provides inter-subrack MAC switching and TDM switching

l Distributes clock signals and radio frame number (RFN) signals to service processing boards

Hardware Involved

The switching subsystem consists of the SCUa/SCUb boards, high-speed backplane channelsin each subrack, and inter-subrack cables between SCUa/SCUb boards.

Network topologies between subracks

The BSC6900 subracks can be connected in the star or chain topology. In Figure 2-2 , (1) and(2) represent the star and chain topologies, respectively, where the dots represent subracks.

l Star topology

One node functions as the center node and it is connected to each of the other nodes. Thecommunication between the other nodes must be switched by the center node.

l Chain topology

There is a connection between every two adjacent nodes. If an intermediate node is out of service, the communication between other nodes is affected. The bandwidth usageefficiency is high in this topology.

Figure 2-2 Network topologies between subracks

In the switching subsystem of the BSC6900, the star or chain topology is established amongMAC switching logical modules.



4


13/89

Inter-Subrack ConnectionThe MAC switching logical module switches the ATM-based or IP-based traffic data, O&Msignals, and signaling. Switching is performed by the SCUa boards and the Ethernet cables

between the SCUa/SCUb boards.

The MPS functions as the basic subrack, and a maximum of five EPSs function as extensionsubracks. The star interconnections between the MPS and EPSs are established through theEthernet cables between SCUa boards, as shown in Figure 2-3 .

Figure 2-3 Interconnections between the MPS and EPSs through the inter-subrack cables between SCUa boards

The MPS functions as the basic subrack. Star interconnections are established between the MPSand EPSs in the MPR through the Ethernet cables between SCUb boards. Chain interconnectionsare established between the EPSs in the MPR and other EPSs through the Ethernet cables

between SCUb boards, as shown in Figure 2-4 .

Figure 2-4 Interconnections between the MPS and EPSs through the inter-subrack cables between SCUb boards

For example, as shown in Figure 2-4 , subracks 0, 1, and 2 are in the same ca binet and star interconnections are established between them through the Ethernet cables between SCUb



5


14/89

boards. Chain interconnections are established between subracks 1 and 3 through the Ethernetcables between SCUb boards. Data is exchanged between subrack 0 and subrack 3 throughsubrack 1. For details, see Installing the Inter-SCUb SFP+ High-Speed Cables Between DifferentSubracks.

2.2 Service Processing SubsystemThe service processing subsystem performs the control functions defined in 3GPP protocols and

processes services of the BSC6900.

Functions

The service processing subsystem performs the following functions:

l User data transfer

l System admission controll Radio channel ciphering and decipheringl Data integrity protectionl Mobility managementl Radio resource management and controll Cell broadcast service controll System information and user message tracingl Data volume reportingl Radio access managementl CS service processingl PS service processing

Service processing subsystems communicate with one another through the switching subsystemto form a resource pool and to perform tasks cooperatively. They can be increased as required,according to the linear superposition principle, thereby improving the service processingcapability of the BSC6900.

Hardware Involved

The service processing subsystem consists of:

l Signaling processing boards: SPUa, SPUb, and SPUcl Service processing boards: DPUb and DPUe

2.3 Interface Processing SubsystemThe interface processing subsystem provides transmission ports and resources, processestransport—layer and network—layer messages, and enables interaction between the BSC6900internal data and external data.

Functions

The interface processing subsystem performs the following functions:



6


15/89

l Provides the following types of ports for IP and ATM transmission:– E1/T1 electrical ports– Channelized STM-1/OC-3 optical ports– Unchannelized STM-1/OC-3 optical ports– FE/GE electrical ports– GE optical ports

l Processes transport—layer and network—layer messages and hides differences betweenthem within the BSC6900.

l Terminates transport—layer and network—layer messages on the interface boards in theuplink. It also transmits the user plane, control plane, and management plane datagrams tothe corresponding service processing boards. The signaling flow processing in the downlink is the reverse of the signaling flow processing in the uplink.

Hardware InvolvedThe interface processing subsystem consists of the AEU, AOU, FG2, GOU, PEU, and UOI

boards.

2.4 Clock Synchronization SubsystemThe clock synchronization subsystem of the BSC6900 consists of the GCUa/GCUb/GCGa/GCGb board and the clock processing units of each subrack. It provides working clocks andreference clocks for base stations for the BSC6900.

2.4.1 Clock SourcesThe BSC6900 can use the following clock sources: Building Integrated Timing Supply System(BITS) clock, external 8 kHz clock, LINE clock, Global Positioning System (GPS) clock, andlocal oscillator.

BITS Clockl BITS clock signals consist of 2 MHz, 2 Mbit/s, and 1.5 Mbit/s clock signals. 1.5 Mbit/s

clock signals are T1 clock signals. 2 MHz and 2 Mbit/s are E1 clock signals. 2 MHz isintended for electrical impulse, and 2 Mbit/s is intended for data flow.

l The BITS clock has two inputs: BITS1 and BITS2. BITS1 and BITS2 correspond to theCLKIN0 and CLKIN1 ports on the GCUa/GCUb/GCGa/GCGb board, respectively. TheBSC6900 obtains the BITS clock signals through the CLKIN0 or CLKIN1 port.

External 8 kHz Clock

Through the COM1 port on the GCUa/GCUb/GCGa/GCGb board, the BSC6900 obtains 8 kHzstandard 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 theGCUa/GCUb/GCGa/GCGb board through the backplane channel. The LINE clock has two inputmodes: LINE1 and LINE2.



7


16/89

NOTE

LINE1 and LINE2 correspond to backplane channel 1 and backplane channel 2, respectively.

GPS ClockThe GPS clock provides 1 Pulse Per Second (PPS) clock signals. The BSC6900 obtains the GPSclock signals from the GPS system. The GCGa/GCGb board is configured with a satellite card,and the BSC6900 receives the GPS signals over the antenna port on the GCGa/GCGb board.

NOTE

The GCUa/GCUb board is not configured with a satellite card. Therefore, when the BSC6900 is configured withthe GCUa/GCUb board instead of the GCGa/GCGb board, the GPS clock is unavailable to the BSC6900.

Local OscillatorIf the BSC6900 fails to obtain any external clock, the BSC6900 can obtain its working clock

signals from the local oscillator.

2.4.2 Structure of the Clock Synchronization SubsystemThe clock synchronization subsystem consists of the clock board, backplanes, clock cables

between subracks, and clock module in each board.

Figure 2-5 shows the structure of the clock synchronization subsystem.

Figure 2-5 Structure of the clock synchronization subsystem



8


17/89

The structure of the BSC6900 clock synchronization subsystem is described as follows:

l The BSC6900 clock board can be the GCUa/GCUb/GCGa/GCGb board. The BSC6900

cannot be configured with both the GCUa/GCUb and GCGa/GCGb boards. It can beconfigured with only the GCUa/GCUb board or the GCGa/GCGb board, depending on theclock type.

l If the MPS extracts clock signals, the clock signals enter the MPS in any of the followingways:– The clock signals enter the port on the panel of the GCUa/GCUb/GCGa/GCGb board.– The clock signals enter the port on the panel of an interface board that can extract line

clock signals, include AEUa/AOUa/AOUc/PEUa/POUa/POUc/UOIa/UOIc board. Theclock signals are then switched to the GCUa/GCUb/GCGa/GCGb board through the

backplane.

– The GCUa/GCUb/GCGa/GCGb board generates oscillator clock signals.l If the EPS extracts clock signals, the interface board that extracts clock signals must be the

AEUa/AOUa/PEUa/POUa/UOIa board.

Figure 2-6 shows the connections of the clock cables between the clock boards in the MPS andthe SCU boards in the EPS when the BSC6900 is configured with active and standby clock

boards and SCU boards.

Figure 2-6 Connections of the clock cables between the clock boards in the MPS and the SCU boards in the EPS

The active and standby clock boards in the MPS are connected to the active and standby SCU boards in the EPS through the Y-shaped clock signal cables. This connection mode ensures thatthe 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 SCU board.



9


18/89

In addition, the Y-shaped clock signal cable ensures the proper working of the SCU boardsduring the switchover of the active and standby clock boards.

NOTE

In the MPS, the clock board sends clock signals to the SCU board in the same subrack through the backplanechannel. Therefore, a Y-shaped clock signal cable is not required.

2.4.3 Clock Synchronization ProcessThe BSC6900 processes external clock signals before sending them to its boards. The clock synchronization process varies slightly from one subrack to another.

NOTE

Select a board according to the board function. For more information, see Boards. All the boards listed inthis chapter are used as examples for your reference.

Clock Synchronization in the MPS/EPSThe MPS/EPS reference clock signals are provided by the clock board. The clock board canextract clock signals from an external device or extract LINE clock signals from the Iu-CSinterface. The GCGa/GCGb board can also extract clock signals from the GPS.l Figure 2-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 2-8 shows the process of clock synchronization in the MPS/EPS when the clock

board extracts LINE clock signals from the Iu-CS interface.

Figure 2-7 Process of clock synchronization in the MPS/EPS (1)



10


19/89

Figure 2-8 Process of clock synchronization in the MPS/EPS (2)

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 porton 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 theclock 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 SCU board in the MPS through the backplane and to the SCU

board in each EPS through the clock signal output ports.

3. The SCU board in the MPS/EPS transmits the clock signals to other boards in the samesubrack through the backplane.

NOTE

The Iub interface boards transmit the clock signals to the base stations.

2.4.4 PLL Working PrinciplesA phase-locked loop (PLL) uses the digital phase discrimination, software filtering, and PIDcontrol algorithms to implement the phase lock function. It tracks selected reference clock sources and outputs high-precision and reliable 8 kHz clock signals.

A PLL works in one of the following states: Free Running, Quick Capture, Lock, and Hold.Figure 2-9 shows how a PLL shifts from one state to another in automatic working mode.



11


20/89

Figure 2-9 Diagram for PLL state shift

l Free Running

– If no reference clock source is configured or the reference clock sources are unavailable,the PLL works in the Free Running state.

– If there's an available reference clock source, the BSC judges the reference clock sourcefor 260 seconds. If the source remains stable for more than 260 seconds, the PLL shiftsto the Quick Capture state. Otherwise, the PLL remains in the Free Running state.

l Quick Capture

– If the reference clock source is available and remains stable for a period (400 secondsfor a GPS source or 200 seconds for any source other than GPS), the PLL shifts to the

Lock state.– If the reference clock source is lost, the PLL shifts back to the Free Running state.

l Lock

– If the reference clock source is lost when the lock has been started for more than 600seconds, the PLL shifts to the Hold state.

– If the reference clock source is lost within 600 seconds after the lock is started, the PLLshifts back to the Free Running state.

l Hold

– If there's still no reference clock source available 10 days after the PLL shifts to the

Hold state, the PLL shifts back to the Free Running state.



12


21/89

– If other reference clock source is available, or the reference clock source recovers within10 days and remains stable for more than 260 seconds, the PLL shifts to the Quick Capture state.

2.5 O&M SubsystemThe O&M subsystem enables management and maintenance in the following scenarios: routinemaintenance, emergency maintenance, upgrades, and capacity expansion. It enablesmanagement in data configuration, security, performance, alarm, loading, and upgrade. TheO&M subsystem consists of the EOMUa board.

2.5.1 Dual O&M Plan eThe BSC6900 has a dual O&M plane to prevent single-point failure from affecting the normaloperation and maintenance.

Figure 2-10 shows the dual O&M plane design.

Figure 2-10 Dual O&M plane

The internal network and external network should be on different network segments to ensurethat the two networks are isolated.

The dual O&M 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 O&Mchannel works properly.



13


22/89

The active/standby OMU boards use the same external virtual IP address to communicate withthe LMT or U2000 and use the same internal virtual IP address to communicate with the SCU

boards.

l When the active OMU board is faulty, an active/standby switchover is performedautomatically, and the standby OMU board takes over the O&M task. In this case, theinternal and external virtual IP addresses remain unchanged. This ensures the proper communication between the internal and external networks of the BSC6900.

l When a single-poin t failure occurs on the switching network, the active/standby SCU boards in each subrack are switched over automatically. This ensures that the O&M channelworks properly.

2.5.2 O&M NetworkThe O&M network of the BSC6900 consists of the U2000, LMT, OMU, SCU boards, and O&Mmodules in other boards.

NOTE

Either the OMUa or OMUc board can serve as an OMU.

Either the SCUa or SCUb board can serve as an SCU.

Figure 2-11 shows the structure of the BSC6900 O&M network.

Figure 2-11 Structure of the O&M network

NOTE

Figure 2-11 shows only some boards in the O&M network.

The SCU boards in the EPS are connected to the SCU boards in the MPS through crossover cables. The crossover cables transmit O&M signals from the MPS to the EPS.



14


23/89

U2000

The U2000 is a centralized network management system. The U2000 is connected to theBSC6900 through Ethernet cables. One U2000 can remotely manage multiple BSCs(BSC6900).

LMT

The LMT is connected to the OMU board of the BSC6900. One or multiple LMTs can beconnected to the OMU board directly or through networks. The maintenance of the BSC6900can be performed locally or remotely through the LMT. The LMT is connected to an alarm boxthrough a serial cable.

OMU Board

The OMU board is the back administration module of the BSC6900. It is connected to an externaldevice through the Ethernet cable. The BSC6900 can be configured with one OMU board inindependent mode or with two OMU boards in active/standby mode.

The OMU board functions as a bridge between the BSC6900 and the LMT or U2000. The O&Mnetwork of the BSC6900 is classified into the following networks:

l Internal network: implements the communication between the OMU board and the host boards of the BSC6900.

l External network: implements the communication between the OMU board and externaldevices, such as the LMT or U2000.

SCU BoardThe SCU board is the switching and control board of the BSC6900. It is responsible for theO&M of the subrack where it is located. If a subrack is configured with two SCU boards, thetwo boards work in active/standby mode.

The SCU board performs O&M on other boards in the same subrack through the backplanechannels. The SCU boards in different subracks are connected through crossover cables.

2.5.3 Data Configuration ManagementThe data configuration management involves managing the data configuration process of the

BSC6900 so that configuration data is successfully sent to the related boards.

Data Configuration Modes

The BSC6900 supports two data configuration modes: effective mode and ineffective mode.

If data configuration is performed on the BSC6900 in effective mode, the configuration datatakes effect on the host boards in real time.

If data configuration is performed on the BSC6900 in ineffective mode, the configuration datatakes effect only after the BSC6900 is switched to the effective mode and is reset.

NOTE

For the concept of host boards, see 2.5.8 BSC6900 Upgrade Management .



15


24/89

l Configuration in effective mode

Configuration in effective mode is applied to dynamic modification of the BSC6900configuration data.

Figure 2-12 shows the principle of configuration in effective mode.

Figure 2-12 Principle of configuration in effective mode

The process of configuration in effective mode is as follows:

1. The BSC6900 is switched to the effective mode.

2. The LMT or U2000 sends MML commands to the configuration management moduleof the OMU.

3. Upon receiving the MML commands, the configuration management module of theOMU sends the configuration data to the database of the related host board and writesthe data to the OMU database.

l

Configuratio n in ineffecti ve modeConfiguration in ineffective mode is applied to BSC6900 initial configuration.

Figure 2-13 shows the principle of configuration in ineffective mode.

Figure 2-13 Principle of configuration in ineffective mode

The process of configuration in ineffective mode is as follows:

1. The BSC6900 is switched to the ineffective mode.

2. The LMT or U2000 sends MML commands to the configuration management moduleof the OMU.



16


25/89

3. Upon receiving the MML commands, the configuration management module sendsonly the configuration data included in the MML commands to the OMU database.

4. When a subrack or the BSC6900 is reset, the OMU formats the configuration data inthe database into a .dat file, loads the file onto the related host boards, and then

activates the configuration data.

Data Configuration Check

The data configuration check involves the data validity check and data consistency check. Thisensures the normal operation of the BSC6900.

l Data validity check

The data validity check checks whether a configuration complies with the configurationrules and whether an MML script file complies with the syntactic rules.

When a configuration is performed or an MML command is executed, the data validity

check is performed. If an error is detected, the BSC6900 stops performing the configurationor running the command. At the same time, a warning message is displayed.

l Data consistency check

The data consistency check consists of two parts:– Checking data consistency between the active and standby OMUs

If the BSC6900 is configured with the active and standby OMUs, the data on the activeOMU must be the same as that on the standby OMU to ensure BSC6900 reliability. If a data consistency is detected, an active/standby switchover cannot be performed whenthe active OMU becomes faulty.

– Checking data consistency between the OMU and host boards

The data on th e ho st boards must be the same as that on the OMU. Otherwise, the systemcannot run stably. In addition, some data modified by users cannot take effect. Figure2-14 shows the procedure for the data consistency check.

Figure 2-14 Checking data consistency between the OMU and host boards



17


26/89

The procedure for checking data consistency between the OMU and host boards is asfollows:

1. On the LMT, a data consistency check command is sent to the OMU automaticallyon a regular basis or manually.

2. The OMU analyzes the parameters of the command and checks whether the data inthe board databases is the same as that in the OMU database.

3. The OMU generates a result file and sends it to the LMT.

NOTE

For more information about data configuration, see section Running MML Commands of BSC6900 UMTSLMT User Guide.

2.5.4 Security ManagementThe security management ensures the security of user login and helps to identify equipment

faults. It involves rights management, log management, and inventory management.

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 certainrights to the users at each level. To log in to the LMT of the BSC6900, a user must enter theregistered 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 theBSC6900 installation or during the disconnection from the U2000.

– Domain users: refer to the accounts that are created, changed, authenticated, andauthorized on the U2000. Domain users can manage the BSC6900 after logging in tothe LMT or after logging in to the U2000 server through the U2000 client.

l Password– You can use upper-case letters, lower-case letters, digits, and special characters to

specify a user password to the maximum complexity.– Run the SET PWDPOLICY command to set Maximum Valid Days and Password

History Records Number .NOTE

Run the LST PWDPOLICY command to query the password configuration information.

l User rights



18


27/89

Table 2-1 Definitions of the user rights

Class Rights CommandGroup

Description

Guest Guest can only browse data.

G_0 The objects in this command group are used toquery system information, such as users,command groups, logs, NTP, EMS, and timezones.

G_2 The objects in this command group are used toquery data configurations.

G_4 The objects in this command group are used toquery alarm information.

G_6 The objects in this command group are used toquery performance data, for example, a result fileor a task file.

G_8 The objects in this command group are used toquery device information such as device status.

G_13 The objects in this command group are used toquery the information about base stations, for example, the attributes and boards of basestations.

User In addition tothe rightsgranted to theGuest, User can performsystem OM.

G_7 The objects in this command group are used to perform performance management, for example,to activate a performance task file or to upload a

performance result file.

G_9 The objects in this command group are used to perform device management, for example, toreset, block, unblock, or switch over a board.

G_10 The objects in this command group are used totrace and monitor the signal flow on the control

plane and on the user plane, for example, to querya tracing task or to create/delete/start a tracingtask.

G_11 The objects in this command group are used tomodify device panels.

G_12 The objects in this command group are used to perform software management, for example, patch management.



19


28/89

Class Rights CommandGroup

Description

G_14 The objects in this command group are used to perform base station management, for example,to manage base station software or to reset a basestation.

Operator In addition tothe rightsgranted to theUser, theOperator can

perform data

configurationon theequipment.

G_3 The objects in this command group are used toconfigure data, for example, the data for a newcell.

G_5 The objects in this command group are used to perform alarm management, for example, to

clear an alarm or to set the alarm severity.

Administrator

Administrator has the highestoperationrights. It canmanage all theother users.

G_1 The objects in this command group are used tomanage system information, for example, tomanage a user, to set the time zone, to set thedaylight saving time, or to perform batchconfiguration.

Custom The rights of this user are defined by the Administrator according to the

command groups required for the user.

Log ManagementLog management records the operation history and saves the related logs about the BSC6900.Therefore, it helps analyze and identify faults.

Table 2-2 lists the types of logs that are recorded when the BSC6900 is running.

Table 2-2 Types of logs

Type Description

Running log Records the information on the operating status of the system. Theinformation is used to analyze and locate faults.

Operation log Records the information on operation and maintenance performed by users.

Security log Records the information on operations that may affect systemsecurity, for example, information on changing the user password.

Log management provides the following functions:



20


29/89


30/89

Performance Management Process

The BSC6900 boards collect performance measurement data and periodically report the data tothe performance measurement module of the OMU. According to the task file, the performance

measurement module periodically reports the measurement data to the U2000.Figure 2-15 shows the process of periodically collecting performance measurement data by theBSC6900.

Figure 2-15 Process of periodically collecting performance measurement data

The process of periodically collecting performance measurement data is as follows:

1. The user registers a customized performance measurement task and specifies the object,time, and item attributes of the task on the U2000 client.

2. Based on the performance measurement task, the U2000 server modifies the measurementtask file, sends it to the OMU, and issues a command to activate the new measurement task file.

3. Based on the new measurement task file, the OMU requests host boards to collect dataaccording to the new requirements. The OMU receives the measurement results from thehost boards and saves them as files.

4. The OMU notifies the U2000 server of the measurement results and uploads the files intothe U2000 server. The U2000 server processes the files and saves them into the database.

5. Based on the performance measurement task registered by the U2000 client, the U2000server obtains the relevant results from the database, performs certain calculation on them,and then sends the result to the U2000 client.

Measurement

Performance measurement objects consist of three types: default measurement objects, non— default measurement objects, and real-time measurement objects. You cannot add objects to or remove objects from the list of default measurement objects on the U2000.

l Default measurement objects

The BSC6900 automatically measures all objects of this type. The default measurementtask file supports three periods:

– Normal measurement period with a default duration of 30 minutes or 60 minutes. A proper measurement period can be selected on the U2000.



22


31/89


32/89

Figure 2-16 Alarm management process

Each board automatically detects alarms and reports them to the OMU. The OMU then classifiesthese alarms into different severity levels and sends them to the LMT or U2000 server. You can

view and manage alarm information on the LMT or U2000 client.The alarm management module of the OMU provides the following functions:

l Alarm storage

The alarm management module stores the alarms reported by host boards in the databaseof the OMU.

l Alarm processing

The alarm management module processes the operation commands from the LMT or U2000client and then returns the operation results to the LMT or U2000 client. These commandsinclude 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 reportsthe two alarms to the LMT or U2000 client.

l Alarm clearing

After an alarm is handled, the system automatically clears the alarm. At the same time, thealarm management module clears the alarm information from the LMT or U2000.

NOTE

During a BSC6900 upgrade, the BSC6900 will re-detect alarms and will not inherit the alarms of the sourceversion.

l For the alarms generated on the BSC6900, the BSC6900 will re-detect alarms after a reset.l For the alarms generated on the GBTS, the BSC6900 will re-detect alarms after the GBTS resets during a

BSC upgrade. If the GBTS OML is always disconnected after a BSC upgrade, the GBTS can not reportalarms.

l For the alarms generated on the eGBTS, the alarms are directly reported to the U2000. Therefore, theBSC6900 upgrade will not affect the alarms.

Alarm Box

The alarm box generates audible and visual alarms. The red, orange, yellow, and green alarmindicators on the alarm box indicate the critical, major, minor, and warning alarms, respectively.Different alarm severity levels have different alarm sounds. Figure 2-17 shows the working

principle of the alarm box.



24


33/89

Figure 2-17 Working principle of the alarm box

The alarm box is connected to the LMT through a serial port. When an alarm is reported, theLMT 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.

2.5.7 BSC6900 Loading ManagementThe BSC690 0 loading m anagement involves managing the process of loading program and data

files onto boards after the boards (or subracks) are started or restarted.

NOTE


Principle of Loading

The OMU board and the active SCU board in each subrack play important roles during theBSC6900 loading process.

l The OMU board functions as the first-level center of the entire BSC6900 loading

management process. The loading and power-on of the OMU are independent of other boards. The OMU board processes the loading control requests of other boards.

l The active SCU board functions as the second-level center of the loading management process. If the OMU board cannot be detected, the active SCU board in a subrack processesthe loading control requests from other boards in the same subrack. If the SCU boards inan extension subrack are not started, the active SCU board in the basic subrack processesthe loading control requests from the boards in the extension subrack.

2.5.8 BSC6900 Upgrade ManagementUpgrade management involves managing the procedures for upgrading the software and patches

of the OMU and host boards.

Concepts

Table 2-3 describes the OMU-related concepts.



25


34/89

Table 2-3 OMU-related Concepts

Concept Description

Active

andstandbyworkspaces

The active and standby workspaces are used to store files of different versions

on the OMU.

Relationship

betweenthe activeandstandbyworkspaces

l The relationship between the active and standby workspaces is relative. Theactive/standby relationship is determined by the location where the runningversion files are stored. The workspace that stores the running version files isreferred to as the active workspace, and the other workspace is referred to asthe standby workspace.

l In the OMU, the active and standby workspaces are independent from eachother. The running of the active workspace does not change any informationstored in the standby workspace.

Relationship

betweenthe activeandstandbyworkspaces of theactive

andstandbyOMUs

The active and standby workspaces of the active OMU map onto those of thestandby OMU. The files stored in the active workspaces can be automaticallysynchronized in real time between the active and standby OMUs, while the filesstored in the standby workspaces must be synchronized manually between theactive and standby OMUs.

Host boards

Host boards refer to all the boards except the OMU.

Table 2-4 describes the concept of version and patch and their respective upgrade and rollback.



26


35/89

Table 2-4 Concept of Version and Patch and their Respective Upgrade and Rollback

Concept Description

Version l A version refers to a set of features for a product or solution within a specific

period of time, including the first production/solution delivery or subsequent product/solution delivery after an upgrade. A product/solution may havemultiple versions.

l A version No. (VxxxRxxxCxx) consists of three parts: Vxxx, Rxxx, and Cxx.Therefore, you can also refer to a version as a VRC version. The first version

No. is Vx00R0xxC0x, such as V900R017C10.– The Vxxx part is called the V version and starts from 100, with increments

of 100.– The Rxxx part is called the R version and starts from 001, with increments

of 1.

– The Cxx part is called the C version and starts from 00, with incrementsof 1.

Patch l A patch refers to a version delivered after the first delivery version. The patch No. is SPyABC, where SP stands for Service Pack. For example, the first patch No. after V900R017C10 is V900R017C10SPC100.

l If y is C, the patch is a cold patch. If y is H, the patch is a hot patch. SPH andSPC are numbered separately. ABC refers to the SP patch serial number. Itranges from 001 to 999, with increments of 1.

Versionupgrade

Version upgrades consist of two types:l Upgrade from one VRC version to another VRC versionl Upgrade within the same VRC version but the source version and target

version use different A values (no requirements for B and C values)

NOTEAn upgrade within the same VRC version is referred to as a patch upgrade if the sourceversion and target version use the same A value but different B and C values.

The upgrade interrupts services and operation and maintenance. Therefore,service experience is adversely affected.

Versionrollback

Perform a version rollback if you need to roll back the post-upgrade version tothe pre-upgrade version after a version upgrade. The rollback interrupts ongoingservices and operation and maintenance. Therefore, service experience isadversely affected.



27


36/89

Concept Description

Cold patch

upgrade

l For example, an upgrade from V900R017C10SPH501 toV900R017C10SPC510 is a cold patch upgrade. The upgrade interrupts

services and operation and maintenance. Therefore, service experience isadversely affected.l Cold patches consist of OMU patches and cold patches of host boards.

NOTEl The OMU software supports only a cold patch upgrade.l V900R017C10SPC500 must be upgraded to the immediate version

V900R017C10SPC510, which is a cold patch, before being upgraded toV900R017C10SPH511. Therefore, an upgrade from V900R017C10SPC500 toV900R017C10SPH511 is referred to as a cold patch upgrade.

Cold patchrollback

Perform a cold patch rollback if you need to roll back the post-upgrade patch tothe pre-upgrade patch after a cold patch upgrade. For example, a rollback fromV900R017C10SPC510 to V900R017C10SPH501 is a cold patch rollback. Therollback interrupts ongoing services and operation and maintenance. Therefore,service experience is adversely affected.

NOTEV900R017C10SPH511 must be rolled back to the immediate versionV900R017C10SPC510, which is a cold patch, before being rolled back toV900R017C10SPC500. Therefore, a rollback from V900R017C10SPH511 toV900R017C10SPC500 is referred to as a cold patch rollback.

Hot patchupgrade

l For example, an upgrade from V900R017C10SPC510 toV900R017C10SPH511 is a hot patch upgrade. The upgrade interrupts O&M

but not ongoing services. Therefore, service experience is not affected.l Hot patches consist of OMU patches and hot patches of host boards.

NOTEThe OMU software supports only a cold patch upgrade.

Hot patchrollback

Perform a hot patch rollback if you need to roll back the post-upgrade patch tothe pre-upgrade patch after a hot patch upgrade. For example, a rollback fromV900R017C10SPH511 to V900R017C10PC510 is a hot patch rollback. Therollback interrupts O&M but not ongoing services. Therefore, service experienceis not affected.

NOTETo perform a rollback to a hot patch, for example, a rollback from V900R017C10SPH500

to V900R017C10SPH201, first perform a rollback to the cold patch V900R017C10SPC200and then an upgrade to the hot patch V900R017C10SPH201.

Upgrade Method

You can use the dedicated upgrade tool to remotely upgrade the BSC6900 through its O&Mnetwork. For details about how to use the upgrade tool, see the corresponding upgrade guide.To obtain the upgrade guide and the required installation package, contact Huawei engineers.Save the required installation package to the root directory of a drive (for example, drive D) onthe PC.



28


37/89

The following sections describe version upgrade/rollback, hot patch upgrade/rollback, and cold patch upgrade/rollback.

Version Upgrade Process

Figure 2-18 shows the process of a version upgrade.

Figure 2-18 Version upgrade process

1. Start the upgrade tool and upload the target software package to the OMU. The detailed procedure is as follows:

a. Start the upgrade client on the PC.



29


38/89

b. Upload the target software package. The upgrade server of the active OMU uses theFTP server to upload the target software package to the specified directory of the activeOMU. The target software package includes the upgrade server and upgrade versionfiles, which contain programs, data, and patch packages.

c. The upgrade client on the PC starts the upgrade server of the active OMU and thensets up a connection between them.

d. The upgrade server of the active OMU synchronizes the target software packages tothe specified directory of the standby OMU.

e. The upgrade server of the active OMU starts the upgrade server of the standby OMUand then sets up a connection between them.

2. Perform a pre-upgrade to update OMU-related programs and data in the standbyworkspaces of the active and standby OMUs. The detailed procedure is as follows:

a. Perform a pre-upgrade.

b. The upgrade servers of the active and standby OMUs perform an environment check on their respective OMUs.

c. The upgrade servers of the active and standby OMUs update OMU-related programsin the standby workspaces of their respective OMUs and copy the related host

programs in the specified directory to the standby workspaces of their respectiveOMUs.

d. The upgrade server of the active OMU upgrades data in the standby workspaces of the active OMU. After the data is upgraded, the upgrade server synchronizes the datato the standby workspaces of the standby OMU.

e. Optional: If the upgrade version files include the cold patch package, the upgradeservers of the active and standby OMUs install the cold patch package to the standbyworkspaces of their respective OMUs.

3. Perform a version upgrade. Firstly load the programs and data files to host boards. Thenswitch over the active and standby workspaces of the active and standby OMUs. Then resetsthe host boards. After the resets, the host boards use the target version. The detailed

procedure is as follows:

a. Perform a version upgrade.

b. The upgrade server of the active OMU issues an SYN BRDAREA command to loadthe programs and data files in the standby workspace of the active OMU to host boards.

c. Switch over the active and standby workspaces of the active and standby OMUs. Theupgrade servers of the active and standby OMUs issue an SWP OMUAREAcommand to switch over the active and standby workspaces of their respective OMUs.After the switchovers, the active workspaces of the two OMUs use the target version.

d. Restart the host system. The upgrade server of the active OMU issues an RST BSCcommand to reset the standby host boards.

After the reset, the standby host boards load the local version that is consistent withthe OMU version, that is, the standby host boards start from the target version

programs and data files.

e. The upgrade server of the active OMU resets the active host boards after detectingthat the standby host boards have started.

After the active host boards reset, the original standby host boards become active, andthe original active host boards become standby and load the local version that is



30


39/89

consistent with the OMU version, that is, the original active host boards start from thetarget version programs and data files.

f. Optional: If the host boards have hot patch packages to upgrade, the upgrade server of the active OMU issues an INS PATCH command to decompress the hot patch

packages to the OMU and then install them.4. Perform service verification. If the service verification is successful, view the upgrade

report.

Version Rollback Process1. Start the upgrade tool by performing a, c, d and e in 1 of Version Upgrade Process.

2. Perform a version rollback. Firstly switch over the active and standby workspaces of theactive and standby OMUs. Then resets the host boards. After the resets, the host boards usethe pre-upgrade version. The detailed procedure is as follows:

a. Perform a version rollback.

b. The upgrade servers of the active and standby OMUs issue an SWP OMUAREAcommand to switch over the active and standby workspaces of their respective OMUs.After the switchovers, the active and standby workspaces of the two OMUs use the

pre-upgrade version.

c. Reset host boards. The upgrade server of the active OMU issues an RST BSCcommand to res et the host boards.

After the resets, the host boards load the local version that is consistent with the OMUversion, that is, the host boards start from the pre-upgrade programs and data files.

d. The upgrade server of the active OMU checks the status of host boards.

e. Optional: If the pre-upgrade version has hot patch packages to upgrade, the upgradeserver of the active OMU issues an INS PATCH command to decompress the hot patch packages to the OMU and then install them.

3. Perform service verification. If the service verification is successful, view the rollback report.

Cold Patch Upgrade Process

Figure 2-19 shows the process of a cold patch upgrade.



31


40/89

Figure 2-19 Cold patch upgrade process

1. Start the upgrade tool by performing 1 of Version Upgrade Process.

2. Perform a cold patch upgrade. Firstly update OMU-related programs and data in the activeworkspaces of the active and standby OMUs. Then load the programs and data files to host

boards. At last, resets the host boards. After the resets, the host boards use the target version.The detailed procedure is as follows:

a. Perform a cold patch upgrade.

b. The upgrade server of the active OMU performs a pre-upgrade check and backs upthe OMU software and host board software for the active workspaces of the OMU.



32


41/89

c. The upgrade servers of the active and standby OMUs upgrade OMU-related programsin the active workspaces of their respective OMUs and copy the related host programsin the specified directory to the active workspaces of the two OMUs.

d. The upgrade server of the active OMU issues a command to load the host programs

and data files in the active workspaces of the active OMU to the standby workspacesof host boards.

e. The upgrade server of the active OMU resets the standby host boards on which a cold patch upgrade is to be executed.

After the reset, the standby host boards load the local version that is consistent withthe OMU version, that is, the standby host boards start from the target version

programs and data files.

f. The upgrade server of the active OMU resets the active host boards on which a cold patch upgrade is to be executed after detecting that the standby host boards havestarted.

After the active host boards reset, the original standby host boards become active, andthe original active host boards become standby and load the local version that isconsistent with the OMU version, that is, the original active host boards start from thetarget version programs and data files.

g. Optional: If the host boards have hot patch packages to upgrade, the upgrade server of the active OMU issues an INS PATCH command to decompress the hot patch

packages to the OMU and then install them.

3. Perform service verification. If the service verification is successful, view the upgradereport.

Cold Patch Rollback Process1. Start the upgrade tool by performing a, c, d and e in 1 of Version Upgrade Process.

2. Perform a cold patch rollback. Firstly install pre-upgrade OMU programs and data in theactive workspaces of the active and standby OMUs. Then resets the host boards. After theresets, the host boards use the old version. The detailed procedure is as follows:

a. Perform a cold patch rollback.

b. The upgrade servers of the active and standby OMUs restore OMU software and host board software in the active workspaces of their respective OMUs, that is, the upgradeservers copy the pre-upgrade OMU software and host board software in the backup

files to the active workspaces of the two OMUs.c. The upgrade servers of the active and standby OMUs install the pre-upgrade OMU

software in the active workspaces of their respective OMUs and copy the pre-upgradehost programs in the backup files to the active workspaces of the two OMUs.

d. The upgrade server of the active OMU issues a command to load the data files in theactive workspaces of the active OMU to the standby workspaces of host boards.

e. The upgrade server of the active OMU resets the host boards on which cold patcheshave been installed. After the resets, the host boards switch over the active and standbyworkspaces. Then, the host boards load the version that is consistent with the OMUversion, that is, the host boards start from the pre-upgrade programs and data.

f. The upgrade server of the active OMU checks the status of host boards.



33


42/89

g. Optional: If the pre-upgrade version has hot patch packages to upgrade, the upgradeserver of the active OMU issues an INS PATCH command to decompress the hot

patch packages to the OMU and then install them.

3. Perform service verification. If the service verification is successful, view the rollback

report.

Hot Patch Upgrade ProcessFigure 2-20 shows the process of a hot patch upgrade.

Figure 2-20 Hot patch upgrade process

1. Start the upgrade too l by performing 1 of Version Upgrade Process.

2. Perform a hot patch upgrade. Firstly update OMU-related programs in the activeworkspaces of the active and standby OMUs. Then delete the source hot patch package for



34


43/89

host boards, and then installs the target hot patch package. The detailed procedure is asfollows:

a. Perform a hot patch upgrade.

b. The upgrade server of the active OMU performs a pre-upgrade check and backs upthe OMU software and host board software for the active workspace of the activeOMU.

c. The upgrade servers of the active and standby OMUs upgrade OMU-related programsin the active workspace of their respective OMUs and copy the related host programsin the specified directory to the active workspace of the two OMUs.

d. The upgrade server of the active OMU issues an RMV PATCH command to deletethe source hot patch package for host boards.

e. The upgrade server of the active OMU issues an INS PATCH command todecompress the target hot patch packages for host boards to the OMU and then installthem.

f. The upgrade server of the active OMU checks the hot patch No. and status of host boards.

3. Perform service verification. If the service verification is successful, view the upgradereport.

Hot Patch Rollback Process

1. Start the upgrade tool by performing a, c, d, and e in 1 of Version Upgrade Process.

2. Perform a hot patch rollback. Firstly install pre-upgrade OMU software in the activeworkspaces of the active and standby OMUs. Then deletes the hot patch package for host

boards. The detailed procedure is as follows:

a. Perform a hot patch rollback.

b. The upgrade servers of the active and standby OMUs restore OMU software and host board software in the active workspaces of their respective OMUs, that is, the upgradeservers copy the pre-upgrade OMU software and host board s oftware in the backupfiles to the active workspaces of the two OMUs.

c. The upgrade servers of the active and standby OMUs install pre-upgrade OMUsoftware in the active workspaces of their respective OMUs and copy the pre-upgradehost programs in the backup files to the active workspaces of the two OMUs.

d. The upgrade server of the active OMU issues an RMV PATCH command to deletethe hot patch package for host boards.

e. Optional: If the pre-upgrade version has hot patch packages to upgrade:

a. The upgrade server of the active OMU issues an INS PATCH command todecompress the pre-upgrade hot patch packages for host boards to the OMU andthen install them.

b. The upgrade server of the active OMU checks the hot patch No. and status of host boards.

3. Perform service verification. If the service verification is successful, view the rollback report.



35


44/89

3 Signal FlowAbout This Chap ter

The BSC690 0 signal flow consists of the user-plane signal flow, control-plane signaling flow,and O&M sig nal flow.

NOTE

See WCD MA RAN Controller Resource Sh aring Feature Parameter Description to get more information.

Definitionsl User plane

User plane refers to the set of BSC6900 logical function units used for processing servicedata, including voice data and packet data.

l Control plane

Control plane refers to the set of BSC6900 logical function units used for processing controlsignaling, including the call control signaling and the connection control signaling.

3.1 User-Plane Signal FlowThe user plane of the BSC6900 processes user-plane messages over each interface.

3.2 Control-Plane Signaling FlowThe control plane of the BSC6900 processes the control-plane messages over each interface.

3.3 O&M Signal FlowO&M signal flow refers to the messages transmitted between the BSC6900 and the LMT or U2000. The LMT or U2000 maintains and monitors the BSC6900 in real time through the O&Msignal flow.

BSC6900 UMTSTechnical Description 3 Signal Flow


36


45/89

3.1 User-Plane Signal Flow

The user plane of the BSC6900 processes user-plane messages over each interface.

3.1.1 UMTS Signal Flow Between Iub and Iu-CS/Iu-PSThe UMTS signal flow between Iub and Iu-CS/Iu-PS refers to the data transmitted between theBSC6900 and the MSC/SGSN.

The data flow between Iub and Iu-CS/Iu-PS is classified into the following types:l Intra-BSC6900 data flow between Iub and Iu-CS/Iu-PSl Inter-BSC6900 data flow between Iub and Iu-CS/Iu-PS

NOTE


Intra-BSC6900 Data Flow Between Iub and Iu-CS/Iu-PS

If the BSC6900 that receives the data from the Iub interface sends the data directly to the MSC/SGSN over the Iu-CS/Iu-PS interface, the data flow is called an intra-BSC6900 data flow

between Iub and Iu-CS/Iu-PS. Figure 3-1 shows the intra-BSC6900 data flow between Iub andIu-CS/Iu-PS.

Figure 3-1 Intra-BSC6900 data flow between Iub and Iu-CS/Iu-PS

NOTE

l The INT in the figure stands for the interface board. You can use different interface boards as required.

l All the communications between the boards in the same subrack and in different subracks are switched by the SCU boards.

l The boards shown in the figure are only examples.

The signal flow in the uplink is as follows:



37


46/89

1. The NodeB processes the data and then sends it to the Iub interface board of BSC6900 over the Iub interface.

2. The Iub interface board processes the data and sends it to the DPUb board in the samesubrack. See signal flow 1 in Figure 3-1 .

If the DPUb board that processes the data and the Iub interface board that receives the dataare installed in different subracks, the data is switched by the MPS. The MPS then sendsthe data to the target DPUb board. See signal flow 2 in Figure 3-1 .

3. The DPUb board processes the data according to the FP, MDC, MAC, RLC, and Iu UP/PDCP/GTP-U protocols, separates CS user-plane data from PS user-plane data, and thensends the data to the Iu-CS and Iu-PS interface boards, respectively.

4. The Iu-CS/Iu-PS interface board processes the data and then sends it to the MSC/SGSN.

The downlink signal flow is the reverse of the uplink signal flow.

Inter-BSC6900 Data Flow Between Iub and Iu-CS/Iu-PSIf the BSC6900 that receives the data from the Iub interface sends the data to the MSC/SGSNthrough another BSC6900, the data flow is called an inter-BSC6900 data flow between Iub andIu-CS/Iu-PS.

Figure 3-2 shows the data flow between BSC6900-1 and BSC6900-2.

Figure 3-2 Inter-BSC6900 data flow between Iub and Iu-CS/Iu-PS

NOTE


l All the communications between the boards in the same subrack and in different subracks are switched by the SCU boards.

The signal flow in the uplink is as follows:

1. The NodeB processes the data and then sends it to the Iub interface board of BSC6900-1over the Iub interface.

2. The Iub interface board and DPUb board of BSC6900-1 process the data and then send itto the Iur interface board of BSC6900-1.

NOTE

The DPUb board of BSC6900-1 processes the data according to only the FP and MDC protocols.

3. The Iur interface board of BSC6900-1 processes the data and then sends it to the Iur interface board of BSC6900-2 over the Iur interface between BSC6900-1 and BSC6900-2.



38


47/89

4. The Iur interface board of BSC6900-2 processes the data and then sends it to the DPUb board.

5. The DPUb board processes the data, separates CS user-plane data from PS user-plane data,and then sends the data to the Iu-CS and Iu-PS interface boards, respectively.

6. The Iu-CS/Iu-PS interface board processes the data and then sends it to the MSC/SGSN.

The downlink sign al f low is the reverse of the uplink signal flow.

3.1.2 CBC Signal FlowThe data from the Iu-BC interface to the Iub interface refers to the cell broadcast center (CBC)signal flow.

NOTE


Figure 3-3 shows the signal flow from the Iu-BC interface to the Iub interface.

Figure 3-3 Signal flow from Iu-BC to Iub

NOTE


The signal flow is as follows:

1. The CBC broadcasts data to the Iu-BC interface board of th

Documents

BSC6900 UMTS Technical Description(V900R017C10_01)(PDF)-En