Installation Manual-System Commissioning [ cBSC6600 ]

Chapter 1 Commissioning Preparations 1-1.......................................................

1.1 Required Tools 1-1.......................................................................................1.2 Hardware Preparation 1-1............................................................................1.3 Software Preparation 1-1..............................................................................1.4 Data Preparation 1-1....................................................................................1.5 IP Address Planning 1-2...............................................................................

1.5.1 Assignment principles of IP address in Small-CapacityConfiguration 1-2...........................................................................................1.5.2 Assignment principles of IP address in Large-CapacityConfiguration 1-4...........................................................................................

Chapter 2 Loading Operation 2-1.........................................................................

2.1 Basic Concept of Loading 2-1......................................................................2.1.1 Loading Mode 2-1................................................................................2.1.2 Loading Sequence and Path 2-2..........................................................2.1.3 Loading Files 2-3..................................................................................

2.2 Basic Loading Procedure 2-5.......................................................................2.3 Preparations before Loading 2-5..................................................................

2.3.1 Hardware 2-6.......................................................................................2.3.2 Software 2-6.........................................................................................2.3.3 Configuration 2-6..................................................................................

2.4 Loading Procedure 2-6.................................................................................2.5 Loading Checks 2-13......................................................................................

2.5.1 Checking Loading of CSWS 2-14..........................................................2.5.2 Checking Loading Effect of Service Subracks 2-15...............................

Chapter 3 Abis Interface Interconnection 3-1.....................................................

3.1 Interconnection Procedures 3-1...................................................................3.2 Preparing for Abis Interface Interconnection 3-1..........................................3.3 Checking Physical Connections 3-2.............................................................3.4 Checking Data Configuration 3-3.................................................................3.5 Checking E1 Status 3-4................................................................................

3.5.1 Querying E1 Status 3-4........................................................................3.5.2 Carrying out Loopback Tests from the DDF to the BSC 3-5................3.5.3 Carrying out Loopback Tests from the DDF to theTransmission Equipment 3-7........................................................................3.5.4 Checking Connections between the DDF and the BTS 3-8.................

3.6 Checking Link Status 3-8..............................................................................3.6.1 Checking IMA Group Status 3-8..........................................................

3.7 Checking BTS OML 3-9................................................................................3.8 Loading BTS Programs and Data Files 3-9..................................................

Chapter 4 A1/A2 Interface Interconnection 4-1...................................................

4.1 Basic Procedures of Interconnection 4-1......................................................4.2 Preparations before Interconnection 4-1......................................................4.3 Checking Physical Connections 4-2.............................................................4.4 Checking Data Configuration 4-3.................................................................4.5 Checking E1 Status 4-5................................................................................

4.5.1 Querying E1 Status 4-5........................................................................4.5.2 Carrying Out Loopback Tests from DDFs to BSCs 4-6........................

4.6 Checking Signaling Link Status 4-8..............................................................4.6.1 Querying MTP2 Link Status 4-8...........................................................4.6.2 Querying MTP3 Link Status 4-8...........................................................

4.7 Checking Trunk Circuit Status 4-9................................................................4.7.1 Querying A2 Circuit Status 4-9.............................................................4.7.2 Resetting A2 Circuits 4-10.....................................................................

Chapter 5 Service Commissioning 5-1................................................................

5.1 Service Commissioning Procedures 5-1......................................................5.2 Preparing for Service Commissioning 5-1....................................................5.3 Making Test Calls on a Specified A2 Circuit 5-1..........................................

5.3.1 Test Flowchart 5-1...............................................................................5.3.2 Test Procedure 5-2..............................................................................

5.4 Making Test Calls on Basic Services 5-4.....................................................5.5 Making Test Calls on Packet Data Service 5-4............................................5.6 Making Test Calls on Circuit Data Service 5-4.............................................

Chapter 6 Network Optimization 6-1....................................................................

6.1 Network Optimization Procedures 6-1..........................................................6.2 Preparations for Network Optimization 6-2...................................................

6.2.1 Arranging Personnel 6-2......................................................................6.2.2 Preparing Tools 6-2..............................................................................6.2.3 Preparing Documents 6-2....................................................................6.2.4 Checking Engineering Parameters 6-3................................................

6.3 Collection of Network Operation Data 6-3....................................................6.3.1 Collecting Traffic Measurement Data 6-3.............................................6.3.2 Collecting Drive Test Data 6-3.............................................................6.3.3 Collecting Alarm Data 6-4....................................................................6.3.4 Making Test Calls in Major Areas 6-4..................................................

6.4 Data Analysis and Performance Appraisal 6-4.............................................6.5 Suggestions and Measures on Network Optimization 6-4............................

6.5.1 Network Optimization Suggestions 6-5................................................6.5.2 Network Optimization Measures 6-5....................................................

6.6 Network Optimization Verification 6-6..........................................................6.7 Network Optimization Reports 6-6................................................................

Chapter 7 Preliminary Acceptance and Cutover 7-1..........................................

7.1 Preliminary Acceptance 7-1..........................................................................7.2 Service Cutover 7-1......................................................................................

Appendix A Upgrade Operation A-1.....................................................................

A.1 Software Upgrade Procedures A-1...............................................................A.2 Preparing for Software Upgrade A-1............................................................A.3 Switching from Formal BAM Server to the Staging One A-2........................A.4 Upgrading BAM Server Software on Staging BAM Server A-2....................

A.4.1 Disabling the Service and Programs of the Staging BAMServer A-2.....................................................................................................A.4.2 Uninstalling the Emergency Workstation Software A-5........................A.4.3 Installing the BAM Server Software on Staging BAM Server A-6........

A.5 Upgrading Host Software on Staging BAM Server A-6................................A.6 Upgrading BAM Server Software on Formal BAM Server A-7.....................

A.6.1 Making Preparations A-7......................................................................A.6.2 Disabling Services and Programs of the Formal BAM Server A-8.......A.6.3 Uninstalling the BAM Server Software A-9..........................................A.6.4 Installing the BAM Server Software on the Formal BAM Server A-9...

A.7 Switching from Staging BAM Server to Formal One A-9..............................A.7.1 Detaching the Database Files on the Staging BAM Server A-9...........A.7.2 Copying the Files and Programs on the Staging BAM Server A-10.......A.7.3 Attaching the Database Files on the Formal BAM Server A-11.............A.7.4 Replacing the Staging BAM Server with the Formal BAMServer A-12.....................................................................................................

A.8 Upgrading Emergency Workstation Software A-12........................................A.8.1 Uninstalling the BAM Server Software A-12..........................................A.8.2 Installing the Emergency Workstation Software A-12............................

A.9 Modifying Loading Control Mode on Formal BAM Server A-13......................

Appendix B Patch Operation B-1..........................................................................

B.1 Basic Concepts of Patch B-1........................................................................B.1.1 Functions B-1.......................................................................................B.1.2 Features B-1........................................................................................B.1.3 Status B-2............................................................................................

B.2 Operating Commands for a Patch B-2.........................................................B.2.1 Loading Board Patch Files B-2............................................................B.2.2 Transiting Board Patch Status B-3.......................................................B.2.3 Querying Information of Specified Board Patch Area B-3....................

B.2.4 Querying Information of Overall Patch Area B-4..................................B.2.5 Querying Board Patch Information B-4................................................

B.3 Preparations for Patch Operation B-4..........................................................B.3.1 Obtaining Correct Patch File B-5.........................................................B.3.2 Saving Patch File to Loading Directory B-5.........................................B.3.3 Selecting Correct Operation Time B-5.................................................

B.4 Patch Operation B-5.....................................................................................B.4.1 Querying Loading Control Mode B-5....................................................B.4.2 Loading Patch B-5................................................................................B.4.3 Checking Patch Status B-6..................................................................B.4.4 Activating Patches B-6.........................................................................B.4.5 Querying Patch Status B-6...................................................................B.4.6 Checking System Operation B-6..........................................................B.4.7 Confirming Patch Running Status B-6.................................................

HUAWEI

Airbridge cBSC6600 CDMA Base Station Controller Installation Manual - System Commissioning

V100R003

Airbridge cBSC6600 CDMA Base Station Controller

Installation Manual

Volume System Commissioning

Manual Version T2-030434-20040513-C-1.30

Product Version V100R003

BOM 31041234

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and service. Please feel free to contact our local office or company headquarters.

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd.,

Bantian, Longgang District, Shenzhen, P. R. China

Postal Code: 518129

Website: http://www.huawei.com

Email: [email protected]

Copyright © 2004 Huawei Technologies Co., Ltd.

All Rights Reserved

No part of this manual may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.

Trademarks

, HUAWEI, C&C08, EAST8000, HONET, , ViewPoint, INtess, ETS, DMC,

TELLIN, InfoLink, Netkey, Quidway, SYNLOCK, Radium, M900/M1800, TELESIGHT, Quidview, Musa, Airbridge, Tellwin, Inmedia, VRP, DOPRA, iTELLIN, HUAWEI OptiX, C&C08 iNET, NETENGINE, OptiX, iSite, U-SYS, iMUSE, OpenEye, Lansway, SmartAX, infoX, TopEng are trademarks of Huawei Technologies Co., Ltd.

All other trademarks mentioned in this manual are the property of their respective holders.

Notice

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

About This Manual

Release Notes

This manual applies to Airbridge cBSC6600 CDMA Base Station Controller V100R003.

Related Manuals

The related manuals are listed in the following table.

Manual Content

Airbridge cBSC6600 CDMA Base Station Controller Documentation Guide

Describes documentation package of the cBSC6600, including the organization, content, and methods of using it.

Airbridge cBSC6600 CDMA Base Station Controller Compliance and Safety Manual

Describes regulatory compliance statement and regulatory compliance information of the cBSC6600, and safety information needed to install and maintain the equipment.

Airbridge cBSC6600 CDMA Base Station Controller Technical Manual-System Description

Introduces the development of the CDMA network, and the product features, system configuration, system functions, related operation and maintenance, and technical specifications of the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Technical Manual-System Architecture

Describes the general architecture of the cBSC6600, including the subracks, clock system, O&M system, power supply system, and signal flows.

Airbridge cBSC6600 CDMA Base Station Controller Technical Manual-Interfaces and Protocols

Details the external interfaces, related protocols and standards, and typical service flows for the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Technical Manual-System Function

Introduces the supporting bands, networking capacity, radio channel management, power control, handoff decision, performance management, alarm management, dynamic configuration, and reliability design of the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Hardware Description Manual

Details the structures and working principles of the cables, boards, subracks, and cabinets of the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Installation Manual-Hardware Installation

Covers the hardware installation of the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Installation Manual-Software Installation

Describes the software installation of the cBSC6600.

Manual Content

Airbridge cBSC6600 CDMA Base Station Controller Installation Manual-System Commissioning

Describes the procedures in system commissioning of the cBSC6600 after hardware and software installation to ensure normal operation.

Airbridge cBSC6600 CDMA Base Station Controller Operation Manual-Data Configuration

Covers the data configuration of the cBSC6600 for large-capacity and small-capacity offices.

Airbridge cBSC6600 CDMA Base Station Controller Maintenance Manual-Routine Maintenance

Describes contents and methods of routine maintenance over the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Maintenance Manual-Troubleshooting

Details the troubleshooting for the cBSC6600.

Airbridge cBSC6600 CDMA Base Station Controller Maintenance Manual-Parts Replacement

Presents procedures and methods of replacing boards and components of the cBSC6600.

Organization

The Airbridge cBSC6600 CDMA Base Station Controller Installation Manual - System Commissioning details the commissioning procedures after BSC hardware and software installation to ensure normal operation of the system. It comprises nine parts:

Chapter 1 Commissioning Preparations: Briefs the preparations for system commissioning.

Chapter 2 Loading Operation: Describes the loading processes of programs and data files.

Chapter 3 Abis Interface Interconnection: Introduces the methods and procedures of checking and commissioning the connection channels between the BSC and BTS.

Chapter 4 A1/A2 Interface Interconnection: Introduces the methods and procedure of checking and commissioning the connection channels between the BSC and MSC.

Chapter 5 Service Commissioning: Introduces the methods and procedures of service commissioning.

Chapter 6 Network Optimization:Describes the methods and procedures of network optimization.

Chapter 7 Preliminary Acceptance and Cutover: Briefs the procedures and precautions of preliminary acceptance and service cutover.

Appendix A Upgrade Operation: Describes the methods and procedures of software upgrade.

Appendix B Patch Operation: Describes the methods and procedures of host software patch operation.

Intended Audience

The manual is intended for the following readers:

Installation engineers and technicians Operation and maintenance personnel

Conventions

The manual uses the following conventions:

I. General conventions

Convention Description

Arial Normal paragraphs are in Arial.

Arial Narrow Warnings, Cautions, Notes and Tips are in Arial Narrow.

Boldface Headings are in Boldface.

Courier New Terminal Display is in Courier New.

II. Command conventions


Boldface The keywords of a command line are in Boldface.

italic Command arguments are in italic.

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

{ x | y | ... } Alternative items are grouped in braces and separated by vertical bars. One is selected.

[ x | y | ... ] Optional alternative items are grouped in square brackets and separated by vertical bars. One or none is selected.

{ x | y | ... } * Alternative items are grouped in braces and separated by vertical bars. A minimum of one or a maximum of all can be selected.

[ x | y | ... ] * Optional alternative items are grouped in square brackets and separated by vertical bars. Many or none can be selected.

III. GUI conventions


< > Button names are inside angle brackets. For example, click the <OK> button.

[ ] Window names, menu items, data table and field names are inside square brackets. For example, pop up the [New User] window.

/ Multi-level menus are separated by forward slashes. For example, [File/Create/Folder].

IV. Keyboard operation

Format Description

<Key> Press the key with the key name inside angle brackets. For example, <Enter>, <Tab>, <Backspace>, or <A>.

<Key1+Key2> Press the keys concurrently. For example, <Ctrl+Alt+A> means the three keys should be pressed concurrently.

<Key1, Key2> Press the keys in turn. For example, <Alt, A> means the two keys should be pressed in turn.

V. Mouse operation

Action Description

Click Press the left button or right button quickly (left button by default).

Double Click Press the left button twice continuously and quickly.

Drag Press and hold the left button and drag it to a certain position.

VI. Symbols

Eye-catching symbols are also used in the manual to highlight the points worthy of special attention during the operation. They are defined as follows:

Caution: Means reader be extremely careful during the operation.

Note: Means a complementary description.

Environmental Protection

This product has been designed to comply with the requirements on environmental protection. For the proper storage, use and disposal of this product, national laws and regulations must be observed.

Installation Manual - System Commissioning Airbridge cBSC6600 CDMA Base Station Controller Table of Contents

i

Table of Contents

Chapter 1 Commissioning Preparations..................................................................................... 1-1 1.1 Required Tools................................................................................................................... 1-1 1.2 Hardware Preparation........................................................................................................ 1-1 1.3 Software Preparation ......................................................................................................... 1-1 1.4 Data Preparation................................................................................................................ 1-1 1.5 IP Address Planning .......................................................................................................... 1-2

1.5.1 Assignment principles of IP address in Small-Capacity Configuration ................... 1-2 1.5.2 Assignment principles of IP address in Large-Capacity Configuration ................... 1-4

Chapter 2 Loading Operation....................................................................................................... 2-1 2.1 Basic Concept of Loading.................................................................................................. 2-1

2.1.1 Loading Mode.......................................................................................................... 2-1 2.1.2 Loading Sequence and Path................................................................................... 2-2 2.1.3 Loading Files ........................................................................................................... 2-3

2.2 Basic Loading Procedure................................................................................................... 2-5 2.3 Preparations before Loading ............................................................................................. 2-5

2.3.1 Hardware................................................................................................................. 2-6 2.3.2 Software .................................................................................................................. 2-6 2.3.3 Configuration........................................................................................................... 2-6

2.4 Loading Procedure ............................................................................................................ 2-6 2.5 Loading Checks ............................................................................................................... 2-13

2.5.1 Checking Loading of CSWS.................................................................................. 2-14 2.5.2 Checking Loading Effect of Service Subracks ...................................................... 2-15

Chapter 3 Abis Interface Interconnection................................................................................... 3-1 3.1 Interconnection Procedures............................................................................................... 3-1 3.2 Preparing for Abis Interface Interconnection ..................................................................... 3-1 3.3 Checking Physical Connections ........................................................................................ 3-2 3.4 Checking Data Configuration............................................................................................. 3-3 3.5 Checking E1 Status ........................................................................................................... 3-4

3.5.1 Querying E1 Status ................................................................................................. 3-4 3.5.2 Carrying out Loopback Tests from the DDF to the BSC......................................... 3-5 3.5.3 Carrying out Loopback Tests from the DDF to the Transmission Equipment ........ 3-7 3.5.4 Checking Connections between the DDF and the BTS.......................................... 3-8

3.6 Checking Link Status ......................................................................................................... 3-8 3.6.1 Checking IMA Group Status.................................................................................... 3-8

3.7 Checking BTS OML ........................................................................................................... 3-9 3.8 Loading BTS Programs and Data Files ............................................................................. 3-9


ii

Chapter 4 A1/A2 Interface Interconnection ................................................................................ 4-1 4.1 Basic Procedures of Interconnection................................................................................. 4-1 4.2 Preparations before Interconnection.................................................................................. 4-1 4.3 Checking Physical Connections ........................................................................................ 4-2 4.4 Checking Data Configuration............................................................................................. 4-3 4.5 Checking E1 Status ........................................................................................................... 4-5

4.5.1 Querying E1 Status ................................................................................................. 4-5 4.5.2 Carrying Out Loopback Tests from DDFs to BSCs................................................. 4-6

4.6 Checking Signaling Link Status ......................................................................................... 4-8 4.6.1 Querying MTP2 Link Status .................................................................................... 4-8 4.6.2 Querying MTP3 Link Status .................................................................................... 4-8

4.7 Checking Trunk Circuit Status ........................................................................................... 4-9 4.7.1 Querying A2 Circuit Status...................................................................................... 4-9 4.7.2 Resetting A2 Circuits............................................................................................. 4-10

Chapter 5 Service Commissioning.............................................................................................. 5-1 5.1 Service Commissioning Procedures.................................................................................. 5-1 5.2 Preparing for Service Commissioning ............................................................................... 5-1 5.3 Making Test Calls on a Specified A2 Circuit...................................................................... 5-1

5.3.1 Test Flowchart......................................................................................................... 5-1 5.3.2 Test Procedure........................................................................................................ 5-2

5.4 Making Test Calls on Basic Services................................................................................. 5-4 5.5 Making Test Calls on Packet Data Service ....................................................................... 5-4 5.6 Making Test Calls on Circuit Data Service ........................................................................ 5-4

Chapter 6 Network Optimization.................................................................................................. 6-1 6.1 Network Optimization Procedures ..................................................................................... 6-1 6.2 Preparations for Network Optimization.............................................................................. 6-2

6.2.1 Arranging Personnel ............................................................................................... 6-2 6.2.2 Preparing Tools ....................................................................................................... 6-2 6.2.3 Preparing Documents ............................................................................................. 6-2 6.2.4 Checking Engineering Parameters ......................................................................... 6-3

6.3 Collection of Network Operation Data ............................................................................... 6-3 6.3.1 Collecting Traffic Measurement Data...................................................................... 6-3 6.3.2 Collecting Drive Test Data ...................................................................................... 6-3 6.3.3 Collecting Alarm Data ............................................................................................. 6-4 6.3.4 Making Test Calls in Major Areas ........................................................................... 6-4

6.4 Data Analysis and Performance Appraisal ........................................................................ 6-4 6.5 Suggestions and Measures on Network Optimization....................................................... 6-4

6.5.1 Network Optimization Suggestions ......................................................................... 6-5 6.5.2 Network Optimization Measures ............................................................................. 6-5

6.6 Network Optimization Verification...................................................................................... 6-6 6.7 Network Optimization Reports ........................................................................................... 6-6


iii

Chapter 7 Preliminary Acceptance and Cutover........................................................................ 7-1 7.1 Preliminary Acceptance ..................................................................................................... 7-1 7.2 Service Cutover ................................................................................................................. 7-1

Appendix A Upgrade Operation...................................................................................................A-1 A.1 Software Upgrade Procedures ..........................................................................................A-1 A.2 Preparing for Software Upgrade........................................................................................A-1 A.3 Switching from Formal BAM Server to the Staging One...................................................A-2 A.4 Upgrading BAM Server Software on Staging BAM Server ...............................................A-2

A.4.1 Disabling the Service and Programs of the Staging BAM Server ..........................A-2 A.4.2 Uninstalling the Emergency Workstation Software.................................................A-5 A.4.3 Installing the BAM Server Software on Staging BAM Server .................................A-6

A.5 Upgrading Host Software on Staging BAM Server ...........................................................A-6 A.6 Upgrading BAM Server Software on Formal BAM Server ................................................A-7

A.6.1 Making Preparations...............................................................................................A-7 A.6.2 Disabling Services and Programs of the Formal BAM Server................................A-8 A.6.3 Uninstalling the BAM Server Software ...................................................................A-9 A.6.4 Installing the BAM Server Software on the Formal BAM Server ............................A-9

A.7 Switching from Staging BAM Server to Formal One.........................................................A-9 A.7.1 Detaching the Database Files on the Staging BAM Server....................................A-9 A.7.2 Copying the Files and Programs on the Staging BAM Server .............................A-10 A.7.3 Attaching the Database Files on the Formal BAM Server....................................A-11 A.7.4 Replacing the Staging BAM Server with the Formal BAM Server........................A-12

A.8 Upgrading Emergency Workstation Software .................................................................A-12 A.8.1 Uninstalling the BAM Server Software .................................................................A-12 A.8.2 Installing the Emergency Workstation Software ...................................................A-12

A.9 Modifying Loading Control Mode on Formal BAM Server...............................................A-13

Appendix B Patch Operation........................................................................................................B-1 B.1 Basic Concepts of Patch ...................................................................................................B-1

B.1.1 Functions ................................................................................................................B-1 B.1.2 Features..................................................................................................................B-1 B.1.3 Status......................................................................................................................B-2

B.2 Operating Commands for a Patch.....................................................................................B-2 B.2.1 Loading Board Patch Files......................................................................................B-2 B.2.2 Transiting Board Patch Status ................................................................................B-3 B.2.3 Querying Information of Specified Board Patch Area.............................................B-3 B.2.4 Querying Information of Overall Patch Area...........................................................B-4 B.2.5 Querying Board Patch Information .........................................................................B-4

B.3 Preparations for Patch Operation......................................................................................B-4 B.3.1 Obtaining Correct Patch File...................................................................................B-5 B.3.2 Saving Patch File to Loading Directory ..................................................................B-5 B.3.3 Selecting Correct Operation Time ..........................................................................B-5

B.4 Patch Operation.................................................................................................................B-5


iv

B.4.1 Querying Loading Control Mode.............................................................................B-5 B.4.2 Loading Patch.........................................................................................................B-5 B.4.3 Checking Patch Status ...........................................................................................B-6 B.4.4 Activating Patches ..................................................................................................B-6 B.4.5 Querying Patch Status............................................................................................B-6 B.4.6 Checking System Operation ...................................................................................B-6 B.4.7 Confirming Patch Running Status...........................................................................B-6

Installation Manual - System Commissioning Airbridge cBSC6600 CDMA Base Station Controller Chapter 1 Commissioning Preparations

1-1

Chapter 1 Commissioning Preparations

This chapter describes preparations before system commissioning, including required personnel, tools, hardware, software, data, and IP address planning.

1.1 Required Tools Tools required for commissioning include a laptop, commissioning serial port cables, and drive test equipment.

A signaling analyzer is required depending on site-specific requirement.

1.2 Hardware Preparation The BSC hardware installation and installation checks are completed before commissioning. For details, see Airbridge cBSC6600 CDMA Base Station Controller Installation Manual-Hardware Installation. For installation checks, you should focus on the connections of trunk cables, network cables, and optical fibers.

You should also check DIP switch settings of subracks, boards, fan box control board, and environment and power monitoring boards. For details, see Airbridge cBSC6600 CDMA Base Station Controller Hardware Description Manual.

1.3 Software Preparation The BSC software installation and installation checks are completed before commissioning. For details, see Airbridge cBSC6600 CDMA Base Station Controller Installation Manual-Software Installation.

You should also check that loading program is copied to the directory D:\cdma2000\LoadDATA.

1.4 Data Preparation Make sure that you have obtained related data files.

Before commissioning, collect and record BSC information listed in the following tables.

Table 1-1 Network information table

Local office name

Customer name SID MSC ID NID MCC MNC


1-2

Table 1-2 Atrribute table of each module

Module No.

Signling point

code of the

module

Length of

signaling point code

Support of SCCP

management

A interface version

Um interface version

Band class

Channel No.

Network indicator

Link set

mask

0

1

…

Table 1-3 Information table of trunk circuit

Module No. CAIE/CSTU slot No. Number of initial E1 Initial CIC Number of batch

added E1s Availability of

timeslot 16

0

1

…

Table 1-4 Informatin table of DSP

DSP name DPC Network indicator Length of DPC

Table 1-5 Information table of signaling link

Module No. CAIE/CSTU slot No. E1 No. SLC SLC sending Signaling timeslot

0

1

…

1.5 IP Address Planning The IP address planning of BSC system is complicated. Therefore, you must have a clear idea of assignment principles and planning of IP addresses.

1.5.1 Assignment principles of IP address in Small-Capacity Configuration

The following are the assignment principles in the small-capacity configuration.


1-3

I. BTS operation and maintenance path

Figure 1-1 shows BTS operation and maintenance path.

BAM WSCMUX

10.12.3.f

129.m.10.n

129.m.10.N

10.12.3.128

BSC

BTS

Figure 1-1 BTS operation and maintenance path

IP addresses of various network segments are assigned as follows:

1) IP address between the BAM and workstation.

The operator determines the IP address between BAM and workstation, which cannot be within the 10.12.3.0/24 network segment.

2) IP address between the BAM and the CMUX of CIPS

The IP address between the BAM and CMUX of CIPS is within 10.12.3.0/24 network segment.

Set the IP address of the BAM to 10.12.3.128. Set the IP address of the active CMUX to 10.12.3.f and standby CMUX to

10.12.3.128+f. “f” is the number of the CIPS where the CMUX is located. 3) IP address between the CMUX of CIPS and the BTS.

The IP address between the CMUX of CIPS and BTS is within the 129.m.10.0/16 network segment.

Set the IP address of CMUX to 129.m.10.n. “m” starts from 8 and increases sequentially along with the change of the CIPS number. The range of “n” is 1 to 3.

Set the IP address of BTS to 129.m.10.N. “m” is the same as that in the IP address (129.m.10.n) of CMUX in the corresponding CIPS. “N” starts from 4 and increases sequentially along with the change of BTS number.

II. BTS signaling path

Figure 1-2 shows the BTS signaling path.


1-4

CSPU

80.m.130.0

80.m.130.n

BSC

BTS

Figure 1-2 BTS signaling path

The signaling IP address between CSPU of CIPS and BTS is within the 80.m.0.0/14 network segment.

Set the IP address of CSPU to 80.m.130.0. Here, m = f × 4 + 1 and “f” is the number of the CIPS where the CSPU is located.

Set the IP address of BTS to 80.m.130.n. Here, m = f × 4 + 1 and “f” is the number of the CIPS where the CSPU is located. “n” starts from 116 and increases sequentially along with the change of BTS number.

III. Board communication path

IP address for the operation and maintenance and internal communication of a board is within the 80.4×N.0.0/14 network segment. “N” is the number of the subrack where the board is located.

The following table lists the allocation of address bits and corresponding implication.

Table 1-6 Implication of board IP address

Address bit 0 – 7 8 – 13 14 – 18 19 – 23 24 – 26 27 – 31

Implication 80 (permanent) Subrack Slot Board type Subsystem

No. CPU No. of subsystem

IV. IP address of BSC

Each BSC is identified through its IP address in the same MSC. The MSC assigns the IP addresses uniformly for inter-BSC handoffs.

1.5.2 Assignment principles of IP address in Large-Capacity Configuration

The following are the assignment principles in the large-capacity configuration.

I. BTS operation and maintenance path

Figure 1-3 shows the BTS operation and maintenance path.


1-5

BAM WSCMPU

10.12.3.64

192.1.1.254

CMUX

192.1.1.f

129.m.10.n

129.m.10.N

10.12.3.128

BSC

BTS

Figure 1-3 BTS operation and maintenance path

IP addresses of various network segments are assigned as follows:

IP address between the BAM and workstation.

The operator determines the IP address between the BAM and the workstation, which cannot be within the 10.12.3.0/24 network segment.

1) IP address between BAM and CMPU of CSWS.

The IP address between BAM and CMPU of CSWS is within the10.12.3.0/24 network segment.

Set the IP address of BAM to 10.12.3.128. Set the IP address of CMPU to 10.12.3.64.

2) IP address between CMPU of CSWS and CMUX of CIPS/CBMS.

The IP address between CMPU of CSWS and CMUX of CIPS/CBMS is within the 192.1.1.0/24 network segment.

Set the IP address of CMPU to 192.1.1.254. Set the IP address of CMUX to 192.1.1.f (IP address of CMUX optical

interface). “f” is the number of the CIPS/CBMS where the CMUX is located. 3) IP address between CMUX of CIPS/CBMS and BTS.

The IP address between CMUX of CIPS/CBMS and BTS is within the 129.m.10.0/16 network segment.

Set the IP address of CMUX to 129.m.10.n with “m” starting from 8 and increasing sequentially along with the change of the CIPS/CBMS number. The range of “n” is 1 to 3.

Set the IP address of BTS to 129.m.10.N. “m” is the same as that in the IP address (129.m.10.n) of CMUX in the corresponding CIPS/CBMS. “N” starts from 4 and increases sequentially along with the change of BTS number.


1-6

II. BTS signaling path

Figure 1-4 shows the BTS signaling path.

CSPU

80.m.130.0

80.m.130.n

BSC

BTS

Figure 1-4 BTS signaling path

The signalig IP address between CSPU of CIPS/CBMS and BTS is within the 80.m.130.0/14 network segment.

Set the IP address of CSPU to 80.m.130.0. Here, m = f × 4 + 1 and “f” is the number of the CIPS/CBMS where the CSPU is located.

Set the IP address of BTS to 80.m.130.n. Here, m = f × 4 + 1 and “f” is the number of the CIPS/CBMS where the CSPU is located. “n” starts from 116 and increases sequentially along with the change of BTS number.

III. Board communication path

The IP address between CMUX and other boards that in the same subrack is within the 80.4×N.0.0/14 network segment.

The following table lists the allocation of address bits and corresponding implication.

Table 1-7 Implication of board IP address

Address bit 0 – 7 8 – 13 14 – 18 19 – 23 24 – 26 27 – 31

Implication 80 (permanent) Subrack Slot Board type Subsystem

No. CPU No. of subsystem

IV. IP address of BSC

Each BSC is identified through its IP address in the same MSC. The MSC assigns the IP addresses uniformly for the inter-BSC handoffs.

Installation Manual - System Commissioning Airbridge cBSC6600 CDMA Base Station Controller Chapter 2 Loading Operation

2-1

Chapter 2 Loading Operation

This chapter describes loading of programs and data files. For loading of patch files, see Appendix B Patch Operation.

2.1 Basic Concept of Loading The following describes some basic concepts:

Loading means to load the programs, data files, and patch files from the loading directory of BAM server to the BSC. After loading, BSC software collaborates with board software to manage hardware resources and provide functions such as signaling processing, radio resource management, and interface management to ensure normal service provision.

Program refers to the program file of a board, and data file refers to the file generated by formatting data in service tables of BAM server database.

2.1.1 Loading Mode

I. Loading mode of CSWS

The small-capacity configuration scheme does not involve loading mode of CDMA Switch Subrack (CSWS).

The loading mode of CSWS is generally set before delivery. It is unnecessary to set the loading mode on site. For CSWS, the loading mode of board program files is different from that of data files. The following respectively describes the two loading modes:

Loading mode of program files 1) Execute the command LOD SWCMPUHD to load board program files from

BAM to CMPU hard disk. And then execute the command LOD SWBRD to load the program files to the Flash Memory of each board. This operation is generally completed before delivery.

2) Reset boards. The system will check whether the program files in the Flash Memory and those in the CMPU hard disk are consistent. If the program files are identical in version, the system will load program files from Flash Memory; otherwise it will load program files from the CMPU hard disk, but not write the Flash Memory.

Loading mode of data files 1) Power on a board (for the first time). The system will load data files of the

CSWS from the BAM to the CMPU hard disk. 2) Reset the board. The system will load data files of the CSWS to the CMPU

hard disk again.


2-2

II. Loading mode of service subracks

You can change the loading mode of a service subrack using the command MOD LODCM. The loading control mode includes:

Load from BAM and Not Write to Flash Load from BAM and Write to Flash Load from FLASH

Set the loading mode of service subracks as follows:

1) Before power-on, you must set the loading mode of board program files and data files to "Load from BAM and Write FLASH".

2) After the BSC is powered on and successfully loaded, set the loading mode of board program files to "Load from FLASH" and maintain the loading mode of data files as "Load from BAM and Write FLASH".

2.1.2 Loading Sequence and Path

I. Small-capacity configuration scheme

GCKP

The programs and data files of the GCKP are directly loaded from the BAM.

The loading path is:

BAM → GCKP

The BAM connects the GCKP through a 10M Ethernet cable.

CMUX

The programs and data files of the CMUX are directly loaded from the BAM.


BAM → CMUX

The BAM connects the CMUX through a 10M Ethernet cable.

Other boards

The programs and data files of other boards must be loaded from the BAM through the CMUX in the same subrack. Upon executing the command FMT, the system first loads programs and data files on the CMUX, and then other boards according to the sequence of their loading requests.


BAM → CMUX → Other boards

The BAM connects to the CMUX through a 10M Ethernet cable. The CMUX connects to other boards in the local subrack through the backplane.

II. Large-capacity configuration scheme

GCKP


2-3

The programs and data files of the GCKP are directly loaded from the BAM.


BAM → GCKP

The BAM connects to the GCKP through a 10M Ethernet cable.

Boards in service subracks

The programs of the boards in service subracks are loaded before delivery. You only need to load data files for these boards on site.


BAM → CSWS

The BAM connects to the CSWS through a 10M Ethernet cable.

Other boards

The programs and data files of other boards are loaded from the BAM through the CMUXs in the CSWS and service subracks. Upon executing the command FMT, the system first loads programs and data files on the boards in the CSWS and the CMUX in service subracks, and then other boards according to the sequence of their loading requests.


BAM → CSWS → CMUX → Other boards

The BAM connects to the CSWS through a 10M Ethernet cable. The CSWS connects the CMUX through an optical fiber. The CMUX connects to other boards in the same subrack through the backplane.

2.1.3 Loading Files

The loading file directory of BAM server stores the board programs and data files of the BSC.

I. Loading files of the CSWS

Table 2-1 lists the loading files of the CSWS are stored in "D:\cdma2000\LoadDATA", and data files in D:\cdma2000\LoadDATA\config.

Table 2-1 List of loading files of the CSWS

File Description

MPUA.vfs Program file of CMPU (version A)

MPUAMBT.vfs Program file of CMPU (version A)

MPUASBT.abs Program file of CMPU (version A)

MPUB.vfs Program file of CMPU (version B)

MPUBMBT.vfs Program file of CMPU (version B)


2-4

File Description

MPUBSBT.abs Program file of CMPU (version B)

NETA.vfs Program file of CNET (version A)

NETAMBT.vfs Program file of CNET (version A)

NETASBT.vfs Program file of CNET (version A)

NETB.vfs Program file of CNET (version B)

NETBMBT.vfs Program file of CNET (version B)

NETBSBT.abs Program file of CNET (version B)

LPUA.vfs Program file of CLPU (version A)

LPUAMBT.vfs Program file of CLPU (version A)

LPUASBT.abs Program file of CLPU (version A)

LPUBGFI.vfs Program file of CLPU (version B)

LPUBMBT.vfs Program file of CLPU (version B)

LPUBSBT.abs Program file of CLPU (version B)

CLKC_log.vfs Program file of CLKC

BNET.dat Data files of the CSWS

You can format data in the database service table to create data file BNET.dat for the CSWS.

II. Loading files of service subracks

Table 2-2 lists the loading files of service subracks. The files are stored in "D:\cdma2000\LoadDATA".

Table 2-2 List of loading files of service subracks

File Description

I00AIE0.bin Program file of CAIE

I00BIE0.bin Program file of CBIE

I00BPU0.bin Program file of CBPU

I00EVC0.bin Program file of CEVC

I00FMR0.bin Program file of CRMR

I00FMR0.dsp Program file of CRMV

I00FMR0.dsp(norfn) Program file of CFMR (without rfn)

I00FMR0.dsp(rfn) Program file of CFMR (with rfn)

I00HAC0.bin Program file of CHAC


2-5

File Description

I00IWF0.bin Program file of CIWF

I00LAP0.bin Program file of CLAP

I00MUX0.bin(8750+UTCP) Program file of CMUX (Used by 8750 to add UTCP clock source)

I00MUX0.bin(8850+UTCP) Program file of CMUX (Used by 8850 to add UTCP clock source)

I00MUX0.bin(GCKP) Program file of CMUX (GCKP clock source)

I00PCU0.bin Program file of CPCU

I00PPU0.bin Program file of CPPU

I00RMU0.bin Program file of CRMU

I00SPU0.bin Program file of CSPU

I00STU0.bin Program file of CSTU

I00XIE0.bin Program file of CXIE

QC1GCKP3.bin Program file of GCKP

I00EVC0.dsp Program file of CEVC



*.dat Data files of service subracks

You can format the data in the database service table to create data files for the CMUX, CRMU, CSPU, and CPCU.

The naming rule of a data file is: "Subrack type (one letter)" + "Subrack No. (two digits)" + "Board type (three letters)" + "Subsystem No. (one digit)" + ".dat".

For example, the data file of the CMUX in Subrack 2 is I02MUX0.dat.

2.2 Basic Loading Procedure The loading (upon power-on) includes the following procedures:

1) Prepare for the loading. 2) Process script data files in batch, and then power on the system to load programs

and data files. 3) Check system running status and the loading result.

2.3 Preparations before Loading Before powering on the system, make sure the environment described in the following sections are ready.


2-6

2.3.1 Hardware

Before powering on the BSC system, you must check the hardware to ensure that:

The hardware installation, especially the physical connection of each loading path, is correct. For details, see Airbridge cBSC6600 CDMA Base Station Controller Installation Manual – Hardware Installation.

The DIP switches are correctly set on subracks and boards inside subracks, control units of fan boxes, and power and environment monitoring boards. For details, see Airbridge cBSC6600 CDMA Base Station Controller Hardware Description Manual.

The power switch of the power distribution box (PDB) on top of the cabinet is in OFF state.

2.3.2 Software

Before powering on the BSC, you must check the software to ensure that:

The software of BAM server is correctly installed. For details, see Airbridge cBSC6600 CDMA Base Station Controller Installation Manual – Software Installation.

Correct loading programs are loaded to the directory D:\ Airbridge\LoadDATA. The software version matches the hardware version.

2.3.3 Configuration

For a BSC of small-capacity configuration, there is no need to check basic parameters of the CSWS. For a BSC of large-capacity configuration, the basic parameters of the CSWS are configured before delivery. These parameters include:

Lan2 IP and Lan2 subnetMask The Connected BAM IP address Connecting with BAM or not Resume config file by BAM.

Before powering on the system, you must check that the above parameters are correctly set.

2.4 Loading Procedure

I. Open the [Loading] window

Start the Service Maintenance System and open the [Loading] window.

II. Set loading control mode

Execute the command LST LODCM to check the loading control mode.


2-7

If the loading control mode of BSC programs, data files, and patch files is "Load from BAM and Write to FLASH", it indicates that the loading control mode is correct. Otherwise you must execute MOD LODCM to modify the loading control mode.

Note:

The loading control mode affects the loaindg mode of the boards in service subracks. But it does not affect the loading mode of the boards in the CSWS. The program files of boards in the CSWS are loaded from the Flash Memory, and the data files are loaded from the BAM.

III. Configure routing data

To configure routing data on the BAM, proceed as follows:

1) Select [Start/Run]. 2) Enter "CMD" in the [Run] dialog box, and then click <Yes>. 3) Configure routing data in the DOS window displayed.

For specific configuration methods, see Airbridge cBSC6600 CDMA Base Station Controller Operation Manual – Data Configuration.

IV. Enter offline mode

Execute LOF to enter the offline status.

This prevents the operation on the data files of the BAM server from affecting the BSC.

V. Check script data file

Check the script data files and modify the files as needed.

Generally, the script data files of both service subracks and the CSWS are configured before delivery. The script files are in .txt format.

Note:

In small-capacity configuration, there is no script data file of the CSWS.

Check that the script data file of service subracks starts with the following data:

RMV BSCTBL:CONFIRM=Y;

CLR SYSDATA:CONFIRM=Y;

MOD DYNCFGSWT: DYNCFGSWT=NO;

Check that the script data file of service subracks ends with the following data:


2-8

CLR SYSDATA:CONFIRM=Y;

RUN: SCRIPT="delete from tbl_SubString";

MOD DYNCFGSWT: DYNCFGSWT=YES;


FMT: FMTTYPE=FMTALL;


Check that the script data file of the CSWS starts with the following data:

LOF:;

RMV SWTBL:CONFIRM=Y;

Check that the script data file of the CSWS ends with the following data:

FMT SWDATA:;

LON:;

Check that the commands and parameters in the script data files are correct and satisfy the actual requirements.

For specific data configuration method, see Airbridge cBSC6600 CDMA Base Station Controller Operation Manual – Data Configuration.

VI. Process script data files in batch

Note:

In large-capacity configuration, you must first process script data files of service subracks and then those of the CSWS in batch. In small-capacity configuration, you only need to process script data files of service subracks in batch.

1) Select batch operation command

Select [System/Execute Batch File] in the Service Maintenance System, as shown Figure 2-1.


2-9

Figure 2-1 Select the batch operation command

2) Select the path of the script data files

Select the path of the script data files in the [Execute Batch File] dialog box, as shown in Figure 2-2.

Figure 2-2 Execute Batch Files dialog box

Click <OK>.

3) Execute script data files in batch

Click <Batch Run> in the [Debugging] window displayed, as shown in Figure 2-3.


2-10

Figure 2-3 [Debugging] window

The system executes all commands automatically.

If any error occurs during the execution, remove faults according to the error message.

VII. Check loading files

Check that the programs and data files under D:\Airbridge\LoadDATA are correct and complete.

VIII. Enter online mode

Execute LON to enter the online status.

This ensures that the data files on the BAM server are set to the BSC.

IX. Switch on the power supply

Wear antistatic wrist strap and switch on the PDB on top of each cabinet.

The system starts loading board programs and data files.

Caution:

Do not execute data configuration command during the board loading process.


2-11

X. Observe the loading information

During loading, you can see the following information in the [Loading] window of the Service Maintenance System:

+++ HW-Airbridge 2004-03-19 18:21:32

LOADER 0098974438

0%

Frame No. = 2 Active MUX Board

File Name = I00MUX0.BIN

Total Used Time = 00:00:00 Start Time = 2004-03-19 18:21:32

--- END

+++ HW-Airbridge 2004-03-19 18:21:33

LOADER 0098974438

10%




--- END

+++ HW-Airbridge 2004-03-19 18:21:34

LOADER 0098974438

20%




--- END

+++ HW-Airbridge 2004-03-19 18:21:35

LOADER 0098974438

30%




--- END

+++ HW-Airbridge 2004-03-19 18:21:36

LOADER 0098974438

40%




--- END

+++ HW-Airbridge 2004-03-19 18:21:38

LOADER 0098974438

50%



2-12



--- END

+++ HW-Airbridge 2004-03-19 18:21:39

LOADER 0098974438

60%




--- END

+++ HW-Airbridge 2004-03-19 18:21:40

LOADER 0098974438

70%




--- END

+++ HW-Airbridge 2004-03-19 18:21:41

LOADER 0098974438

80%




--- END

+++ HW-Airbridge 2004-03-19 18:21:42

LOADER 0098974438

90%




--- END

+++ HW-Airbridge 2004-03-19 18:21:43

LOADER 0098974438

100%




--- END

+++ HW-Airbridge 2004-03-19 18:21:43

LOADER 0098974438

Load succeeded




2-13


--- END

If an error occurs during loading of board programs and data files, reset the board.

After the loading succeeds, query the operational status of a board. You can also query the Equipment Panel of the Service Maintenance System to check whether the board is normal. The Equipment Panel is shown as Figure 2-4.

Figure 2-4 Equipment panel

XI. Modify loading control mode

Execute MOD LODCM to ensure that the loading control mode of all host programs and DSP programs is "Load from FLASH".

2.5 Loading Checks After the loading, check the loading data and board status to verify the loading effect.

In large-capacity configuration, you need to verify the loading CSWS and service subracks. In small-capacity configuration, you only need to verify the loading of service subracks.


2-14

2.5.1 Checking Loading of CSWS

I. Query statuses of the boards in the CSWS

Command

DSP SWBRDINFO

Function

Checks the types and statuses of the boards in the CSWS, and the types of the backplanes and sub-boards.

Example

The following shows the queried statuses of all boards in the CSWS.

+++ HW-Airbridge 2004-04-06 09:59:39

O&M #47916

%%DSP SWBRDINFO:;%%

RETCODE = 0 Execution succeeded

Query Result

------------

Slot No. = 0

Board Type = CMPU

Board Status = Normal

Mother Board Type = MPUB

Type of Subboard 1 = None




Slot No. = 3

Board Type = CLPC


Mother Board Type = LPUC

Type of Subboard 1 = ATM155




Slot No. = 6

Board Type = CLPC


Mother Board Type = LPUB




2-15



Slot No. = 8

Board Type = CNET


Mother Board Type = NETB





( Records = 4 )

--- END

If the status of each board is normal, this indicates that the loading is successful. Otherwise you must re-load board programs and data files.

2.5.2 Checking Loading Effect of Service Subracks

I. Cyclic redundancy check (CRC)

Command

STR CRC

Function

Checks whether the data of the BAM server and the host is consistent.

Example

The following shows the CRC result of the No.40 table (1X Auxiliary Pilot table) of the CSPU in Subrack 2.

+++ HW-Airbridge 2004-04-06 10:02:18

O&M #47927

%%STR CRC: FN=2, BTP=CSPU, SPUTBL=TBL40;%%


CRC result

----------

Table ID Table description CRC result

40 1X Auxiliary Pilot Table Identical


2-16

(Total result = 1)

--- END

If the CRC results are inconsistent, reset the board and re-load corresponding board program and data files.

II. Query unset data

Command

LST USD

Function

In offline setting, or when the system fails to set the configured data to the BSC, the unset data is saved in the System Data table. You can use this command to query the data unset to the BSC.

Example

The following shows the unset data.

+++ HW-Airbridge 2004-04-06 10:04:16

O&M

%%LST USD:;%%


Setting data

------------

No result!

(Total result = 0)

--- END

If you find any unset data, execute SND USD to set the data to the BSC.

III. Query board information

Command

DSP BRDINFO

Function

Checks board status and version information.

Example

The following shows the information of the CMUX in Slot 8, Subrack 2.

+++ HW-Airbridge 2004-04-06 10:08:40

O&M #47960

%%DSP BRDINFO: FN=2, SN=8;%%


2-17


Query Result

------------

Frame No. = 2

Slot No. = 8

Board Type = CMUX

Operational Status = Available

Administrative Status = Enable

Active/Standby Status = Master

ATM Bus Interface = 7

SubSysSoftwareVer =

MVBSC6600-MUXV100R003

BIOSSoftwareVer =

SV0010301103(20030325B)

PCBVer = REV0

CPLDHardwareLogicVer = LV00003

FPGAHardwareLogicVer = FV03005

ATMBusBackplaneVer = KV01100

--- END

Check whether the board status is normal and whether the version is correct. If there is anything wrong, reset the board and re-load board programs and data files.

Installation Manual - System Commissioning Airbridge cBSC6600 CDMA Base Station Controller Chapter 3 Abis Interface Interconnection

3-1

Chapter 3 Abis Interface Interconnection

Abis interface interconnection means performing checks and commissioning on the connection channels between the BSC and BTS to ensure their normal connection.

The BSC and BTS involved in the Abis interface interconnection in this chapter are in different equipment rooms. E1 trunk cables connect digital distribution frames (DDFs) with the BSC and BTS respectively through transmission equipment.

Figure 3-1 shows the connection between the BSC and BTS.

BSC DDF BTS

BSC equipment room BTS equipment room

DDFBSC DDF BTS

BSC equipment room BTS equipment room

DDF

Figure 3-1 Connection between the BSC and BTS

Note:

The figure omits the transmission equipment between the BSC and the BTS.

3.1 Interconnection Procedures Abis interface interconnection comprises the following procedures:

1) Preparing for Abis interface interconnection 2) Checking physical connections 3) Checking data configuration 4) Checking E1 status 5) Checking link status

3.2 Preparing for Abis Interface Interconnection Make the following preparations for the Abis interface interconnection:

1) Load the program and data of the BSC to make boards run normally. 2) Complete the following connections:

From the BSC to the local DDF.


3-2

From the local DDF to the local transmission equipment. From the peer transmission to the peer DDF. From the peer DDF to the BTS.

3) Configure the data related to the transmission between the BSC and the BTS.

3.3 Checking Physical Connections Check the physical connections of the Abis interface in the following steps:

1) Check the connection between trunk cables and CBIEs/CXIEs in the BSC.

Insert trunk cables into the sockets on the CBIE/CXIE panel tightly from the bottom up.

2) Check the connection between the DDF and the trunk cables of CBIE/CXE.

One trunk cable includes 8 E1s, each of which has one pair of receive and transmit terminals.

The 16 receive and transmit terminals must be inserted into the sockets on the DDF sequentially. As shown in Figure 3-2, the 16 receive and transmit terminals of the trunk cables of the BSC are numbered sequentially according to E1 systems.

The receive terminals alternate with the transmit terminals from left to right.

RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX

TX RX TX RX TX RX TX RX TX RX TX RX TX RX TX RX

连接BSC

连接BTS

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Figure 3-2 Arrangement of receive and transmit terminals

3) Check the connection between the DDF and the trunk cables of transmission equipment.

One trunk cable includes 8 E1s, each of which has one pair of receive and transmit terminals connecting to DDFs.

The 16 receive and transmit terminals must be inserted into the sockets on the DDF sequentially. As shown in Figure 3-2, the 16 receive and transmit terminals of trunk cables of the transmission equipment are numbered sequentially according to E1 systems.

The transmit terminals alternate with the receive terminals from left to right.

4) Check the arrangement order of E1s on DDFs.

The E1s from the BSC must be interconnected with those from the transmission equipment sequentially in the way of one receive terminal to one transmit terminal.


3-3

For example, the receive terminal of E1 No.1 from the BSC must interconnect with the transmit terminal of E1 No.1 from the transmission equipment. The transmit terminal of E1 No.1 from the BSC must interconnect with the receive terminal of E1 No.1 from the transmission equipment.

As shown in Figure 3-3, the receive and transmit terminals from the BSC and the transmission equipment are connected through connectors.



To BSC

To transmissionequipment

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15



To BSC

To transmissionequipment

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Figure 3-3 Connection between receive and transmit terminals

3.4 Checking Data Configuration After the check on physical interconnection, check the logical interconnection, that is, check whether the BSC data configuration matches the BTS data configuration.

Table 3-1 lists the parameters to be negotiated.

Table 3-1 Data negotiation of BSC and BTS interconnection

Negotiation item

Value Command

BTS No. Internal BTS: 0 – 959 External BTS: 960 – 1919

BSC: ADD BSCBTSINFO BTS: ADD BTS

BTS BOOTP ID

VPI: 1 – 64 VCI: 32 – 225 It is recommended to select 2 to 15 for VPIs and 32 to 80 for VCIs.

BSC: ADD BTSOMLNK BTS: ADD BTSBTPINFO

BTS OML ID VPI: 1 – 64 VCI: 81 – 225

BSC: ADD BTSOMLNK

Service Link ID

The “VPI-VCI-VCCI” values of ATM links corresponding to service link IDs are numbered in forms like “1-250-1”, “1-249-2”, and “1-248-3”.

BSC: ADD BTSTRFLNK BTS: ADD BTSTERTRFLNK

BTS O&M IP Address

It is 129.m.10.N. “m” is the same as that in the IP address (129.m.10.n) of CMUX in the corresponding CIPS. “N” starts from 4 and increases sequentially with the change of BTS IDs.

BSC: ADD BSCBTSINFADD BTS


3-4

Negotiation item

Value Command

BTS Signaling IP Address

It is 80.m.130.n. “m” is equal to f % 4 + 1 and “f” is the number of the home CIPS of CSPU. “n” starts from 116 and increases sequentially with the change of BTS IDs.

BSC: ADD BSCBTSINF BTS: SET BTSTERSIGLNK

Carrier ID Starts from 0 in sectors. BSC: ADD CDMACH BTS: ADD BTSBTRM

For detailed data configuration, see Airbridge cBSC6600 CDMA Base Station Controller Data Configuration-Operation Manual and Airbridge BTS36 Series CDMA Base Station Data Configuration Manual.

3.5 Checking E1 Status After checking physical and logical interconnections between the BSC and BTS, check E1 status.

3.5.1 Querying E1 Status

Execute the command DSP E1T1STAT on the service maintenance system to query statuses of all links.

For example, query statuses of all links of the CBIE in slot 0 of subrack 2.

+++ HW-Airbridge 2004-04-06 10:18:22

O&M #47992

%%DSP E1T1STAT: FN=2, SN=SLOT0, BTP=CBIE;%%


Query Result

------------

Slot E1/T1No. E1/T1OperationalStatus

0 0 Has_loss-of-signal_alarm








0 8 Available



3-5























( Records = 32 )

--- END

Normally, “E1/T1OperationalStatus” should be “Available”. If the system displays abnormality, locate problems through loopback test.

Note:

Generally, loopback tests on CBIEs/CXIEs are unnecessary on the project site.

3.5.2 Carrying out Loopback Tests from the DDF to the BSC

Carry out a loopback test from the DDF in the BSC equipment room to the BSC in the following steps:

1) In the BSC equipment room, remove all connectors on the DDF that connect with the BSC and the transmission equipment.


3-6

2) Use one connector to join the receive terminal and the transmit terminal of link 0 on the BSC, as shown in Figure 3-4:



自环前

连接BTS

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15



连接BSC

连接BTS

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

自环后

连接BSC

Figure 3-4 Loopback on the DDF

3) Execute the command DSP E1T1STAT to query the status of link 0. If the status is normal, it indicates the link is connected well. Go to step 6. If the status is abnormal, it indicates the link connection is faulty. Go to step 4.

4) Check the connections between trunk cables and the DDF, and between trunk cables and the BSC.

If the connectors of trunk cables are faulty, remake them. If the connections between trunk cables and boards of the BSC or the DDF

are loose, fix related devices. If the receive and the transmit terminals of BSC trunk cables connecting to

the DDF are in incorrect sequence, refer to Figure 3-2 to reconnect them. 5) Execute the command DSP E1T1STAT to confirm that the status of link 0 is

normal. 6) Use connectors to join the receive terminal and the transmit terminal of link 1 on

the BSC. Refer to steps 3 to 5. Carry out this operation on all links to make sure that all links are normal.

7) Execute the command DSP E1T1STAT to confirm that all link statuses are normal.

8) Restore all connections to the original state before the loopback.


3-7

3.5.3 Carrying out Loopback Tests from the DDF to the Transmission Equipment

After the loopback test from the DDF to the BSC in the BSC equipment room, execute the command DSP E1T1STAT to query statuses of all links.

If any link is abnormal, carry out a loopback test from the DDF to the transmission equipment in the BTS equipment room to continue troubleshooting.

If all links are normal, it is recommended to carry out a loopback test to avoid cross-connected lines.

1) Remove all DDF trunk cables from the BTS in the BTS equipment room. 2) Connect the receive terminal and the transmit terminal of DDF link 0 connected

with the transmission equipment. 3) Execute the command DSP E1T1STAT to query the status of link 0.

If the status is normal, it indicates the link is connected well. Go to step 6. If the status is abnormal, it indicates the link connection is faulty. Go to step 4.

4) Check the connection from the DDF in the BTS equipment room to the DDF of the transmission equipment.

If the connectors of trunk cables are faulty, remake them. If the connection between trunk cables and the DDF is loose, fix related

devices. If the receive and the transmit terminals of trunk cables connected to the DDF

are not connected according to right sequential number, reconnect them correctly.

If trunk cables connect with the transmission equipment improperly, or the transmission equipment is abnormal, contact technical support engineers of transmission equipment for further troubleshooting.

5) Execute the command DSP E1T1STAT to confirm that the status of link 0 is normal.

6) Join the receive terminal and the transmit terminal of link 1 on the DDF in the BTS equipment room. Refer to steps 3 to 5. Carry out this operation on all links to make sure that all links are normal.

Note:

Generally, one or two E1s are connected to the BTS.

7) Execute the command DSP E1T1STAT to confirm that all link statuses are normal.

8) Restore all connections to the original state before the loopback test.


3-8

3.5.4 Checking Connections between the DDF and the BTS

After the loopback test from the DDF to the transmission equipment in the BTS equipment room, execute the command DSP E1T1STAT to query statuses of all links.

If any link is abnormal, check the connection between the BTS and the DDF in the BTS equipment room.

1) If the connectors of trunk cables are faulty, remake them. 2) If the connections between trunk cables and boards or the DDF are loose, fix

related devices.

After the above troubleshooting, the connection between the BTS and the DDF in the BTS equipment can recover to normal status.

3.6 Checking Link Status After the above E1 status check, links are available, which indicates normal physical connection.

Then execute commands DSP IMAGRPSTAT and DSP IMALNKSTAT to check statuses of IMA link groups and IMA links.

Note:

The Abis interface supports more than one link mode, such as IMA group, UNI link, electrical interface fractional ATM link, and optical interface fractional ATM link. Therefore, you need to select proper query commands for different link modes. The IAM group is used as an example in this part.

3.6.1 Checking IMA Group Status

Execute the command DSP IMAGRPSTAT on the service maintenance system to query IMA group status.

For example, query the status of IMA group 0 of the board in slot 0 of subrack 2.

+++ HW-Airbridge 2004-04-06 10:24:13

O&M #48021

%%DSP IMAGRPSTAT: FN=2, SN=SLOT0, IMAGN=0;%%


Query Result

------------

GroupLocalStatus = Operable

GroupRemoteStatus = Operable

UsableCellRateSentbyGroup = 3592


3-9

UsableCellRateReceivedbyGroup = 3592

GroupConfiguredSentLinks = 2

GroupConfiguredReceivedLinks = 2

GroupActivatedSentLinks = 1

GroupActivatedReceivedLinks = 1

GroupInvalidStatus = -

--- END

If the status of “GroupLocalStatus” and “GroupRemoteStatus” is ”Operable”, and the number of activated links meets the actual requirement, the IMA links are normal; otherwise, check and change the data configuration.

3.7 Checking BTS OML Before loading the programs and data files of the BTS, ensure that the operation and maintenance link (OML) from the BSC to the BTS is normal.

You can check the status of the OML from the BSC to the BTS by executing the command Ping on the BAM server. For example, if the IP address of the BTS operation and maintenance is 129.8.10.1, execute the command ping 129.8.10.1 –t.

If the execution succeeds, the OML from the BSC to the BTS is normal; otherwise, check and change the data configuration.

3.8 Loading BTS Programs and Data Files After the above commissioning, you can load the programs and data files of the BTS. For details, see Airbridge BTS36 Series CDMA Base Station Installation Manual-Software Installation & System Commissioning.

Installation Manual - System Commissioning Airbridge cBSC6600 CDMA Base Station Controller Chapter 4 A1/A2 Interface Interconnection

4-1

Chapter 4 A1/A2 Interface Interconnection

A1/A2 interface interconnection means performing checks and commissioning on the connection channels between the BSC and MSC to ensure normal connection.

This chapter describes the A1/A2 interface interconnection through E1s between the BSC and MSC in the same equipment room. Figure 4-1 shows the connection between the BSC and MSC.

BSC DDF MSC

Figure 4-1 Connection between the BSC and MSC

Note:

The BSC connects with the MSC through transmission equipment if they are located in different equipment rooms. It depends on actual situations.

4.1 Basic Procedures of Interconnection A1/A2 interface interconnection comprises the following basic procedures:

1) Preparations before A1/A2 interface interconnection 2) Check on physical connections 3) Check on data configuration 4) Check on E1 status 5) Check on signaling link status 6) Check on trunk circuit status

4.2 Preparations before Interconnection Before A1/A2 interface interconnection, complete the following:

1) Abis interface interconnection 2) BSC-DDF and DDF-MSC connections 3) Data configuration on the MSC and commissioning on the BSC


4-2

4.3 Checking Physical Connections Check basic physical connections of A1/A2 interface in the following steps:

1) Check the connection between trunk cables and CAIEs in the BSC.

The plugs of trunk cables must be inserted in the sockets on the CAIE panel tightly from the bottom up.

2) Check the connection between the trunk cables of CAIE and the DDF.

One trunk cable includes eight E1s, each of which has one pair of receive and transmit terminals.

The 16 receive and transmit terminals must be inserted into the sockets on the DDF sequentially. As shown in Figure 4-2, the 16 receive and transmit terminals of a trunk cable connecting with the BSC are numbered sequentially according to E1 systems.




To BSC

To MSC

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Figure 4-2 Arrangement of receive and transmit terminals

3) Check the connection between the DDF and trunk cables of the MSC.

One trunk cable includes eight E1s, each of which has one pair of receive and transmit terminals.

All the receive and transmit terminals must be inserted into the sockets on the DDF sequentially. As shown in Figure 4-2, the 16 receive and transmit terminals of a trunk cable connecting with the MSC are numbered sequentially according to E1 systems.


4) Check the connection between the BSC and MSC.

E1s from the BSC and the MSC must interconnect sequentially in the way of one receive terminal to one transmit terminal.

For example, the receive terminal of E1 No.1 of the BSC must connect with the transmit terminal of E1 No.1 of the MSC. Similarly, the transmit terminal of E1 No.1 of the BSC must connect with the receive terminal of E1 No.1 of the MSC.

As shown in Figure 4-3, the receive and transimt terminals from the BSC and the MSC are connected through connectors.


4-3



To BSC

To MSC

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

Figure 4-3 Connection between receive and transmit terminals

4.4 Checking Data Configuration After checking physical interconnection, check whether the BSC data configuration matches the MSC data configuration.

Table 4-1 lists the parameters to be negotiated.

Table 4-1 Data negotiation of BSC and MSC interconnection

Negotiation item

Value Description

Network Indicator

INTC (International) INT2C (International standby) NATC (National) NAT2C (National standby)

Identifies the network where signaling points reside. As defined in the protocol, the MSC must be in the same network as the BSC.

SPC Length 14 bits 24 bits

Coding scheme used for the network IP address of the BSC. It must match that of the A interface on the MSC.

Originating Point Code

0x0001 – 0x3FFF (14 bits) 0x000001 – 0xFFFFFF (24 bits)

Signaling point code (SPC) of the BSC itself. It must be a hexadecimal code matching that assigned by the MSC.

Destination Point Code

0x0001 – 0x3FFF (14 bits) 0x000001 – 0xFFFFFF (24 bits)

A-interface SPC of the MSC, a hexadecimal code.

Signaling Link Code and Send Signaling Link Code

0 – 255

Identity code of the signaling link between the BSC and the MSC, identifying signaling links. One signaling link has four same codes, that is, one Signaling Link Code and one Send Signaling Link Code on both the BSC and the MSC.

Subsystem No. BSSAPI (0xFE, 254) BSSAPGS (0xFC, 252) SCMG (0x01, 01)

It must match that corresponding to the A interface of the MSC.

CIC No. 0 – 4095 Identifies numbers of trunk circuits between the BSC and the MSC. The CIC number of a circuit at the BSC must match that at the MSC.


4-4

Negotiation item

Value Description

Circuit Table Uninstalled

You can select one or several circuits from circuits 0 to 31. By default, it is circuits 0 and 16.

One E1 cable requires at least one timeslot (timeslot 0) to transfer synchronization signals and others (timeslot 16) to transfer signaling signals. To ensure proper transmission and reception of the signals, the synchronization timeslot and signaling timeslot used on the BSC at one end of an E1 cable must match that on the MSC at the other end of the E1 cable.

A-Interface Version

IOS2.4 (version 2.4) IOS4.1 (version 4.1)

It must match that on the MSC.

System ID 0 – 32767 Uniquely identifies a CDMA cellular system.

Network ID 0 – 65535 Uniquely identifies the network in a CDMA cellular system.

MSC ID 0 – 0xFFFFFF Identifies different MSCs in the case of hard handoffs.

Manufacturer ID 0 – 65535 Identifies source BSCs in the case of inter-BSC soft handoffs, along with Entity IDs.

Entity ID 0 – 65535 For its function, see the item “Manufacturer ID". For its value, Entity IDs of an operator must differ.

Packet Zone ID 0 – 255

In a zone with specified System ID (SID)/Network ID (NID), Packet Zone ID (PZID) is used to uniquely specify the zone covered with the packet control function (PCF). Combination of SIDs/NIDs/PZIDs must correspond to the configuration on the PCF one by one.

Local Area Code 0 – 0xFFFF Numbered sequentially to define a group of cells.

Line Coding Format

HDB3 AMI B8ZS

Planned unifiedly in the same coding scheme.

For details about data configuration, see Airbridge cBSC 6600 CDMA Base Station Controller Operation Manual-Data Configuration.


4-5

Note:

In addition to data configuration listed in Table 4-1, you need to decide whether to change software and timer parameters in accordance with the MSC. Be careful that the settings of software parameters and timer may affect the system greatly.

4.5 Checking E1 Status After checking physical and logical interconnections between the BSC and MSC, check E1 status.

4.5.1 Querying E1 Status

Execute the command DSP E1T1STAT on the service maintenance system to query statuses of all links.

For example, query statuses of all links of the CAIE in slot 15 of subrack 3.

+++ HW-Airbridge 2004-04-06 10:28:19

O&M #48042

%%DSP E1T1STAT: FN=3, SN=SLOT15, BTP=CAIE;%%


Query Result

------------

Slot E1/T1No. E1/T1OperationalStatus

0 0 Available

0 1 Available

0 2 Available

0 3 Available

0 4 Available

0 5 Available

0 6 Available

0 7 Available










4-6

















( Records = 32 )

--- END

Normally, the E1/T1 Operational Status should be “Available”. If the system displays any exception, locate problems through loopback tests.

4.5.2 Carrying Out Loopback Tests from DDFs to BSCs

Carry out a loopback test in the following steps:

1) Remove all connectors on the DDF that connect the BSC and the MSC. 2) Use one connector to join the receive and the transimit terminals of link 0 on the

BSC, as shown in Figure 4-4:


4-7



Before loopback

To MSC

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15



To BSC

To MSC

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

After loopback

To BSC

Figure 4-4 Loopback connections on a DDF

3) Execute the command DSP E1T1STAT to query the status of link 0. If the status is normal, it indicates the link is connected well. Go to step 6. If the status is abnormal, it indicates the link connection is faulty. Go to step 4.

4) Check the connections between trunk cables and the DDF, and between trunk cables and the BSC.

If the connectors of trunk cables are faulty, remake them. If the connection between trunk cables and boards of the BSC, or between

trunk cables and the DDF is loose, fix related devices. If the receive and the transmit terminals of BSC trunk cables connecting to

the DDF are in incorrect sequence, refer to Figure 4-2 to reconnect them. 5) Execute the command DSP E1T1STAT to confirm that the status of link 0 is

normal. 6) Use connectors to join the receive and transmit terminals of link 1 on the BSC.

Refer to steps 3 to 5. Carry out this operation on all links to make sure that all links are normal.

7) Execute the command DSP E1T1STAT to confirm that the status of all links is normal.

8) Restore all connectors to the connection states before the loopback. 9) If you find no abnormal link connection during the loopback test, it indicates that

the DDF connects with the BSC normally. Contact MSC maintenance engineers for further commissioning and troubleshooting.


4-8

4.6 Checking Signaling Link Status After the above E1 status check, if links are available, it indicates normal physical connection of E1s.

Then execute the commands DSP MTP2STAT, DSP N7LNK, and DSP N7DPC to further check statuses of MTP2 and MTP3 links and destination signaling points (DSPs).

4.6.1 Querying MTP2 Link Status

Execute the command DSP MTP2STAT on the service maintenance system to query MTP2 link status.

For example, query the status of link 0 of the CLAP in slot 11 of subrack 3.

+++ HW-Airbridge 2004-04-06 10:40:37

O&M #48083

%%DSP MTP2STAT: FN=3, SN=11, LNKNO=0;%%


Query Result

------------

MTP2LinkStatus = Provide_Service

--- END

If the MTP2 link is in the Provide_Service state, it indicates that the MTP2 link is normal. Otherwise, check the data configuration.

4.6.2 Querying MTP3 Link Status

Execute the command DSP N7LNK on the service maintenance system to query MTP3 link status.

For example, query the status of link 0 of module 0.

+++ HW-Airbridge 2004-04-06 10:48:15

O&M #48114

%%DSP N7LNK: OPT=MN, MN=0, LNKNO=0;%%


Query Result

------------

ModuleNo. LinkNo. TransferService LinkActivated LinkBlocked

LinkFault LocalManagementInhibit RemoteManagementInhibit


4-9

LinkCongested Switchover Switchback SLS

0 0 Yes Yes No No

No No No No

No 00/01/02/03/04/05/06/07/08/09/0A/0B/0C/0D/0E/0F/

( Records = 1 )

--- END

Check whether the Transfer Service, Link Activated, and Link Blocked in the query result are normal. If no, check the data configuration.

4.7 Checking Trunk Circuit Status If the commissioning of signaling links is normal, check A2 circuit status.

4.7.1 Querying A2 Circuit Status

Execute the command DSP A2 on the service maintenance system to query A2 circuit status.

For example, query the status of the circuits with circuit identification code (CIC) numbers of 0 to 15.

+++ HW-Airbridge 2004-04-06 10:54:30

O&M #48197

%%DSP A2: OPC="0x00D105", NI=NATC, SCIC=0, ECIC=15;%%


Query Result

------------

CICNo. CICStatus OccupiedStatus

0 Unequipped Unequipped

1 Idle Idle

2 Idle Idle

3 Idle Idle

4 Idle Idle

5 Idle Idle

6 Idle Idle

7 Idle Idle

8 Idle Idle

9 Idle Idle


4-10

10 Idle Idle

11 Idle Idle

12 Idle Idle

13 Idle Idle

14 Idle Idle

15 Idle Idle

( Record Number = 16 )

--- END

If the system displays that the circuits are idle, it indicates that trunk circuits are normal. Otherwise, check the data configuration.

4.7.2 Resetting A2 Circuits

If the A2 circuits are all normal, you can execute the command RST A2 to further confirm A2 status.

Execute the command RST A2 on the service maintenance system to reset A2 circuits.

For example, reset the circuit with the CIC No. of 1.

+++ HW-Airbridge 2004-04-06 10:58:53

O&M #48212

%%RST A2: OPC="0x00D105", NI=NATC, SCIC=1, ECIC=1, CONFIRM=Y;%%


Execution Result

----------------

CICNo. ResetResults

1 Successful

( Record Number = 1 )

--- END

Meanwhile, the system displays the following alarm information in the window [Alarm].

+++ HW-Airbridge 2004-04-06 10:58:53

ALARM 5656 Event Major BSC 2107 Trunk System

Alarm Name = BSC Reset Circuit

Location Information = BSC SPC=0x00D105, Network Indicator=NATC,

Speech Processing Subrack No.=

46, Start E1 No.=0, Start TS No.=1, Start


4-11

Circuit No.=1, Number of Reset

Circuits=1, Reset Multiple Circuits=No,

Reset All Circuits over SP=No,

Reset All Circuits in Circuit Range=No,

Circuit Position Table=0x00000000

, Cause=OAM&P Intervention

--- END

+++ HW-Airbridge 2004-04-06 10:58:53

ALARM 5657 Event Major BSC 2108 Trunk System

Alarm Name = BSC Circuit Reset Acknowledgement

Location Information = BSC SPC=0x00D105, Network Indicator=NATC,

Speech Processing Subrack No.=

46, Start E1 No.=0, Start TS No.=1, Start

Circuit No.=1

--- END

If there is any BSC Circuit Reset Acknowledgement, it indicates that the A2 circuit is normal; if no, it indicates the CIC is incorrect. In the latter case, you need to change relevant data configuration.

Installation Manual - System Commissioning Airbridge cBSC6600 CDMA Base Station Controller Chapter 5 Service Commissioning

5-1

Chapter 5 Service Commissioning

If interconnections of Abis interface and A1/A2 interface are successful, it indicates that the physical connections between BSC and BTS and between BSC and MSC, and the data configuration on them are correct.

To check whether services are normal, proceed with the procedures in the following sections.

5.1 Service Commissioning Procedures Service commissioning comprises the following procedures:

1) Preparing for service commissioning 2) Making test calls on a specified A2 circuit 3) Making test calls on basic services 4) Making test calls on packet data service 5) Making test calls on circuit data service

In actual deployment, you can test other services as needed.

5.2 Preparing for Service Commissioning Before service commissioning, complete the following:

Interconnection of Abis interface Interconnection of A1/A2 interface Interconnection of A10/A11 interface Preparation of test MSs

5.3 Making Test Calls on a Specified A2 Circuit Specify CIC of a specific A2 circuit and make test calls to check its status.

Note:

The test of a specified A2 circuit requires that the MSC must support the preferred circuit and the function must be activated. Otherwise the test is invalid.

5.3.1 Test Flowchart

Figure 5-1 shows the basic procedure of test calls of a specified A2 circuit:


5-2

Specify preferred CIC/Modify preferred CIC

Start

Prepare an MS

Is call test performed to all

CICs?

Cancel preferred CIC

End

Y

N

Make call test

Remove faults in call test.

Figure 5-1 Flowchart of test calls of a specified A2 circuit

5.3.2 Test Procedure

I. Prepare a MS

Prepare a MS for the test. The number of the MS must have been defined in the HLR and corresponding parameters must have been set.

II. Specify a preferred CIC

Specify a preferred CIC using the command OCP CIC. The following details the command:

Command

OCP CIC

Function

Specifies a preferred CIC and the corresponding MS.

Parameters


5-3

[IMSI]: IMSI of the MS specified for test.

[Network indicator]: Indicator of the network. There are four options for this parameter, namely, International, International Standby, National, and National Standby. For A2 interface, National Standby is generally selected.

[Originating point code]: Originating point code uniformly assigned for each module of BSC during system planning. It is coded in hexadecimal. The originating signaling point and the destination signaling point code must be identical in terms of number of digits.

[CIC No.]: CIC No. uniquely specified. Only the MS with specified IMSI can select this CIC.

III. Test calls

Dial a fixed telephone number using the test MS. After the call is connected, the telephone of the called party should ring, and the conversation should be carried out normally after the called party hooks off. At the moment, check whether the circuit is occupied using DSP A2.

If there is anything wrong during the test, you should record the CIC of the circuit.

IV. Modify preferred CIC

To proceed with test of another A2 circuit, you need to modify the CIC after the test.

You can modify the preferred CIC using SET CIC. The following details the command:

Command

SET CIC

Function

Modifies the preferred CIC and the corresponding MS.

Parameters

[IMSI]: IMSI of the MS specified for test. Normally, it is equal to the IMSI in the command OCP CIC.

[Network indicator]: Indicator of the network. There are four options for this parameter, namely, International, International Standby, National, and National Standby. For A2 interface, National Standby is generally selected.

[Originating point code]: Originating point code uniformly assigned for each module of BSC during system planning. It is coded in hexadecimal. The originating signaling point and the destination signaling point code must be identical in terms of number of digits.

[CIC No.]: CIC No. uniquely specified. Only the MS with specified IMSI can select this CIC.


5-4

V. Test calls

Same as III. Test calls.

VI. Cancel preferred CIC

Cancel the preferred CIC specified using UOC CIC after the test. The following details the command:

Command

UOC CIC

Function

Cancels the preferred CIC associated with the test MS.

Parameters

[IMSI]: IMSI of the MS specified for test.

VII. Remove faults

If everything is all right during the test, this step is unnecessary.

If there is anything wrong during the test, you must record the CIC of the circuit, modify the configuration data, and test the circuit with the CIC until the test passes.

5.4 Making Test Calls on Basic Services In this test, check that:

Voice calls (MO calls and MT calls) can be established successfully, and conversation and call release is normal.

SMS is normal. Location update is normal. Handoff is smooth, and conversation is normal.

5.5 Making Test Calls on Packet Data Service In this test, check that:

Packet data service calls are normal. Internet services (browse and download services) of the MS are normal.

5.6 Making Test Calls on Circuit Data Service In this test, check that:

Circuit data service calls are normal. Asynchronous data services are normal. G3 fax services are normal. Analog fax services are normal.

Installation Manual - System Commissioning Airbridge cBSC6600 CDMA Base Station Controller Chapter 6 Network Optimization

6-1

Chapter 6 Network Optimization

To optimize wireless network is to do the following in accordance with relevant rules:

Collect network operation data. Analyze and appraise network performance. Adjust design of radio network properly.

By optimizing wireless network, you can make network operation more reliable and efficient, and improve network service quality.

Network optimization is a complex procedure. This chapter provides a brief description of network optimization procedures.

6.1 Network Optimization Procedures Figure 6-1 shows procedures of network optimization.

Analyze data andappraise performance

Start

Collect network operationdata

Verify networkoptimization

Doesthe system meetrequirements?

Provide networkoptimization reports

End

Y

N

Adjust parameters

Prepare for networkoptimization

Figure 6-1 Network optimization flowchart


6-2

6.2 Preparations for Network Optimization Before optimizing network, ensure that the system and services operate normally.

In addition, you must prepare the following:

6.2.1 Arranging Personnel

Huawei network optimization engineers take charge of network optimization tasks with the assistance of Huawei technical support engineers and a manager of a network operator.

6.2.2 Preparing Tools

Before optimizing the network, prepare the following tools:

Software for network tests, analysis, and diagnoses High-performance laptop CDMA mobile stations (MSs) for tests (with data wires) Global position system (GPS) attached with data wires and antennas PCMCIA dual-serial port cards or cables for converting universal serial bus (USB)

ports to serial ports

In addition, you need the following for some other uses:

A signaling analyzer for signaling trace and location A pseudo number (PN) scanning instrument for tests of network pilot pollution Devices like a frequency spectrometer for disturbed tests

6.2.3 Preparing Documents

Before optimizing the network, collect all reports in the phase of network planning and check whether the current network differs from that defined in the planning phase.

Moreover, you should prepare the following documents for reference:

Airbridge cBSC6600 CDMA Base Station Controller Installation Manual-Hardware Installation

Airbridge cBSC6600 CDMA Base Station Controller Installation Manual-Software Installation

Airbridge cBSC6600 CDMA Base Station Controller Operation Manual-Data Configuration

Airbridge BTS36 Series CDMA Base Station Installation Manual-Software Installation & System Commissioning


6-3

6.2.4 Checking Engineering Parameters

Before optimizing the network, check hardware engineering parameters of BTSs, such as antenna heights, azimuths, and tilts. If any parameter is inconsistent with the design requirements, adjust it as soon as possible to keep it identical with the design.

6.3 Collection of Network Operation Data To optimize the network, you must first know the performance and status of the network operation. Then you can analyze network faults and figure out resolutions.

To know the performance and status of the network operation, collect the following network operation data.

6.3.1 Collecting Traffic Measurement Data

Traffic measurement data reflects the operation quality and status of the whole network from the perspective of statistics. Therefore, the operator appraises the network performance based on traffic measurement items.

When optimizing the network, pre-register traffic measurement tasks as needed. Set the following performance measurement items:

Congestion rate Call drop ratio of radio system Success ratio of call setup Success ratio of soft handoff Success ratio of hard handoff

Registration of traffic measurement tasks and setting of performance measurement items depend on actual site requirements.

6.3.2 Collecting Drive Test Data

Drive tests are to sample certain paths using drive test devices. Drive test data reflects the operation quality of the network by sampling. The number of sampling points is in proportion to the amount of information obtained. Compared with traffic measurement data, drive test data can reflect network problems in more details.

Drive test data includes:

Distribution of pilot strength (Ec/Io) Distribution of frame error rate (FER) Distribution of receiving level Distribution of transmitting level Handoff distribution Call drop Access time and speed


6-4

Subjective voice quality

Collection of drive test data depends on actual site requirements.

6.3.3 Collecting Alarm Data

Alarms centrally reflect abnormalities or quasi abnormalities in network operation. During network optimization, you should periodically check alarm information to in time identify faults or pre-warning information to minimize accidents.

6.3.4 Making Test Calls in Major Areas

The quality of major areas in the network may affect the whole network.

You can choose the following areas to make test calls:

Government agencies Distribution regions of large enterprises or group users Major hotels or entertainment places Bus stops, airports, or harbors

Selection of call test sites depends on actual site requirements.

You can directly use MSs to make test calls by MSs calling MSs, MSs calling fixed phones, or fixed phones calling MSs. You can determine the network coverage and quality through your feeling. If your MSs can display test information, the information helps determine the coverage and quality of the network.

6.4 Data Analysis and Performance Appraisal Collection of network operation data is to evaluate network performance and locate network problems.

Analysis of network operation data is to learn quality of network operation and find out potential problems in the network by analyzing traffic measurement data, drive test data, test call data, and alarm data.

To locate problems and provide network optimization suggestions, you should integrate analysis of network operation data with analysis of engineering parameters, system configuration parameters, and calling processes.

6.5 Suggestions and Measures on Network Optimization Optimization suggestions and measures are provided on the basis of the analysis of network operation data and appraisal of network performance.

Take specific network optimization measures to resolve such problems as call drop, handoff, interference, poor coverage, and traffic unbalance.


6-5

6.5.1 Network Optimization Suggestions

I. Partition optimization and overall network optimization

For a large-scale network, you can divide it into several partitions, optimize each partition individually and then the overall network.

That is, first optimize several neighbor BTSs and then another several. Deal with the rest similarly until complete the whole network optimization.

You can begin optimization with the densely-populated area until to the sparsely-populated area.

II. Network optimization of overall performance

Network optimization focuses on enhancing radio frequency (RF) environment. The hardware engineering parameters of RF environment such as total transmit power and antenna parameters of each sector determine the overall layout of the network, service areas of cells, and even the overall performance of the network.

III. Network optimization of partial performance

After optimizing overall performance, go on with optimizations in more details. That is, adjust such parameters as pilot search window, message-related system parameters, handoff ratio, and handoff threshold.

6.5.2 Network Optimization Measures

Network optimization measures are classified as:

I. Adjusting engineering parameters

To resolve such problems as network coverage or interference, adjust the engineering parameters of the network including power configuration, antenna downtilts, azimuths, and height.

II. Adjusting system parameters

After determining engineering parameters, you can set system parameters. Because system parameters affect network performance to a certain extent, proper adjustment can optimize the system operation. If the network fails owing to improper setting of system parameters, you must change system parameters.

III. Expanding the system capacity

If the system fails to meet the requirements of network quality even after the adjustment of engineering parameters and system parameters, you need to expand the capacity. For example, add carriers or BTSs.

This measure is inapplicable to newly-deployed offices.


6-6

6.6 Network Optimization Verification After taking network optimization measures, check whether network problems are resolved or network performance are enhanced.

The verification process is also an integral part of network optimization.

It is similar to the initial phase of network optimization, that is, collecting and analyzing network operation data. Types of collected data and analysis methods comply with the above requirements. By data collection and analysis after optimization, you can determine whether the network performance meets requirements.

Note:

If the network performance does not meet requirements yet, re-adjust parameters until the system provides acceptable level of performance.

6.7 Network Optimization Reports After verifying network optimization, if the network performance meets requirements, you submit network optimization reports.

A network optimization report covers processes of analyzing and locating problems, measures taken, measurement items before and after the optimization, outstanding issues, and follow-up suggestions.

Engineering parameters are adjusted during network optimization. Therefore, you must update the total engineering parameter table provided at the planning phase based on current engineering parameters.

Installation Manual - System Commissioning Airbridge cBSC6600 CDMA Base Station Controller Chapter 7 Preliminary Acceptance and Cutover

7-1

Chapter 7 Preliminary Acceptance and Cutover

This chapter briefs the procedures of preliminary acceptance, service cutover and corresponding precautions.

7.1 Preliminary Acceptance According to the engineering plan, Huawei BSC technical support engineers must carry out preliminary acceptance with the customer after service commissioning and network optimization. For specific acceptance items, see Airbridge cBSC6600 CDMA Base Station Controller-Acceptance Manual.

Before the preliminary test, BSC technical support engineers can negotiate with the customer on the test items.

After testing each item, the customer is required to confirm the test results.

7.2 Service Cutover

Note:

Normally, if the preliminary acceptance passes, it indicates that the equipment satisfies requirements of the operator and can be put into service. In this case, there is no service cutover process.

Service cutover is necessary in the following cases:

If the channel numbers used in the commissioning process are temporary ones, the temporary channel numbers must be changed to formal ones.

If the specified BTS is not connected to the BSC during the commissioning process, all BTSs must be connected to the BSC as required.

If the BSC is just connected to the MSC used for commissioning, the BSC must be connected to an operating MSC as required.

Before service cutover, BSC technical support engineers must collaborate with the customer to nail down particular cutover scheme. If change of equipment like MSC and HLR is involved, BSC technical support engineers must ask relevant technical support engineers to join the service cutover.

If change of data configuration and hardware connection is involved, BSC technical support engineers must carry out the service cutover after 24:00.

After service cutover, network optimization is required to ensure that the equipment being launched into commercial use truly satisfies the design requirements.

Installation Manual - System Commissioning Airbridge cBSC6600 CDMA Base Station Controller Appendix A Upgrade Operation

A-1

Appendix A Upgrade Operation

The system needs to be upgraded to meet the requirements of service, function, and maintenance in a better way. With higher reliability and better maintainability, the upgraded system can provide you with better services.

This appendix describes the software upgrade procedure without involving the upgrade of operating system and database software and hardware.

Note:

This appendix only covers the basic operations on the software upgrade. For details, see the upgrade guideline corresponding to the product version.

A.1 Software Upgrade Procedures

The software upgrade comprises the following:

1) Prepare for software upgrade 2) Upgrade the staging BAM server software 3) Upgrade the host software on the staging BAM server 4) Upgrade the formal BAM server software 5) Switch from the staging BAM server to the formal one 6) Upgrade the emergency workstation 7) Modify the loading control mode

A.2 Preparing for Software Upgrade

1) Make sure the BAM server works normally before upgrade.

Before the version upgrade, you must make sure that the BAM server to be upgraded is running normally; otherwise the upgrade is not allowed. To check the operational status of the BAM server, see Airbridge cBSC6600 CDMA Base Station Controller Maintenance Manual – Routine Maintenance

2) Confirm the version information of the current software.

Confirm that the BAM server software matches the software version. Before the upgrade, you must confirm the current software version information in the BAM server and the information of the target version.

3) Confirm the data consistency between the host and the BAM server.


A-2

Before the upgrade, make sure that the data in the BAM server database and that in the host are consistent.

You can use the command STR CRC to perform the cyclic redundancy check (CRC) on the data in the service table to check the consistency between the BAM server and the host.

Note:

Make sure that all the data in the host must be consistent with that in the service table in the BAM server. If the data is inconsistent, contact Huawei technical support engineers for troubleshooting; then decide whether to start the upgrade.

4) Obtain the software and data of the target version.

Obtain the latest BAM server software, loading programs, and data files of the target version from Huawei Technologies.

Check whether the BAM server software of the target version is correct and supports the current upgrade.

A.3 Switching from Formal BAM Server to the Staging One

Use the emergency workstation to replace the formal BAM server. Therefore, the emergency workstation functions as a staging BAM server. The switchover includes the following steps:

1) Disconnect the network cable between the emergency workstation and the formal BAM server.

2) Set the IP address of the emergency workstation to that of the formal BAM server.

3) On the emergency workstation, configure the routing data the same as that on the formal BAM server.

A.4 Upgrading BAM Server Software on Staging BAM Server

The emergency workstation software must be upgraded to the BAM server software to realize the staging BAM server function. Therefore, you need to uninstall the emergency workstation software first; then install the latest BAM server software.

A.4.1 Disabling the Service and Programs of the Staging BAM Server

Before uninstalling the emergency workstation software, you need to disable services and programs on the staging BAM server as below.


A-3

I. Exit all BAM applications

Exit the running service maintenance and alarm management systems.

II. Stop the BAMService and Smirror

The BAMService of the emergency station stays in the stop status by default. If it is in the start status, you need to stop it.

1) Open Services.

Select [Start/Setting/Control Panel/Management Tools/Services], and then the [Services] window is displayed, as shown in Figure A-1:

Figure A-1 Services

Select the “BAMService” and double-click it.

2) Stop BAMService.

The [BAMService Properties (Local Computer)] window is displayed, as shown in Figure A-2:


A-4

Figure A-2 BAMService properties

Select the “Startup Type” as “Manual”.

Click the <Stop> button.

3) Stop Smirror.

Stop the “Smirror” in the same way as stopping the “BAMService”.

III. Exit the BAM manager

The BAM manager of the emergency station stays in the stop status by default. If it is in the start status, you need to stop it.

1) Open the BAM manager.

Double-click the “BAM Manager” icon on the task bar at the right lower corner and then the [BAM Manager] window is displayed, as shown in Figure A-3:


A-5

Figure A-3 BAM manager

Click the shortcut icon on the tool bar.

2) Exit the BAM manager.

The [BAM Security Manager] dialog box is displayed, as shown in Figure A-4:

Figure A-4 Exiting the BAM manager

Click <Yes> to exit the BAM manager.

IV. Exit the database applications

Exit all running applications of Microsoft SQL Server 2000.

A.4.2 Uninstalling the Emergency Workstation Software

Uninstall the BTS software and the BSC software as below.

1) Uninstall the BTS software.

Select [Start/Settings/Control Panel] and run [Add/Remove Programs]. Double-click the BTS software in the program list and complete the uninstalling according to the prompts.

2) Uninstall the BSC software.


A-6

Select [Start/Settings/Control Panel] and run [Add/Remove Programs]. Double-click the BSC software in the program list and complete the uninstalling according to the prompts.

A.4.3 Installing the BAM Server Software on Staging BAM Server

Install the BAM server software of the latest version on the staging BAM server as below.

1) Install the BSC software.

For details of BSC software installation, see Airbridge cBSC6600 CDMA Base Station Controller Installation Manual – Software Installation.

Note:

You must restart the staging BAM server after the installation; otherwise, the system cannot start the BAM manager automatically.

2) Install the BTS software.

For details on BTS software installation, see Airbridge BTS36 Series CDMA Base Station Installation Manual - Software Installation & System Commissioning.

A.5 Upgrading Host Software on Staging BAM Server

Upgrade the host software on the staging BAM server as below:

1) Copy the program files and the script data files.

Copy the program files and script data files of boards to the path “D:\ cdma2000\LoadDATA” of the staging BAM server.

2) Set the loading control mode

Execute the command MOD LODCM to modify the loading control mode. Set the loading control mode of the host program, DSP program and data files of all boards to “Load from BAM and write to FLASH”

3) Batch process the script data files.

In the menu of Service Maintenance System on the staging BAM server, select [System/Execute Batch File…] to batch process the script data files to generate the DAT files.

For details, see Chapter 2, “Loading Operation” in Airbridge cBSC6600 CDMA Base Station Controller Installation Manual – System Commissioning.

4) Replace the formal BAM server.


A-7

Disconnect the network cable between the formal BAM server and the host.

Connect the staging BAM server with the host through the network cable.

5) Load the host software.

Reset the boards; then the system starts to load the program files and data files of the boards.

6) Modify the loading control mode.

On the completion of the loading, execute the command MOD LODCM to modify the loading control mode. Set the loading control mode of the host program and DSP program of all boards to “Load from FLASH.

7) Check the loading.

Check the loading data and the status of boards.

For details, see Chapter 2, “Loading Operation” in Airbridge cBSC6600 CDMA Base Station Controller Installation Manual – System Commissioning.

8) Make test calls.

When the loading succeeds, you need to make test calls to check whether the host software upgrade affects the services.

A.6 Upgrading BAM Server Software on Formal BAM Server

When the upgrade of the host software completes on the staging BAM server and the system runs normally, you can upgrade the software of the formal BAM server.

A.6.1 Making Preparations

You need to make the following preparations before upgrading the formal BAM server software.

I. Make sure that all alarms are processed.

During the version upgrade, the alarm database is replaced by a new one. Therefore, the alarms before the upgrade are removed automatically and cannot be queried after the upgrade. Make sure that all alarms are processed before the upgrade.

II. Make sure that all traffic measurements are processed.

During the version upgrade, the traffic measurement database (Perf database) is replaced by a new one. Therefore, the traffic measurement tasks and results cannot be queried after the upgrade. You need to use related commands to register all traffic measurement tasks again. Make sure that all traffic measurement results are processed before the upgrade and the command script files for re-registering all traffic measurement tasks already exist. It is recommended to save the traffic measurement results to compare the related performance items before and after the upgrade. Consequently, the changes of the network performance can be known.


A-8

III. Back up the database files on the formal BAM server.

You need to back up the database files before the upgrade. In this way, you can restore the database in case of the version upgrade failure.

In the Service Maintenance System of the BAM server, execute the command BKP DB to back up the database and the registry to the default path “F:\cdma2000\backup”. The following are the generated backup database, registry data, and BAM system configuration files:

AlarmYYYYMMDD.dat (alarm database) BamYYYYMMDD.dat (BAM database) PerfYYYYMMDD.dat (traffic measurement database) CSWSYYYYMMDD.dat (switching subrack configuration database) CDrYYYYMMDD.dat (CDR database) RFMTYYYYMMDD.dat (RF items measurement database) BamRegYYYYMMDD.bak (registry data) CDMA2000YYYYMMDD.ini (BAM system configuration files)

Here, “YYYY”, “MM”, and “DD” refer to the year, month, and date of the backup respectively. For the small-capacity scheme of the system, the CSWSYYYYMMDD.dat (switching subrack configuration database) does not exist.

IV. Back up the old programs, patches, and data.

During the version upgrade, the programs and data of the latest version overwrite the old ones directly. For easy backoff in the case of upgrade failure, you need to back up the old programs, patches, and data. Copy the files under the path “D:\cdma2000\LoadDATA” to the backup directory. It is recommended to copy the files to the emergency workstation so that they can be restored if the BAM server is faulty.

V. Export the original registry.

Select [Start/Run…] and enter “regedit” to run the registry. Export the registry file and save it under the specified path.

A.6.2 Disabling Services and Programs of the Formal BAM Server

Before uninstalling the software of the BAM server, you need to disable services and programs of the formal BAM server as below.

1) Exit all BAM applications.

Exit the running service maintenance and alarm management systems.

2) Stop the BAMService and Smirror.

For details, see A.4.1 II. , “Stop the BAMService and Smirror”.

3) Exit the BAM manager.

For details, see A.4.1 III. , “Exit the BAM manager”.


A-9

4) Exit the database applications.

Exit all running applications of Microsoft SQL Server 2000.

A.6.3 Uninstalling the BAM Server Software






A.6.4 Installing the BAM Server Software on the Formal BAM Server

Install the BAM server software of the latest version on the formal BAM server as below.


For details of BSC software installation, see Airbridge cBSC6600 CDMA Base Station Controller Installation Manual – Software Installation.

Note:

You must restart the formal BAM server after the installation; otherwise, the system cannot start the BAM manager automatically.



A.7 Switching from Staging BAM Server to Formal One

After completing the installation of the BAM server software, you can use the formal BAM server to replace the staging one (the original emergency workstation).

A.7.1 Detaching the Database Files on the Staging BAM Server

Detach the database files on the staging BAM server as below:


A-10

1) Stop the BAMService on the staging BAM server.

For details, see A.4.1 II. , “Stop the BAMService and Smirror”

2) Exit the BAM manager on the staging BAM server.

For details, see A.4.1 III. , “Exit the BAM manager”

3) Detach the database files and log files on the staging BAM server.

Select [Start/Programs/ Microsoft SQL Server/Query Analyzer] to run the “SQL Query Analyzer”.

Execute the following commands:

exec sp_detach_db 'Perf'

exec sp_detach_db 'Alarm'

exec sp_detach_db 'Bam'

exec sp_detach_db 'RFMT'

exec sp_detach_db 'CDr'

exec sp_detach_db 'CSWS'

Note:

To ensure the security of the database, it is recommended to use the “Detach. bat” tool to detach the database files and log files automatically. You can get this tool from Huawei technical support engineers. For the small-capacity scheme of the system, do not execute the command “exec sp_detach_db 'CSWS'”.

A.7.2 Copying the Files and Programs on the Staging BAM Server

Copy the files and programs on the staging BAM server as below.

1) Stop the BAMService on the formal BAM server.

For details, see A.4.1 II. , “Stop the BAMService and Smirror”

2) Exit the BAM manager on the formal BAM server.

For details, see A.4.1 III. , “Exit the BAM manager”

3) Copy the database files and log files on the staging BAM server.

Note:

Make sure that the versions of the SQL Server software on the staging BAM server and the formal BAM server are consistent.


A-11

Copy the following files on the staging BAM server to the same directories on the formal BAM server.

D:\cdma2000\mssql\data\Perf.mdf, E:\cdma2000\mssql\data\Perf_log.ldf D:\cdma2000\mssql\data\Alarm.mdf E:\cdma2000\mssql\data\alarm_log.ldf D:\cdma2000\mssql\data\Bam.mdf E:\cdma2000\mssql\data\Bam_log.ldf D:\cdma2000\mssql\data\Cdr.mdf E:\cdma2000\mssql\data\Cdr.mdf D:\cdma2000\mssql\data\RFMT.mdf E:\cdma2000\mssql\data\RFMT.mdf

4) Copy the loading programs and data files on the staging BAM server.

Copy all files under the following directory on the staging BAM server to the same directory on the formal BAM server.

D:\cdma2000\LoadDATA

A.7.3 Attaching the Database Files on the Formal BAM Server

On the formal BAM server, select [Start/Programs/ Microsoft SQL Server/Query Analyzer] to run the “SQL Query Analyzer”.

Execute the following commands:

exec sp_attach_db @dbname = 'Perf', @filename1 =

'D:\cdma2000\mssql\data\Perf.mdf', @filename2 =

'E:\cdma2000\mssql\data\Perf_log.ldf'

exec sp_attach_db @dbname = 'Alarm', @filename1 =

'D:\cdma2000\mssql\data\Alarm.mdf', @filename2 =

'E:\cdma2000\mssql\data\Alarm_log.ldf’

exec sp_attach_db @dbname = 'Bam', @filename1 =

'D:\cdma2000\mssql\data\Bam.mdf', @filename2 =

'E:\cdma2000\mssql\data\Bam_log.ldf'


'D:\cdma2000\mssql\data\RFMT.mdf', @filename2 =

'E:\cdma2000\mssql\data\RFMT_log.ldf'


'D:\cdma2000\mssql\data\CDr.mdf', @filename2 =

'E:\cdma2000\mssql\data\CDr_log.ldf'


'D:\cdma2000\mssql\data\CSWS.mdf', @filename2 =

'E:\cdma2000\mssql\data\CSWS_log.ldf'


A-12

Note:

To ensure the security of the database, it is recommended to use the “Attach. bat” tool to attach the database files and log files automatically. You can get this too from Huawei technical support engineers. For the small-capacity scheme of the system, do not execute the command “exec sp_attach_db @dbname = 'Bam', @filename1 = 'D:\cdma2000\mssql\data\CSWS.mdf', @filename2 = 'E:\cdma2000\mssql\data\CSWS_log.ldf'”.

A.7.4 Replacing the Staging BAM Server with the Formal BAM Server

Replace the staging BAM server with the formal BAM server as below:

1) Disconnect the network cable between the staging BAM server and the host. 2) Re-connect the formal BAM server and the host with the network cable. 3) Connect the staging BAM server with the external network through its network

cable. 4) Change the IP address of the BAM server to that on the network segment of the

external network.

A.8 Upgrading Emergency Workstation Software

After the formal BAM server replaces the staging BAM server, you need to restore the emergency workstation function of the staging BAM server.

A.8.1 Uninstalling the BAM Server Software






A.8.2 Installing the Emergency Workstation Software

Install the emergency workstation software on the emergency workstation as below.



A-13

For details of emergency workstation software installation, see Airbridge cBSC6600 CDMA Base Station Controller Installation Manual – Software Installation.



A.9 Modifying Loading Control Mode on Formal BAM Server

If the equipment can run normally for about three days without any abnormal alarms, it indicates that the software upgrade succeeds.

Execute MOD LODCM to change the loading control mode of host programs and DSP programs of all boards to "Load from FLASH".

Installation Manual - System Commissioning Airbridge cBSC6600 CDMA Base Station Controller Appendix B Patch Operation

B-1

Appendix B Patch Operation

The patch for the BSC system includes BSC software patch and terminal system patch.

The patch described in this manual applies to the BSC software only, that is, this document only describes the patch operation on the BSC software.

Patch operations are designed for terminal system according to actual requirements, and there is no specific method and process; thus, patch operation on terminal system is seldom required. For detailed patch operation on a terminal system, see the instruction of the patch.

B.1 Basic Concepts of Patch

The following details functions, features, and status of a patch.

B.1.1 Functions

Patches can free you from upgrading the BSC software frequently and enhance corresponding BSC software, without affecting normal system operation.

Caution:

Online patching directly affects normal running of BSC programs. You must be careful when patching the BSC software. For precautions of online patching, see the instruction delivered with the patch.

B.1.2 Features

A BSC patch has the following basic features:

The BSC software patch is an online patch. A new patch encompasses the old one, and will override the old one automatically when installed. You can decide whether to enable certain functions through software parameters.

The boards that can be patched online are CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CLAP, CBPU, CPCU, COIE, and CBIE. Each board has its individual patch. For example, the patch file of CRMU is "I00RMU0.002", and that of CSPU is "I00SPU0.001" ("001" and "002" indicate the version number of the patch).


B-2

The patches are designed with basic version plus patch. That is, any patch has a definite basic version. Therefore, you must match the right patch with the right basic version in the patch operation.

B.1.3 Status

There are four patch states, IDLE, DEACTIVATED, ACTIVE, and RUN.

IDLE: The patch does not exist in the memory. DEACTIVATED: The patch is loaded but not activated because the patch code is

not executed. ACTIVE. The patch is activated and the patch code is running. This is a trial

status. If the BSC is reset, the patch is automatically loaded upon restart. But it cannot resume to the active state automatically. After the patch is activated, you must recover the BSC to the deactivated state if the BSC is abnormal in its trial running. If the system runs normally, change it to the RUN state.

RUN: The patch starts running. If the patch is in the RUN state, you cannot recover it to the original status but delete it. Upon restart, the system loads the patch automatically, and then the patch will resume to the RUN state automatically.

Figure B-1 shows the conversion between statuses:

Idle Deactivated

ActiveRun

Loaded

Deleted

Activated Back off

Run

DeletedDeleted

Idle Deactivated

ActiveRun

Loaded

Deleted

Activated Back off

Run

DeletedDeleted

Figure B-1 Status conversion relationship

B.2 Operating Commands for a Patch

Through commands, you can operate on a patch as needed. The following describes the commands used for specific operations.

B.2.1 Loading Board Patch Files

This operation is to load patch files on a board, that is, load the implementation code of a patch to the patch area of each board.


B-3

I. Command

LOD PATCH

II. Parameters

[Option]: You can select one from "Subrack No. + Slot No. + Subsystem No.", "Subrack No. + Board Type", and "Board Type".

[Board Type]: You can select to load patches to any of the following: CMUX, CSPU, CPPU, CFMR, CRMU, CXIE, CEVC, CAIE, CLAP, CBPU, CPCU, COIE, and CBIE.

[Running Patches]: It indicates the number of the patches that can start running automatically. If the value is "n", then "1 – n" patches will run automatically upon system restart. The rest are deactivated.

[Patch File No.]: It indicates the number of the patch file to be loaded. If the value is "n", then "1 – n" patch files are loaded.

B.2.2 Transiting Board Patch Status

This operation is to change the board patch status.

1) Command

SET PATCHSTAT

2) Parameters

[Option]: You can select one from "Subrack No. + Slot No. + Subsystem No.", "Subrack No. + Board Type", and "Board Type". It is recommended to use "Subrack No. + Board type" because it can reduce the impact on the system and the risk of operations.


[Patch File No.]: It indicates the number of the patch file to be loaded. Assume the entered value is "n", if the [Transition Type] is "Activate Patch" or "Confirm Patch", "1 – n" patch files are loaded; if the [Transition Type] is "Deactivate Patch" or "Delete Patch", "n – end" patches are loaded.

[Transition Type]: You can choose one from "Activate Patch", "Deactivate Patch", "Confirm Patch", and "Delete Patch". After loading a patch, you must activate it and observe whether it runs normally. If normal, confirm the patch and transit it to the RUN state; if abnormal, delete the patch.

B.2.3 Querying Information of Specified Board Patch Area

This operation is to query the status of a specified patch of specified board. The queried result can be DEACTIVATED, ACTIVATED, and RUN.


B-4

Command

DSP PATCHSINGLESTAT

Parameters



[Patch File No.]: It indicates the number of the patch file to be loaded. If the value is "n", the number "n" patch of the board is queried.

B.2.4 Querying Information of Overall Patch Area

This operation is to query use of the board patch area of a specified board. It covers the following: numbers of the current patch files, versions of the current programs, number of the patches, number of formal patches, number of temporary patches, and number of running patches.

Command

DSP PATCHFULLAREAINFO

Parameters



B.2.5 Querying Board Patch Information

This operation is to query the number of running patches and corresponding patch file number of a specified board that are recorded on the BAM.

Command

LST PTCH

Parameters


B.3 Preparations for Patch Operation

Before the patch operation, you must make the following preparations.


B-5

B.3.1 Obtaining Correct Patch File

The online patch for a board is based on the software version. It must be used together with the corresponding basic software. Thus you must select the patch file for a board correctly. To obtain applicable version information of a patch, you must read the instructions of the patch carefully.

One patch file may contain several modifications on the software. If unspecified, a newly released patch file is usually based on the previous one. That is, a subsequent patch file not only solves the new problems but the old ones.

B.3.2 Saving Patch File to Loading Directory

Save the patch file to the directory that stores the corresponding board software. By default, the loading directory is D:\cdma2000\LoadDATA\ on the BAM. If the patch file in the directory is an old one, back it up to another directory, delete it, and copy the new one.

B.3.3 Selecting Correct Operation Time

You must load the patch at low traffic hour, generally, after 24:00.

B.4 Patch Operation

To operate on the patch, proceed as follows:

B.4.1 Querying Loading Control Mode

Query the patch loading mode using LST LODCM. By default, the loading control mode is "Load from BAM". If the loading mode is "Load from FLASH", change it using MOD LODCM.

B.4.2 Loading Patch

Load the patch using LOD PATCH directly as the new patch also contains the original one. When loading the new patch, the system deletes all old patches automatically.

Caution:

If the patch does not match the software version, loading patch may cause board reset. If that happens, delete the patch from the loading directory immediately and contact Huawei technical support engineers.


B-6

B.4.3 Checking Patch Status

Query the status of a specified patch of a specified board using DSP PATCHSINGLESTAT. The patch newly loaded should be in the deactivated state, and the status of the active and standby boards must be identical.

Note:

When loading patches to all modules simultaneously, loading may fail in certain modules. If that happens, load patches to these modules separately.

The patches newly loaded are in deactivated state. But this does not affect normal system running.

B.4.4 Activating Patches

Activate patches using SET PATCHSTAT if the status of the loaded patches is normal.

B.4.5 Querying Patch Status

After activating patches, query the patch status using DSP PATCHSINGLESTAT. The patch newly loaded should be in the deactivated state, and the status of the active and standby boards must be identical.

B.4.6 Checking System Operation

After activating patches, check whether board status is normal according to CPU usage, board indicator, alarm message and so on.

If board switchover or system reset occurs, recover the activated patch to the deactivated state.

B.4.7 Confirming Patch Running Status

If the patch versions of the active and standby boards are identical and the system runs normally, confirm patch status using SET PATCHSTAT and transit the patch state to RUN.

At this point of time, the procedure of applying a patch is completed.

Installation Manual-System Commissioning [ cBSC6600 ]

Documents

Transcript of Installation Manual-System Commissioning [ cBSC6600 ]